Are you a MicroProfile Speaker?
Your session needs MP media coverage! Submit a github issue by filling in all the required information & we will do our best to push your session to the MicroProfile Community.
Community Day at EclipseCon 2022 was held in person on Monday, October 24 in Ludwigsburg, Germany. Community Day has always been a great event for Eclipse working groups and project teams, including Jakarta EE/MicroProfile. This year was no exception. A number of great sessions were delivered from prominent folks in…
Serverless applications, which can scale to zero and allocate resources on demand, are certainly a hot topic in 2022. Can MicroProfile applications be serverless? YES. This post demonstrates how to run a MicroProfile application on Open Liberty as a serverless function in IBM Cloud Code Engine.
A brief history in maker projects of the cloud-native Java demos that we’ve built around Open Liberty using MicroProfile, Jakarta EE, and Java EE technologies.
Do you want cloud-native Java applications that can start up in milliseconds, without compromising on throughput, memory, development-production parity, or Java language features? The Open Liberty 22.0.0.11-beta brings you InstantOn, an exciting new feature that provides incredibly fast startup times for MicroProfile and Jakarta EE applications.
Open Liberty 22.0.0.12-beta release previews MicroProfile 6 features: MicroProfile JSON Web Token (JWT) 2.1, which includes simple JWT validation, and MicroProfile Metrics 5.0, which provides user-defined metric registry scopes.
Liberty Tools for Eclipse provides a new experience for developing cloud-native Java microservices on Open Liberty. This early release provides assistance when using MicroProfile APIs, editing your Liberty server.xml configuration in Maven and Gradle projects, a Liberty Dashboard for organizing your projects, and Liberty dev mode (automatically deploying code changes to your running app, without having to restart the server), all from within your Eclipse IDE.
For MicroProfile 4.1 applications that require additional startup time on their first initialization, you can define startup probes which are used to check the startup status of the application before the Liveness probe takes over. MicroProfile Health 3.1 introduces a new health check called Startup. You can create your own health check procedures to verify that your microservices have fully initialized using the @Startup annotation. And you can configure the Kubernetes Startup probe with the REST endpoint /health/started.
