News for hackers. Stuff that matters.
Re:Microservice Antipatterns: The Queue Explosion by mindcrash on Monday March 26, 2018 @03:56PM (#16681961)
Kafka deserves some credits here, because it destroys these kind of architectural problems however.

It completely changes how to think about service based architectures. In fact, with a properly designed architecture sitting around Kafka APIs and a plethora of queues magically disappear, because instead of function and request-response driven the system becomes reactively data driven, sitting around a single bus.

This makes designing actual services a lot easier because instead of thinking about a few hundred function names all you need to think about are actual data flows (data comes in at a central point -> gets transformed -> gets moved out at a central point).

As a added bonus it scales like crazy, to the point that hammering through a terabyte of data looks like nothing.

A great talk from Ben Stopford (Confluent employee, so mostly Kafka centric) about this subject can be found here:

https://www.slideshare.net/benstopford/devoxx-london-2017-re...

Re:Microservice Antipatterns: The Queue Explosion by cpitman on Monday March 26, 2018 @08:45PM (#16684153)
I agree, when Kafka is (or can be made) a good fit it simplifies a lot of this. Thanks for the presentation link. I'm seeing companies trying to use Kafka for "Request style" services, ie as just another enterprise messaging system.