Issue #30 | Jun 17, 2016
The main focus of this article is to provide reasons to use or not to use Microservices architecture.
Rancher team talks about: Moving key Rancher features into separate microservices projects, dockerizing microservices deployments and cataloging Dockerized application templates, and enabling them for deployment through the Rancher catalog.
How can Startups benefit from building Microservices? When should they start to implement Microservices? Which obstacles do companies face when they switch to Microservices?
Talks on performant microservices, exception handling and documentation driven development.
Author talks about why there is a need for microservices (in some settings) and a bit about neglected issue in all the hype surrounding the topic these days: the feasability of organizational adoption of microservices.
The difficulty of monitoring and logging increases exponentially whenever your business logic is running in multiple services. If you don’t plan your microservice logging in a clever way, it can become impossible to understand what the application is doing.
The Fabric Model is the most sophisticated of the three models found in the NGINX Microservices Reference Architecture (MRA). It’s internally secure, fast, efficient, and resilient.
Pivotal architect Rohit Kelapure has been working on this topic a lot and has written a white paper on migrating from Enterprise Service Bus (ESB)-based legacy architectures.
Just as agile development solves an engineering bottleneck, microservices solve an architectural bottleneck.
…and if so why haven’t they done so yet ?
Interview with Chris Richardson ( @crichardson ) on Microservices at the QCon NYC conference.
Interview with Peter Lawrey ( @PeterLawrey ) at QCon NYC about what microservices and trading systems can learn from each other as well as his thoughts on best practices for exception handling.