~hackernoon | Bookmarks (7)

This article explores the evolution and technical intricacies of microservice architecture using Java programming. It covers defining service boundaries, selecting tools and frameworks, establishing communication patterns, ensuring scalability and fault tolerance, and implementing CI/CD practices for efficient deployment.

On one of the projects I worked on, there were 8 services that used Auth0 for front-end authentication and a rotated static token for back-end authentication. Despite this, the main authentication and authorization single sign-on (SSO) system was Microsoft Azure Active Directory (AD), which was used for accessing company email, the corporate VPN, AWS infrastructure, etc.

Konstantin Glumov highlights the importance of continuous learning in tech, with a focus on cloud computing, microservices, and Kotlin for 2024. He advises developers to expand their skills in cloud technologies and engage with the community, while companies should foster an environment of innovation and learning.

12 Factor Apps: What it is: A set of best practices for building cloud-native applications. Benefits: Portable: Runs anywhere (cloud, on-premise). Scalable: Grows easily with your needs. Maintainable: Easier to understand, fix, and update. Developer-friendly: Faster deployments and happy devs. Resilient: Built to handle change and failure. How it works: Treats apps as collections of independent services. Uses clear rules for configuration, dependencies, etc....

Keen on discovering how Uber redefines resiliency in their microservices architecture by drawing on centuries-old concepts? Let's explore the foundational elements together to gain a better understanding of the problems at hand.

Today, I discuss languages and the importance of being language/architecture agnostic. I observe that the backend world is rediscovering itself and criticizes microservices architecture. The key idea is that we shouldn't blindly follow all mainstream trends. Maybe the optimal decision for you is to either stick with a monolith or strike a balance between monolith and microservices.