https://69b9f622ea77c40008596038--watermill.netlify.app/Recent content on WatermillHugoenThree Dots LabsWed, 09 Oct 2024 02:47:30 +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/advanced/metrics/Tue, 12 Feb 2019 21:00:00 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/advanced/metrics/Monitoring of Watermill may be performed by using decorators for publishers/subscribers and middlewares for handlers. We provide a default implementation using Prometheus, based on the official Prometheus client for Go.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/advanced/forwarder/Wed, 13 Jan 2021 12:47:30 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/advanced/forwarder/Publishing messages in transactions (and why we should care) While working with an event-driven application, you may in some point need to store an application state and publish a message telling the rest of the system about what’s just happened.https://69b9f622ea77c40008596038--watermill.netlify.app/advanced/fanin/Sat, 21 Jan 2023 12:47:30 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/advanced/fanin/FanIn component The FanIn component merges two topics into one. Configuring // ... type Config struct { // SourceTopics contains topics on which FanIn subscribes.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/advanced/fanout/Wed, 09 Oct 2024 02:47:30 +0100https://69b9f622ea77c40008596038--watermill.netlify.app/advanced/fanout/FanOut component FanOut is a component that receives messages from a topic and passes them to all subscribers. In effect, messages are “multiplied”.