Kubernetes is becoming the de-facto platform to deploy our application nowadays. But this movement also implies some changes in the way we code our applications. Before this change, we just developed a monolith application where everything was up and running up front, now we are breaking down this monolith into (micro)services architecture and everything is interconnected with the network. Although it might seem easy, done properly is not an easy as there are some challenges to address that was not in a monolith architecture.
In this session, we’re going to start discussing what are these challenges (ie fault tolerance, service discovery, open tracing, or health checks) and demonstrate how they can be solved using Eclipse MicroProfile specification.
Come to this session to learn how to develop a successful Kubernetes-Native application using Quarkus, a Java ecosystem way to develop cloud-first, container-native, serverless focused and Kubernetes optimized.
44. @alexsotob
@
@
</>
The Quarkus Way - Benefits
No FS access at
runtime
No need for a
parser at runtime
No scanning at
runtime
Less reflection
and classloading
at runtime
Optimized config
Less reflection
(proxy generation)
Prepared
initialization
(ready to serve)
53. @alexsotob53
But when I'm way up here
It's crystal clear
That now I'm in a whole
new world with you
— Jasmine
“
[http://bit.ly/quarkus-tutorial]
54. @alexsotob
Hay un amigo en mí,
cuando salgan a volar,
hay un amigo en mí
— Toy Story
“
@alexsotob
asotobue@redhat.com
http://www.lordofthejars.com/
lordofthejars