> a message broker is a service that transforms network errors and machine failures into filled disks
...
> mark it as required in the database, and wait for something else to handle it. > > Assuming that something else isn’t a human who has been paged.
...
> Systems grow by pushing responsibilities to the edges
...
> A distributed system is something you can draw on a whiteboard pretty quickly, but it’ll take hours to explain how all the pieces interact.
I love when you can mix technicals and not taking yourself seriously.
Although be careful with using DB as a task queue. Concurrency is a b* and message brokers are very good at it. AMPQ has been created because the authors started with a BD message broker and it didn't work.
A task queue is message broker + persistance + status. Celery does that very well in the Python word, and works with rabbitmq, redis, postgres, etc.
What amaze me the most is autobahn + crossbar.io. It does PUB/SUB, RPC, load balancing and all the stuff for Python, JS, PHP, C#, Java... And it works even in the browser. Cool stuff.