There are several best practices for building microservices architecture properly. In this article author mentions the best practices with some new rules dedicated especially for microservices deployed on Kubernetes platform. By Piotr Minkowski.
The first question is if it makes any difference when you deploy your microservices on Kubernetes instead of running them independently without any platform? Well, actually yes and no… Yes, because now you have a platform which is responsible for running and monitoring your applications, and it launches some its own rules. No, because you still have microservices architecture, a group of loosely coupled, independent applications, and you should not forget about it!
What you will find in the article:
- Allow platform to collect metrics
- Prepare logs in right format
- Implement both liveness and readiness health check
- Consider your integrations
- Use service mesh
- Be open for framework specific solutions
- Be prepared for a rollback
… and more. You will also get sample Spring Boot application that implements currently described best practices and is written in Kotlin. It is available on GitHub in repository sample-spring-kotlin-microservice under branch kubernetes.[Read More]