In the banking industry, we have a lot of business logic running in the old fashion way as monolith enterprise applications; take a look from 0 to how you can work with last Java Version and Helidon to move forward your application to the Oracle Cloud.

1. Rocking the
microservice world
with Helidon.
Alberto Salazar,
Chief Advance Latam,
Java Champion
Jug Leader
JCP Associate Member
Auth0 Ambassador
Oracle Groundbreaker Ambassador
JakartaEEOne Español
31th July 2023
@betoSalazar

2. @betoSalazar
Microservices ?
Some History
Enterprise Applications

3. How was ruling the EE World ?
Application Server
MONOLITH (EAR | WAR | JAR)
Servlets
EJBs
JPA
Balancer
@betoSalazar

4. How was ruling the EE World ?
Application Server
MONOLITH (EAR | WAR | JAR)
Servlets
EJBs
JPA
Balancer
Customer Payments Loans
Funds
Transfer
N…1 N…
@betoSalazar

5. How was ruling the EE World ?
Application Server
MONOLITH (EAR |
WAR | JAR)
Servlets
EJBs
JPA
Balancer
MONOLITH (EAR |
WAR | JAR)
Servlets
EJBs
JPA
MONOLITH (EAR |
WAR | JAR)
Servlets
EJBs
JPA
MONOLITH (EAR |
WAR | JAR)
Servlets
EJBs
JPA
MONOLITH (EAR |
WAR | JAR)
Servlets
EJBs
JPA
MONOLITH (EAR |
WAR | JAR)
Servlets
EJBs
JPA
MONOLITH (EAR |
WAR | JAR)
Servlets
EJBs
JPA
MONOLITH (EAR |
WAR | JAR)
Servlets
EJBs
JPA
MONOLITH (EAR |
WAR | JAR)
Servlets
EJBs
JPA
@betoSalazar

6. How was ruling the EE World ?
Application Server
Microservicios
(EAR | WAR |
JAR)
Servlets
EJBs
JPA
Application Server
Microservicios
(EAR | WAR |
JAR)
Servlets
EJBs
JPA
Application Server
Microservicios
(EAR | WAR |
JAR)
Servlets
EJBs
JPA
Application Server
Microservicios
(EAR | WAR |
JAR)
Servlets
EJBs
JPA
Application Server
Microservicios
(EAR | WAR |
JAR)
Servlets
EJBs
JPA
Application Server
Microservicios
(EAR | WAR |
JAR)
Servlets
EJBs
JPA
Application Server
Microservicios
(EAR | WAR |
JAR)
Servlets
EJBs
JPA
@betoSalazar

7. How was ruling the EE World ?
Characteristics
● Attachment to the environment(language, platform & OS)
● Single logical executable, deploy everything at once or nothing at all
● Bottlenecks and Failure of part == failure of whole
● Take months even years getting into production
● Centralized authority slows the delivery process (DBA, OPS, QA)
● Coordinated releases are hard, because brings many changes
together from different teams
@betoSalazar

8. The Monolith or Microservices
How it looks
http://microservices.io/patterns/monolithic.html http://microservices.io/patterns/microservices.html
@betoSalazar

9. Microservices
Characteristics
● Deployable, executable & scaled independently
● Smaller code modules are easier to understand
● High cohesion, low coupling
● Failure is isolated (Fail one part of the system)
● Independent Teams (decide their own
architecture)
● Polyglot “Plus”
https://martinfowler.com/articles/microservices.html
https://martinfowler.com/bliki/MicroservicePrerequisites.html
@betoSalazar

10. The future
Java EE to Jakarta EE
Some History
Java EE 8
Ago 2017
Jakarta EE 8
Sep 2019
Jakarta EE 9
Dic 2020
Jakarta EE 10
Sep 2022
Jakarta EE 11
In progress

11. The Java Ecosystem
JavaEE & Jakarta EE
Ecosystem
And more ………………………..
Helidon

12. ¿How to move
forward?
Went out of the labyrinth of tech
frameworks / languages
and
innovation is slow.

13. @betoSalazar
Helidon
Lightweight.
Fast.
Crafted for Microservices

14. Helidon
Set of Java Libraries for Microservices
Small & Fast -> Ready to cloud

15. Helidon
Simple and Fast
Helidon Microprofile or Helidon SE
● Quickstart Demo

16. Helidon
Simple and Fast
Helidon SE
The server Http Functional Routes
https://github.com/lasalazarr/helidon-talk @betoSalazar

17. @betoSalazar
The Real World
Enterprise Applications
The real challenge

18. The reality
Legacy
systems business value.
successful architecture.
has
The result of
Reference: 97 Things Every Software Architect Should Know
there are among of code
== JEE Java EE
Jakarta EE

19. The reality
Few Years of code
Always the goal was to keep the modularization

20. The reality
Some Years of code
More code

21. The reality
Several Years of code
Base code

22. The reality
Java Enterprise Application
Hard to re write from the scratch

23. The reality
@betoSalazar

24. The reality
OMG
@betoSalazar

25. The reality
The solution ?
Cloud ? Kubernetes ? Microservices ? Serverless ?? Or …………??

26. Microservices ?
@betoSalazar

27. Split the backend
Helidon
SE
Also ready as
Docker
Container
Osgi container
engine-orchestrator.jar
Osgi container
dynamic-camel-routes.jar
fat jar
batch.jar
fat jar
services.jar
fat jar
business-module1.jar
fat jar
business-module-n.jar
Service
some api
Service
some api
Service
some api
Service
some api
Service
some api
Service
some api
businesslogic.jar
businesslogic.jar
businesslogic.jar
businesslogic.jar
businesslogic.jar
businesslogic.jar
The Monolith to Microservices

28. Microservices
Domain based services
@betoSalazar

29. It’s hard to trace the thread of execution in a
distributed system.
The experience
@betoSalazar

30. Eventual consistency ?
@betoSalazar

31. The reality
Type of actors
Different Perpectives

32. TIME
TO MARKET
VELOCITY
Sponsors perspectives
The goal that organizations need is to increase velocity & agility;
Get into production as soon as possible;
Projects under budget.

33. Developer perspectives
I just want to code !
Future tech stack, nothing old fashion or vintage

34. Tools perspectives
We are on a Great Era of Tools and Enablers for Software Development;
We have everything: Figma, Jira, Github, Slack, Cloud, Kubernetes, Istio,
Darp, Pipelines, DevOpsSec, and more ……

35. Methodology perspectives
Agile
Vs
Real World

36. Methodology perspectives
Agile Madness
https://dragonboat.io/blog/scaled-agile-framework/

37. Project perpectives
The new challenge
Workforce now with different Generations

38. Project perspectives
The tech are now easy but
The people are
In the process ……

39. Answers….???????
by @betoSalazar

40. @betoSalazar
Experience Gain
Tips and Tricks

41. But….I continue in my confort zone
or ……… I think out of the box
by @betoSalazar

42. and….get the best ideas of everybody at the team….
Listen & Listen

43. and….get the best of everybody at the team….
Every member of the team are different

44. How to Get Software Projects Done!
Digital transformation.
by @betoSalazar

45. Try
Fail

46. Take
care of
your
code

47. Real World Learnings
● Jakarta EE the foundation / Specification; all of
us with the Ecosystem / Frameworks are using
Jakarta EE
● Your Legacy code makes a valuable business
● AgiXXXXX Methodology != Get Projects done
● Always is the synergy and communication on
your team.
● Tools are enablers & Helidon is a great choice
● Fail faster
● The are not a fix recipe to success
by @betoSalazar

48. Insanity:
doing the same
thing over and
over again and
expecting
different results

49. THANK YOU !
@betoSalazar