Contents
How do you monitor microservices in production?
The Five Principles of Monitoring Microservices
- Monitor containers and what’s inside them.
- Alert on service performance, not container performance.
- Monitor services that are elastic and multi-location.
- Monitor APIs.
- Map your monitoring to your organizational structure.
How do you ensure high availability in microservices?
Ensure microservices’ high availability with a focus on caching for fast performance even under high loads, and monitoring that enables quick problem resolution.
- The need for microservices scaling.
- Service-to-service load balancing.
- Built-in data caching.
- Monitoring and tracing for issues.
How do you ensure resilience in microservices?
A microservice needs to be resilient to failures and to be able to restart often on another machine for availability. This resiliency also comes down to the state that was saved on behalf of the microservice, where the microservice can recover this state from, and whether the microservice can restart successfully.
Why are microservices important in the development process?
Microservices — which promote a modular application design — facilitate flexibility, as they provide organizations with the freedom to choose development languages, frameworks, code builds, integration processes and runtime infrastructure. However, such freedom leaves developers and DevOps teams with a daunting array of choices.
Is there a universal action plan for microservices?
There is no prescriptive or universal action plan to deploy microservices in a production environment.
What are the requirements for a microservice SLAs?
We defined requirements for all microservices. All services must support high availability: Send alerts to the accountable team for downtime, slow response times and high error rates The accountable team provides support with 24/7 oncall availability for high priority issues All services must provide broad visibility: We use Librato and New Relic.
Do you need to rethink microservices architecture to succeed?
To succeed with microservices, IT organizations need to rethink the way they design and deploy applications — and not all the necessary changes are technical ones. While a distributed microservices architecture isn’t a fit for all enterprises or application types, it works well in many situations.