Architecting and delivering Java applications in the cloud era

Slide 1

Slide 1 text

Otavio Santana @otaviojava Architecting and delivering Java applications in the cloud era Karina Varela @kvarel4

Slide 2

Slide 2 text

Otavio Santana @otaviojava DevRel Engineer + Java Champion + JCP-EC-EG-EGL + Apache Committer + Eclipse Committer + Eclipse Project Leader + Book and blog writer Speaker

Slide 3

Slide 3 text

Karina Varela @kvarel4 Senior Technical Marketing Manager + KIE Contributor + MOTU Tech Founder + SouJava Organizer + Instructor + Book and blog writer Speaker

Slide 4

Slide 4 text

Cloud Origins, Why and How

Slide 5

Slide 5 text

● Individuals and interactions over processes and tools ● Working software over comprehensive documentation ● Customer collaboration over contract negotiation ● Responding to change over following a plan Agile

Slide 6

Slide 6 text

● DevOps ○ NoOps ● BizDevOps Breaking down the silos Great wall of China

Slide 7

Slide 7 text

"Cloud is somebody else's problem" Cloud Jacob Peter Gowy's The Flight of Icarus (1635–1637)

Slide 8

Slide 8 text

Concepts

Slide 9

Slide 9 text

Some of the options Cloud PaaS IaaS CaaS SaaS Managed Application Services Managed Event Streaming Managed Database Managed API Gateways Managed Integration Decisions and Processes as a Service Backend as a Service (serverless)

Slide 10

Slide 10 text

Cloud Native Applications

Slide 11

Slide 11 text

“Cloud-native is an approach to building and running applications that exploits the advantages of the cloud computing model.” Cloud Native

Slide 12

Slide 12 text

“Cloud-native is a different way of thinking and reasoning about software systems. It embodies the following concepts: powered by disposable infrastructure, composed of bounded, scales globally, embraces disposable architecture.” Cloud Native

Slide 13

Slide 13 text

“In general use, ‘cloud-native’ is an approach to building and running applications that exploits the advantages of the cloud-computing delivery model. ‘Cloud-native’ is about how applications are created and deployed, not where.” Cloud Native

Slide 14

Slide 14 text

“Independent DURS ultimately comes up in every discussion on cloud-native concepts; to independently Deploy, Update, Replace and Scale.” Cloud Native

Slide 15

Slide 15 text

“Cloud-native is more than a tool set. It is a complete architecture, a philosophical approach for building applications that take full advantage of cloud computing.” Cloud Native

Slide 16

Slide 16 text

“Cloud-native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach.” Cloud Native

Slide 17

Slide 17 text

Cloud-native is a term used to describe container-based environments. Cloud Native

Slide 18

Slide 18 text

A set of good practices to optimize an application in the cloud through: ● Containerization ● Orchestration ● Automation Cloud Native

Slide 19

Slide 19 text

Cloud Native Trends Cloud Cloud Ready Cloud Friendly Cloud Native

Slide 20

Slide 20 text

Java is too heavy for the cloud

Slide 21

Slide 21 text

Java, Jakarta EE and Microproﬁle

Slide 22

Slide 22 text

● Optimizations on GC ● Improvements Containers ● Better Integration ● Release 6 months Java

Slide 23

Slide 23 text

● Eclipse Foundation ● Agile - Yearly deliveries ● Cloud Native Jakarta EE

Slide 24

Slide 24 text

● Microservices ● Eclipse Foundation ● Agile- Quarterly releases ○ Fast Delivery Eclipse MicroProﬁle

Slide 25

Slide 25 text

● Jakarta EE8 ● Security ● Fault Tolerance ● Much more... Eclipse Foundation

Slide 26

Slide 26 text

Java ecosystem

Slide 27

Slide 27 text

● Native ● Serverless ● GC ● JIT vs AOT Native image Hardware ISA SO JVM App Hardware ISA SO App

Slide 28

Slide 28 text

Orchestration vs Choreography

Slide 29

Slide 29 text

Independent services… involved in a same business ﬂow

Slide 30

Slide 30 text

Multiple endpoint to endpoint communication?

Slide 31

Slide 31 text

Choreography

Slide 32

Slide 32 text

Event-driven Choreography Sam Newman

Slide 33

Slide 33 text

New order created Services

Slide 34

Slide 34 text

1. New order created 2. New order created, process payment Services

Slide 35

Slide 35 text

1. New order created 3. See new paid order event, Start execution 2. New order created, process payment Services

Slide 36

Slide 36 text

1. New order created 3. See new paid order event, Start execution 4. Execution done. 2. New order created, process payment Services

Slide 37

Slide 37 text

1. New order created 3. See new paid order event, Start execution 4. Execution done. 2. New order created, process payment Order executed, start shipment Services

Slide 38

Slide 38 text

Broker Services Choreography Subscribe / Publish Subscribe / Publish

Slide 39

Slide 39 text

Orchestration

Slide 40

Slide 40 text

Traditional Service Orchestration

Slide 41

Slide 41 text

Automating Business Flows

Slide 42

Slide 42 text

Services Orchestration Business Processes + Integration with (Micro)Services

Slide 43

Slide 43 text

Event-driven solutions

Slide 44

Slide 44 text

CI/CD

Slide 45

Slide 45 text

Continuous Integration Commit Code Frequently Don't Commit Broken Code At every change: ↪ Build your... software ↪ Build your... database ↪ Run your tests Fix Broken Builds Immediately Write Automated Developer Test All tests must pass

Slide 46

Slide 46 text

Continuous Delivery / Deployment

Slide 47

Slide 47 text

DevOps With Containers Across the Hybrid Cloud? Source Repository CI/CD Engine Dev Container Physical Virtual Private cloud Public cloud

Slide 48

Slide 48 text

Best Practices Java

Slide 49

Slide 49 text

● Codebase ● Dependencies ● Config ● Backing services ● Build, release, run ● Process ● Port binding ● Concurrency ● Disposability ● Dev/prod parity ● Logs ● Admin processes The 12 Factors App

Slide 50

Slide 50 text

Old but Gold

Slide 51

Slide 51 text

“Certainly, we always read great things about the microservices architectures implemented by companies like Netﬂix or Amazon. So let me ask a question: how many companies in the world can be Netﬂix and Amazon?” Microservices Conway's law

Slide 52

Slide 52 text

Best Practices For Java + Containers

Slide 53

Slide 53 text

Container engines ● Know the options: ○ Standard: Open Containers Initiative (OCI) ● Team Skills ( Concepts and tool - basics ) ● Will you work with containers locally, during the development? ● Adding tests for your app, within the container ( i.e. Testcontainers )

Slide 54

Slide 54 text

Container engines ● During the image build time: ○ Single Concern Principle ○ Self-Containment Principle ○ Image Immutability Principle

Slide 55

Slide 55 text

Container engines ● During the container runtime: ○ High Observability Principle ○ Lifecycle conformance principle ○ Process disposability principle ○ Runtime conﬁnement principle