Eclipse Che 7 as a developer tool has evolved to work with some of the most relevant technologies available today: Eclipse Theia, Language Servers, Debug Adapters and even VSCode extensions, all containerized within the IDE. Developer environments have become reproducible, repeatable and consistent across teams of developers - allowing easy integration into your devops toolchain. Working on a kubernetes application has never been easier, just bring your kubernetes application directly into your developer environment.
The target audience are Software Engineers and Architects that have a basic understanding of Java, containers and the cloud and are keen of sustainability.
I will take a very simple example Java application and demonstrate how it can be refactored to adhere to cloud native principles. Thereby, I will focus on aspects that are relevant for making the application more sustainable: More flexible usage of resources.
Every development team wants to have their own Jenkins instance and “all the resources”. How can this be administered - especially if you have more than 200 Jenkins instances?
This talk shows how Jenkins master instances can be provisioned and custom tailored in seconds, while admin and upgrade overhead stays reasonable. We will also talk about quotas to fairly distribute resources and avoid teams affecting each other. Whether you are a release engineer or developer of an Eclipse project or a Jenkins administrator at your company, this talk is for you.
Eclipse Che introduces a new kind of developer workspaces that are running directly on Kubernetes and accessible through a web based IDE. The new version of Eclipse Che 7 supports a codified definition of developer tooling needed to work on a project, called “Devfile”.
Devfile provides a declarative abstraction of a replicable developer workspaces, which is inclusive of the runtime environment, the source code of the projects mapped to repositories and the tools, plugins and commands needed to code, build, test, run and debug a project.
Devfile lives with the projects’ source code and follow its lifecycle. It’s easy to create, modify, fork and extend.
Kubernetes is becoming the de-facto platform to deploy our application nowadays. But this movement also implied some changes on the way we code our applications, where we just develop a monolith application where everything was up and running up front, now we are breaking down this monolith into (micro)services architecture. Although it might seem easy, done properly is not an easy movement as there are some challenges to address that were not there before, at monolith architecture time.
This tutorial explains how to design applications to effectively develop them with the Microservices architecture. It examines building microservices step by step, how to design boundaries between components using Domain-driven design and when to split a microservice into smaller services.
IoT is evolving really quickly while the industry is holding back because of (cyber) security and thus requiring on-premise deployments. To create an industrial IoT platform, the concern from the industry has to be addressed. A lot of IoT platforms are available from public cloud providers which makes them unusable.
Eclipse IoT projects enable to build an IIoT platform which can be deployed anywhere, from a private, airgapped installation on a bare metal server to private or public clouds.
Ever wondered what makes a cloud-native application "cloud-native"? Ever wondered what the unique challenges are and how best to address them on fully-open Java technologies? In this workshop, you'll learn what it means to be cloud-native and how that impacts application development. You'll learn about Eclipse MicroProfile, an industry collaboration defining technologies for the development and management of cloud-native microservices.
This fast-paced, demo-driven, entirely slide free session will show you the many ways of effectively deploying a Java EE application to Azure. We will start by deploying a local Java EE application to basic IaaS on Azure. We will then deploy the same application to an entirely managed Azure PaaS. Finally we will deploy the application to Azure using Docker and Kubernetes. We will discuss the trade-offs of each approach on the way, offering guidelines for which approach might be best for your application on the cloud.