We were unable to load Disqus. If you are a moderator please see our troubleshooting guide.
Good question Thiago! It honestly depends on your application what configuration works best for you. In larger applications where the producer is performing a lot of business logic, inputs required for message production can come from a variety of sources or the producing application is written in another programming language, it usually makes sense to split them apart. Granted this means that you also now have the overhead of deploying a separate application and you have to ensure that message structures are compatible between the two services. In smaller applications, it may be easier to produce and consume from the same application with the benefit being that Broadway will gracefully shutdown the consumer and will pick up where it left off from the queue once the application comes back up.
Hopefully that helps!
Excellent! The both part 1 & 2 is a rich dinner of Elixir tech! I'll spend a few days to taste it. Thanks!
haha. Glad you are enjoying the series. May I suggest the BEAM wine pairing ;)
Hi Alex Koutmos excellent post. Thinking about scale this app I should separate the producer and consumer in two apps? So the `HackerNewsIdGenerator` runs on one node and the consumer can run on 2 or more nodes.