In this article, I’ve compiled all the main architectural interaction styles and evaluated them based on their impact on connectivity, data integrity, maintenance/ownership complexity, fault tolerance, and so on. At the end, I’ll summarize everything in a comparison table to help you make your choice.
A summary article on choosing a load balancing approach depending on the task. I decided to collect the main algorithms and approaches. I think some of the information overlaps with what’s described in the book “Designing Data-Intensive Applications” (the one with the boar). Although I might be confused, as I read it a long time ago.
I decided to gather everything I’ve learned about the API from various posts into a single article, cutting out all the unnecessary fluff. I’ll also leave a sort of cheat sheet for myself.
A little bit about integrations in the “bloody” and not so enterprise. Basically, this is an overview article without a detailed dive into technical aspects and examples of implementing solutions. I will try to give a general idea of what integration approaches exist, what problems arise when using them.
