Have you ever wondered what is the modern way to create cloud-native microservices? Is the microservice you have created good for cloud infrastructure? How best to utlise the modern technology to improve your efficiency, so that you can just focus on business logic?
Cloud native is the most hotly debated disruptive technology trend in software. In fact, this new trend has initiated a fundamental architectural design paradigm shift: modern web-scale applications are now constructed cloud native, based on latest microservice architecture principles.
Conventional wisdom has it that Java EE is a bad starting point for building cloud-native Java applications, but despite this most cloud-native frameworks are designed to use and extend Java EE. The issue has been not that Java EE can't be used, but deploying applications to new cloud platforms like Docker and Kubernetes so they can be efficiently updated and scaled requires new API's. Enter the Eclipse MicroProfile initiative which, combined with Jakarta EE, has been rapidly building out these gaps.
There is a new platform in town: Kubernetes. And it is establishing itself as the common denominator for public and private clouds with unprecedented momentum.
This talk is for you when you sensed that Kubernetes may be important and are wondering if using it is more straightforward than spelling its name.
As more Eclipse projects are migrated to the new cluster based build infrastructure, it's time for an update on the current status and to share best practices how projects can make the most of it. The following questions (and more) will be answered: Why does my build take so long and how can it be made faster? What are Jenkins pipelines and why/when should they be used? Can I finally run docker based builds?
The Eclipse infrastructure is undergoing a massive overhaul, modernizing every* aspect from builds, to websites, our data and API, networking and virtualization. New tools and technologies are cropping up in our datacenter, including Kubernetes, Docker, 10GbE, nginx, and new developments with Gerrit and even our home-brewed Drupal-based codebase.
Do you have a technology that you believe is suitable for cloud native development? Do you want to take advantage of the cloud native IDE. In this talk we are going to show how you can extend Eclipse Che with your technology and make it discoverable to the world.
Containers, Kubernetes, Cloud Native, Microservices, Eclipse MicroProfile. It feels like you’re going to drown amongst the buzzwords! In this session we will guide the developer through the minefield of all these buzzwords to understand the concepts and develop solutions with them.
You might know Eclipse Che as an open source web IDE for cloud native applications. The next generation of Che will also be a cloud-native platform for web IDEs in addition to being an IDE. Just like the original Eclipse IDE itself, you will be able to completely customize the developer experience with both server-side and client-side plug-ins!
Microservices are taking over the world. Developing cloud native apps can be challenging. It works on my machine but it fails when deployed to the cloud as a Kubernetes pod - this problem isn't new.