The microservices architecture pattern is designed to be distributed in nature. But recently, we have observed that this distribution of responsibility has gone beyond the microservices itself. With the invent of the very first "Service Mesh" sidecar, people realized that microservices are not small enough and there is more room for improvement. This article discusses how the sidecar pattern is expanding within the microservices architecture.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (2)
We encourage the entire article to be published on DEV.to (if you have proper rights), with a linkback if appropriate. Otherwise, we recommend original material, such as an original commentary on the article. From the Terms of Use:
Posts that are simply intended to encourage readers to view an external resource are discouraged.
Thank you.
Sure. I'll keep a note of this when publishing in the future.