For most enterprise projects, testing is not really fun. It’s boring, cumbersome, and takes time and effort — especially for distributed applications or when changes in existing functionality forces test scenarios to adapt. Still, software tests are crucial; so, how can we tackle them in an effective and productive way?
Enterprise Java has come a long way. What does a modern development approach look like, in the age of Jakarta EE and MicroProfile APIs?
In this session, we’ll have a look at supersonic, subatomic Java with Quarkus. If you’re familiar with enterprise development with Spring or Java EE, you’ll be delighted to see the effective way of working, Quarkus enables. We’ll see the benefits of Quarkus for modern, cloud-native microservices in the year 2020. Get yourself ready for this live-coding-only session!
The problem developers new to open source have is joining the community, starting to contribute, and using common open-source tools. In this session, attendees will learn how to contribute and become valuable a part of any open source community. Attendees will learn soft and hard skills based on two case studies: Eclipse MicroProfile and Apache TomEE projects.
One of the most important things when building microservices for the enterprise mission critical systems
is high reliability. Even if a new deployed service has a bug,
it is required that the other services should not be affected by this bad service.
This session will provide how to build such a robust system with MicroProfile functions such as
Fault Tolerance, Metrics, and OpenTracing.
Although there are a lot of tuning knobs in Fault Tolerance (timeout, circuitbreaker, retry, fallback, and so on),
Are you wondering how to secure microservices? Eclipse MicroProfile JWT (https://microprofile.io/) is the answer. MicroProfile JWT designs a token based authentication and authorization mechanism, which enables authorized access from clients to services or from services to services by using JWT token.
Transactions are one of the most complex and yet very important areas of computing. They can get particularly hard when the system moves to the distributed environments as almost every component in the distributed system is liable to failures. Traditional locking protocols, used in transaction solutions today, are then very prone to holding locks on resources for unnecessarily long periods. The saga pattern provides an alternative non-blocking solution with the design that allows individual parts of the transaction to commited immediately and independently.
For 2 decades, Java EE has been the reference programming model for enterprise applications. With the rise of the cloud, started by Amazon in 2006, the IT landscape has changed and application needs have evolved in terms of architecture, scalability model, observability...
Should we throw away our good old Java EE applications? Are they able to evolve in this new context? How to make them cloud-ready or even better cloud-native? Do we need to switch to another technology?
Over the years Java application servers have acquired a bad reputation among developers:
- Tedious and error-prone development cycle
- Painful testing
- Slow startup time
- Heavy system footprint.
In a nutshell: not productive enough and too heavy for modern cloud-native applications!
But is this bad reputation still relevant today? What about modern application servers and frameworks such as OpenLiberty, WidlFly, Quarkus, Payara, KumuluzEE and TomEE? Are they ready for this new cloud-native world?