Amol Gote

Thank you for your feedback! You’re right that using secrets management tools like AWS Secrets Manager is a modern and secure way to handle sensitive information such as database hostnames and ports. In this context, the environment variables mentioned in my article are retrieved from AWS Secrets Manager when the container starts. This allows us to securely manage and inject secrets into the application ensuring that sensitive information is handled securely.

No problem. Appreciate your feedback.

Article is updated now. Thanks again for pointing it out.

Have added that and submitted to moderation, it should get reflected soon. Thanks for pointing out the issue.

Thanks for the feedback, have removed the date formatting method, had just added as an sample. Also added more example for code commenting.

That's a great point! Spring Boot Actuator's /info endpoint is indeed a valuable tool for this purpose. Our choice to implement a custom controller was driven by a few considerations:

• We wanted to ensure a consistent method across all our microservices without relying on additional configurations.
• Our custom solution provides more flexibility in terms of the data structure and the possibility to extend it.
• Some internal guidelines may also influence the choice, like security policies or specific data exposure needs.

However, it's worth noting that both solutions can coexist and provide value. Thanks for bringing this up!