The Microservice Weekly #98
A hand-curated weekly newsletter with the best articles on microservices, from the engineers of RisingStack.
In this eBook you will learn about the basics of “decomposing” a monolith into microservices and why it is a worthwhile effort for your project. You will also learn about commonly considered microservices best practices and how you can apply them.
There are many decisions to be made when setting up a production cluster, we’ve struggled for quite a while to understand the different available options, networking in the container world is quite hard, there are many competing technologies, load balancing and controlling external traffic can get complicated and how to get started with internal service communication has many options, in this article we’ll show you the decisions we made and found that work out well for us.
The question is whether or not one should go on a centralized, or a decentralized strategy for setting up continuous integration for multiple teams inside the same organization.
Early in 2016, several Netflix teams were asked the question: “What would it take to allow members to download and view content offline on their mobile devices?”
There’s more than one way to skim a monolith. There seem to be two popular ways system designers do it — diving in head first or taking forever to chip away, by being too careless or too cautious.
We are going to discuss efficiency/performance optimizations of different layers of the system. Starting from the lowest levels like hardware and drivers: these tunings can be applied to pretty much any high-load server.
As engineering organizations transition from building monolithic architecture to building microservices architecture one challenge they often face is understanding how to enable communications between microservices.