Contents
How do you keep logging in microservices?
In this post, I’ll share a few best practices that have helped me when dealing with microservices.
- Correlate Requests With a Unique ID.
- Include a Unique ID in the Response.
- Send Logs to a Centralized Location.
- Structure Your Log Data.
- Add Context to Every Request.
- Write Logs to Local Storage.
- Add Traces Where It Matters.
What is log aggregation in microservices?
Use a centralized logging service that aggregates logs from each service instance. The users can search and analyze the logs. They can configure alerts that are triggered when certain messages appear in the logs.
How microservices can communicate with each other?
In asynchronous communication microservices use asynchronous messages or http polling to communicate with other microservices, but the client request is served right away. Instead, do it asynchronously (using asynchronous messaging or integration events, queues, etc.).
Which of the following use cases are good candidates for microservices?
Utility computing scenarios such as integrating an optimization service, forecasting service, price calculation service, prediction service, offer service, recommendation service, and so on are good candidates for microservices.
How do you handle exceptions in microservices?
What we gonna do in this session?
- Build a Spring boot micro-service.
- Add a controller endpoint and service.
- Add global exception handling to handle Spring validations.
- Add custom exception messages enum.
- Populate field validation messages from .properties file.
- Throw all the service and controller exceptions.
How do you do centralized logging in microservices?
Centralized Logging Using Log Streams Using Log Streams is one way to implement centralized logging. The common way to implement it is to stream microservice logs to a common queue. Distributed logging server listens to the queue and acts as log store. It provides search capabilities to search the trace.