https://69b9f622ea77c40008596038--watermill.netlify.app/docs/Recent content in Docs on WatermillHugoenThree Dots LabsSat, 01 Jun 2019 19:00:00 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/docs/message/Wed, 05 Dec 2018 12:42:40 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/docs/message/Message is one of core parts of Watermill. Messages are emitted by Publishers and received by Subscribers . When a message is processed, you should send an Ack() or a Nack() when the processing failed.https://69b9f622ea77c40008596038--watermill.netlify.app/docs/pub-sub/Wed, 05 Dec 2018 12:47:30 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/docs/pub-sub/Publisher // ... type Publisher interface { // Publish publishes provided messages to the given topic. // // Publish can be synchronous or asynchronous - it depends on the implementation.https://69b9f622ea77c40008596038--watermill.netlify.app/docs/messages-router/Wed, 05 Dec 2018 12:48:04 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/docs/messages-router/Publishers and Subscribers are rather low-level parts of Watermill. In production use, you’d usually want to use a high-level interface and features like correlation, metrics, poison queue, retrying, throttling, etc.https://69b9f622ea77c40008596038--watermill.netlify.app/docs/middlewares/Sat, 01 Jun 2019 19:00:00 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/docs/middlewares/Introduction Middleware wrap handlers with functionality that is important, but not relevant for the primary handler’s logic. Examples include retrying the handler after an error was returned, or recovering from panic in the handler and capturing the stacktrace.https://69b9f622ea77c40008596038--watermill.netlify.app/docs/cqrs/Tue, 12 Feb 2019 12:47:30 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/docs/cqrs/The CQRS component is a high-level API that lets you work with Go structs instead of messages. Once you configure the EventBus and EventProcessor (or the command equivalents), publishing and handling events becomes very straightforward.https://69b9f622ea77c40008596038--watermill.netlify.app/docs/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://69b9f622ea77c40008596038--watermill.netlify.app/docs/troubleshooting/Logging In most cases, you will find the answer to your problem in the logs. Watermill offers a significant amount of logs on different severity levels.https://69b9f622ea77c40008596038--watermill.netlify.app/docs/articles/Mon, 01 Jan 0001 00:00:00 +0000https://69b9f622ea77c40008596038--watermill.netlify.app/docs/articles/You can find more in-depth tips on Watermill in these articles: Distributed Transactions in Go: Read Before You Try Live website updates with Go, SSE, and htmx Using MySQL as a Pub/Sub Creating local Go dev environment with Docker and live code reloadinghttps://69b9f622ea77c40008596038--watermill.netlify.app/docs/awesome/Mon, 01 Jan 0001 00:00:00 +0000https://69b9f622ea77c40008596038--watermill.netlify.app/docs/awesome/Below is a list of libraries that are not maintained by Three Dots Labs, but you may find them useful.