MicroProfile vs Jakarta EE
Açıklaması şöyle
Jakarta EE also inspires the MicroProfile initiative, where several organizations, companies, and communities create an optimized profile to work with both microservices and cloud-age.
Açıklaması şöyle
MicroProfile originated as a reaction to Java EE becoming stale, and the first three specifications were actually taken directly from Java EE: CDI, Jax-RS and JSON-B. That is, in most cases, dependency injection, REST endpoints and support for JSON request and return objects.
MicroProfile Standartlara Dayalıdır
Bazı standartlar şöyle
- Jakarta EE Core Profile, which we just described in the previous section.- Health supports the Kubernetes standard of probes for liveness, readiness and startup. It is perhaps the specification that is clearest on the intention of MicroProfile as cloud native.JWT authentication lets you use JSON Web Tokens as authentication bearers, which is growing into being the industry standard these days.- Metrics provides data of how your application is running in terms of generic measures like CPU usage, memory usage and so on, and also lets you write your own custom metric. How many users have put an item into the shopping bin, for instance.- Fault tolerance is what you need when doing calls to other services. They might be down or responding slowly, so you’ll need to be able to retry doing your remote calls, throttle how many calls you make towards a given service, or if all others fail do a fallback to another solution.- Config lets you inject your environment variables directly as objects into your code, using dependency injection. That way you can easily use the same container image in different environments.- Rest Client gives you a type safe way of doing REST calls.- OpenAPI provides documentation for your REST endpoints, and allows you to specify details about your endpoints, parameters and return values.- Telemetry is the newest specification. It focuses on observability. It’s focused on tracing calls spanning multiple services.
Bunların dışında Bazı standartlar şöyle
Long-running actionsGraphQLContext propagationReactive messagingReactive streams operators
MicroProfile Destekleyenler
Açıklaması şöyle
... as opposed to Spring Boot, which isn’t based on any specification .., Eclipse MicroProfile has largely been adopted by many editors who provide different implementations, among which Quarkus, Wildfly, Open Liberty and Payara are from the most evangelical.
Liste şöyle
Payara MicroApache TomEELauncher by FujitsuOpenLiberty by IBMkumuluzEEHelidon by OracleQuarkus by RedHatWildFly by Redhat
Maven
Şöyle yaparız
dependency><groupId>jakarta.platform</groupId><artifactId>jakarta.jakartaee-api</artifactId><version>${jakarta.version}</version><scope>provided</scope></dependency><dependency><groupId>org.eclipse.microprofile</groupId><artifactId>microprofile</artifactId><version>${microprofile.version}</version><type>pom</type><scope>provided</scope></dependency>
Hiç yorum yok:
Yorum Gönder