News for hackers. Stuff that matters.
Re:How do you cut a monolith in half? by sametmax on Friday June 30, 2017 @10:16AM (#14670859)
This article is not just very well written, it's also very funny. Some gold:

> 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.

Re:How do you cut a monolith in half? by marcosdumay on Friday June 30, 2017 @11:36AM (#14671381)
> Concurrency is a b*

I have to say. I spent way too much time trying to understand what b* trees have to do with concurrency, and what system you are using that implements them.

Re:How do you cut a monolith in half? by 102030485868 on Friday June 30, 2017 @01:01PM (#14672020)
I interpreted that as, "Concurrency is a bitch...".
Re:How do you cut a monolith in half? by marcosdumay on Friday June 30, 2017 @01:32PM (#14672275)
Yeah, that's the correct interpretation. I got there, eventually.