If you profile your code under load, you can have an idea of how it would behave under pressure. At a minimum, you should profile your source code before you deploy them. It should be part of your QA-OPS, DevSecOps process and not an afterthought.
How To Debug Your Java Quarkus Microservices With Netbeans
As part of the quick tips series, I will show how you can debug Quarkus microservices using Netbeans. This quick tips work for any Java applications running either through Maven or in standalone.
Here is the commands to debug your application when running through Maven. The default debug port is 5005.
./mvnw compile quarkus:dev -Dagentlib:jdwp=transport=dt_socket,server=y,suspend=nHere is the command to debug your application when executing through the jar command.
# start application in debug: example
java -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=9009 -jar <your-application.jar>I hope this was helpful. Stay tune for more quick tips.
How the community is making Java EE more relevant to the Cloud-native and Containers
Micronaut and Quarkus are competing Java frameworks with their focus in reducing Java applications cold start time and memory footprints; two requirements for serverless architectures and environments such as AWS Lambda.
Is there a future for Java on the (Web) Front End?
Fast forward to 2020; JavaScript frameworks dominate web application development on the front end. Java is relegated to the server-side. JSF 2.3 updated the support for HTML 5 and WebSocket but it feels as if JSF is still missing something to be cool.