We are going to show you what happens when the management lets enterprise Java developers and architects decide how we can control the IoT devices in our new office. While it's easy to figure out why Microprofile is cool, it's harder to see how to get in into your project. By the end of this talk, you will be introduced into the patterns and software in the enterprise world of Java explaining how to build a build a secure, stable, modular, and integrated system on an example of a completely over-engineered IoT solution to control the lights and plant's well-being in the new office.
Platform as a Service (PaaS) is a cloud computing model that allows developers to build and deliver applications without the responsibility of maintaining the infrastructure. Instead, they can focus on what matters: the application business. Platform.sh offers a PaaS that reduces the complexity associated with deploying and managing enterprise Java applications.
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.
In this talk, we’ll have a deep dive into MicroProfile OpenTracing, discussing the key points of the specification, including naming conventions, the @Traced annotation, the ability to add explicit instrumentation in business code or even extend scope of tracing by adding OpenTracing compatible instrumentations. We’ll then build a simple MicroProfile application with the MP-OpenTracing module and see how the reported telemetry data looks like in Jaeger an OpenTracing compliant distributed tracing system.
How would you like to run integration tests on the exact docker container you are already building and pushing into production?
With the use of Testcontainers, this becomes reality. No longer do you have to mock your way to success! Testcontainers allows you to use the same container environment you would use in production. Sleep well at night knowing you’ve tested your real application.
It seems that more and more enterprise technology is emerging that is based on Java EE. There are a lot of options to choose from, between Java EE, what is now Jakarta EE, MicroProfile, and combinations of their APIs. If we look at available application containers the number of possibilities is even higher. Which platforms, particular standards and runtimes should enterprise developers base their applications on in year 2019?
Enterprise Java has come a long way. Let’s not focus on the old, darker days, but modern approaches on how to do enterprise applications. Where do we start? What technologies, tools, and approaches are a good choice for our applications and what allows us to effectively implement business logic and to deliver value to our users?
Java assumed the whole computer belonged to itself, that it could consume all available memory and CPU. In this presentation, we will demonstrate the problems associated using Java for “microservices”, and how the open source ecosystem is working to insure the future of Java by being cloud first, container native, serverless focused and Kubernetes optimized. This is where GraalVM meets Quarkus (https://quarkus.io), bringing server-side and enterprise-capable Java to enable you to build truly cloud native apps.
Historically Java was able to handle the biggest enterprise problem(s) with its Write once,run anywhere(WORA) paradigm. With Cloud Native Applications grown to popularity, things like running applications as linux containers, serverless taking centre stage -- Java was pushed back by languages like golang, node.js as the forerunner to build Cloud Native Applications as they are smaller, quicker and arguably more nimble.
It's a challenge to choose Java microservices framework which satisfies your requirements. Some developers prefer reactive, functional style of APIs and other developers give preference to inversion of control, declarative style APIs offered by MicroProfile. In this session I will explain the differences and pros and cons of each approach. I will demonstrate how the functionality of MicroProfile APIs such as HealthCheck, Metrics and OpenTracing can be implemented in reactive-style applications.