Common Problems and Solutions: Service instance per Container

Common Problems and Solutions: Service instance per Container.md

Problem	Explanation	Solution
Container orchestration and management	Managing and orchestrating containers at scale can be challenging without the proper tools and processes in place	Leverage container orchestration platforms like Kubernetes or Docker Swarm to manage and orchestrate containers at scale
Distributed data management	Defining clear boundaries for each microservice and balancing the autonomy of evolution and deployment of each microservice with strong dependencies, cohesion, and data aggregation	Define clear boundaries for each microservice and balance the autonomy of evolution and deployment of each microservice with strong dependencies, cohesion, and data aggregation. Choose between availability and ACID strong consistency based on the CAP theorem
Security risks	Security risks can arise if microservices are not properly secured and isolated from each other	Be aware of the most common security risks and plan how to prevent and mitigate them. Deploy service instances per container or per host to isolate service instances from one another and eliminate the possibility of conflicting resource requirements or dependency versions
Monitoring and troubleshooting	Monitoring and troubleshooting can be challenging in a containerized microservices environment, especially when dealing with a large number of containers	Configure alerts to focus on attributes closely related to the service experience. Use container-native monitoring solutions to dynamically aggregate container and application data at a service level. Monitor individual containers and their hosts, as well as the pod level which manages several containers used to run a microservice