Key Takeaways

• Quarkus is a full-stack, Kubernetes-native Java framework made for Java virtual machines (JVMs) and native compilation.
• When developing microservices architecture, there are some new challenges that need to be addressed such as scalability, security, and observability.
• Microservicilities provides a list of cross-cutting concerns to correctly implement microservices.
• Kubernetes is a good start to implement these microservicilities but there are some gaps.
• MicroProfile is a specification to implement cross-cutting concerns using the Java programming language.
• Authentication among internal services may be achieved by using tokens (i.e., JWT).

Why Microservicilities?

In a microservices architecture, an application is formed by several interconnected services where all of them work together to produce the required business functionality.

So a typical enterprise microservices architecture looks like this:

At the beginning, it might seem easy to implement an application using a microservices architecture.

But doing so properly is not an easy journey as there are some new challenges that weren’t present with a monolith architecture.

Some of these are fault tolerance, service discovery, scaling, logging, and tracing, just to mention a few.

To solve these challenges, every microservice should implement what we at Red Hat have named “Microservicilities.”

The term refers to a list of cross-cutting concerns that a service must implement apart from the business logic to resolve these concerns as summarized in the following diagram:

#kubernetes #article