Cloud native java are we there yet go tech world 2019

THE MASTER MIX
Peter Pilgrim
http://bit.ly/2cloudnativejava
1

Cloud native Java -
are we there yet?
The quest for the magical enterprise relevance diamonds
PETER PILGRIM
GO TECH WORLD - Bucharest, Romania - 2nd October 2019 - 14:30
PILGRIM ENGINEERING ARCHITECTURE TECHNOLOGY © 2019
2

@peter_pilgrim - http://bit.ly/2cloudnativejava
Your speaker today
➤ Independent Contractor
Blog: http://xenonique.co.uk/blog/
Twitter: @peter_pilgrim
Linkedin: http://linkedin.com/in/peterpilgrim2000
➤ PILGRIM ENGINEERING ARCHITECTURE TECHNOLOGY
3

Your speaker today
➤ Software developer, Java Champion
➤ Java EE technical author
➤ Development, Design and Architecture
➤ I normally contract with e-commerce clients
4

****Agenda****
Cloud Native
Java EE
Microservices
Kubernetes
Jakarta EE
Way Forward
7

Matt Stine
Pivotal
“Cloud-native is an approach to
building and running applications that
exploits the advantages of the cloud
computing delivery model.”
9

Adrian Cockcroft
VP Cloud Architecture Strategy at AWS, @adrianco
“Cloud native architectures take full
advantage of on-demand delivery,
global deployment, elasticity, and
higher-level services.”
10

Dianne Marsh
Director of Engineering, Netflix @dmarsh
Presentation Kubecon 2017 https://www.youtube.com/watch?v=mfFtfaulCtg
“The culture impacts the tech
And tech can impact the culture”
“... and we’re only just getting started”
11

Cloud Native Computing Foundation (CNCF)
official documentation https://github.com/cncf/toc/blob/master/DEFINITION.md
“Cloud native technologies empower
organizations to build and run scalable
applications in modern, dynamic
environments such as public, private, and
hybrid clouds.”
12

What do you need to
become Cloud-Native?
➤ Think of it as “Philia”, “attraction”, “affinity”
and “compatible”
➤ Appropriate technology choices:
○ Elasticity,High availability,
○ Distributed computing,
○ Resilience to failure
➤ Appropriate architecture
➤ Appropriate constraints
➤ Sensitivity to Conway’s Law
➤ Teamwork and THE THREE WAYS*
13

15
Programming environment available free for developers
Palo Alto, CA - January 23, 1996 - JavaSoft, the newly-formed
operating company of Sun Microsystems, Inc., today announced that the
Java™ 1.0 programming environment is now available for download at
http://java.sun.com.
"Java's write-once-run-everywhere capability along with its easy
accessibility have propelled the software and Internet communities to
embrace it as the de facto standard for writing applications for complex
networks," said Alan Baratz, JavaSoft's newly appointed president. "We're
delighted to invite developers to download Java 1.0 immediately and start
building the next killer application."
https://tech-insider.org/java/research/1996/0123.html

WORA
Write Once Run Anywhere: Java’s promise*
A broken promise for mobile, embedded and IoT devices since 2005
16

Biggest issue in 1995 to 2005 was the portability of code
➤ Windows, Mac OS X, Linux, UNIX (mainly C / C++)
➤ Embedded devices
Portability
17

Easy Networking
Java 1.0 had easy networking built-in
➤ Sockets, TCP and UDP support
➤ HTTP, HTML
18

Security
Java 1.x had notions of security
➤ Applet, Sandbox, Remote byte codes
➤ Virtual Machine (container)
19

Revolutionary features
1. Garbage Collection built-in - no malloc() or free()
2. Software Development Kit (SDK) - useful collection library
3. Reasonable built-in graphics library
20

Java == Technology + People + Context
Java is just a means to getting the result for stakeholders
Why are we building it?
What are we building?
How are we building it?
22

High performance teams
➤ Agile team - High performance trustworthy people with great belief
➤ Self reliant members - practicing proactive and empathic behaviours
➤ Egoless - story-centric led, democratic and co-operative
➤ Constant improvements - Small feedback loops in both tech and people
➤ Supportive and caring - every so often, personal circumstances will intervene
➤ Fun! - wind downs, regular lunch and/or evening event
23

24
Scale!
High availability!
Secure!

Cloud native - the technical challenges
On-demand
Flexible
Cost Effective
Sustainable
Reproducibility
Provisionable
Elasticity
Scale
Horizontally
Availability
Partition
Testable
Automation
Efficient
Manageable
Idempotent
Configurable
CI / CD
Pipelines
Measureable
Timely
Retrievable
Accountable
Node
Node
Node

26
Kubernetes
Kubernetes (K8s) is an open-source system for automating deployment,
scaling, and management of containerized applications.

27
2005 Application Server
(WebLogic, WebSphere, Tomcat, Resin, etcx)
2019 Orchestration Manager
(Kubernetes, Mesos, Openstack, IBM, Oracle, BYOCIMS*)

29
Mono
1
Mono
2
N
e
t
w
o
r
k
Corporate
Load
Balancer
Corporate
Database
The Old School
➤ Monolithic server with apps
➤ 1 Load balancer (round robin)
➤ 2 or 3 Federated servers (low volume)

30
N
e
t
w
o
r
k
The New School
➤ Micro Service Oriented Architecture M/SOA
➤ Orchestration (Kubernetes / Openshift)
➤ 200+ nodes (Fortune 500 companies 2019)

What did Java EE do for us?
Standards
JCP
JSR
Open JDK
Jakarta EE
Open Source
Source code
Tomcat
Hibernate
Spring Framework
Market Players +
Jobs
Employment
Contracts
Demand
Career
Social
Community
User Groups
Conferences
Commonality
Leadership
Node
Node
>

➤ The Servlet container - dynamic web content
○ Java Servlets => Tomcat
○ Java Server Pages (JSP) => dynamic web components
○ Java Server Faces (JSF)
○ Java RESTful API (JAX-RS)
○ Bean Validation
○ Context & Dependency Injection (CDI)
32

➤ The EJB container - container for poolable remotable functions
○ Java Messaging Service (JMS) => peer-to-peer, pub / sub messaging
○ Java Persistence => JPA and JDBC
○ Enterprise Java Beans (EJB) => local / remote endpoints
○ Transactions (JTS and JTA)
○ Asynchronous operations (almost free)
33

Java EE
PROS
➤ Elementary application containers (Servlet and EJB)
➤ Suitable for low and medium volume websites
CONS
➤ Lack of scalability (both horizontally and vertically)
➤ Hard to achieve High Availability (HA) with supreme high volume
34

Enter “container-less” JAR circa 2010
➤ Uber-JARs
➤ DIY Tomcat and Jetty embedded containers
➤ Work around System Administrators, Ops IT - WebLogic Servers
➤ Fine examples of so-called guerilla engineering
35

“Containerless” Java software
DropWizard
dropwizard.io
Vert X
vertx.io
Spring Boot
spring.io/projects/spri
ng-boot
Play
Framework
playframework.com

Social networking and high volume content
In the mid-2000, social networking exploded
Scale and high-availability (HA) became supremely important!
Monolithic architecture became cumbersome and overloaded
38

Josh Evans - Mastering Chaos - A Netflix Guide to Microservices
Former vice president of engineering at Netflix
“A microservice is this extreme
reaction to monolithic applications ...
it is an evolutionary approach to a
set of specific problems.”
39

Monolithic applications (Full Server)
Payara Full
Application Server
Oracle 11g
Database
Server
Network
Application EAR
JAR
WAR
40 40

Monolithic applications (Tomcat)
Apache Tomcat
(Web Profile)
Application
WAR
Oracle 11g
Database
Server
Network
41 41

Microservice application (Embedded Tomcat)
Standalone
Application
(JAR)
Embedded
Tomcat Server
Oracle 11g
Database
Server
Network
42 42

$ java -jar acme-inbound-emitter.jar
43

Microservices summary
An evolution response to monolithic applications
➤ separation of concerns - modularity, encapsulation
➤ scalability - horizontally scaling, workload partitioning
➤ virtualisation & elasticity - automated operations,
on-demand provisioning
44

45

Spring Boot
47
Spin off project from Spring Framework circa 2012
➤ Embedded Servlet container (Tomcat or Jetty)
➤ Spring Inversion-of-Control (IoC) style
➤ Spring RESTful service
➤ Spring Model View Controller (MVC)

Spring Boot
➤ Extended configuration using Java annotations
➤ Removed XML deployment and lifecycle configuration
➤ Uber-JAR
○ (WAR rebuilt into a single runnable JAR file)
48

Spring Boot
PROS
➤ Easy to understand
➤ Many Java EE developers already experienced (on-the-market)
➤ Just enough compatibility with Java EE to work
CONS
➤ Vendor lock-in
➤ Neither JAX RS or CDI are not supported (or ever will be)
49

Spring Boot
For enterprise Java developers, Spring Boot is the market leader
Each step to cloud-native services from Spring / Pivotal
➤ Spring Cloud
➤ Spring Reactive (WebFlux / Reactor) proposition
➤ Pivotal Cloud Foundry
However, see my recommendations later*
50

A quick example on
Spring Boot and PCF
51

PCF - Spring Boot Microservice #1
// /coderepo/acme-inbound-emitter/manifest-parent.yml
name: acme-inbound-emitter
buildpack: https://github.com/cloudfoundry/java-buildpack.git
memory: 2048M
instances: 3
path: ./build/libs/acme-inbound-emitter-4.5.6.jar
env:
JAVA_OPTS: -Djava.security.egd=file:///dev/urandom
52

// /coderepo/acme-inbound-emitter/manifest-development.yml
inherit: manifest-parent.yml
buildpack: java_buildpack_offline
services: [ acme-redis, acme-rabbit, acme-aws-s3, acme-ha-credentials,
acme-kafka-spike ]
env:
security.user.name: MrMagic
security.user.password: WhoCalledMe
api.cloudConfigService.uri: https://dev.digital.tech.acme.com
routes:
- route: dev.digital.tech.acme.com/inbound/transfer
- route: dev.digital.tech.acme.com/inbound/pay
53

@ComponentScan(
basePackages = {"com.acme.phoenix.inboundprocessor",
"com.acme.phoenix.batch"})
@EnableJpaRepositories(
basePackages = {"com.acme.phoenix.batch.repository",
"com.acme.phoenix.inboundprocessor.repository"})
@EntityScan(
basePackages = {"com.acme.phoenix.batch.domain",
"com.acme.phoenix.inboundprocessor.model"})
@SpringBootApplication
@AcmePaymentsRestClientApplication
public class InboundPaymentsEngineApplication {
public static void main(String[] args) {
SpringApplication.run(InboundPaymentsEngineApplication.class, args);
}
}
54

55
@Configuration()
/* ... */
public class AcmeInboundEmitterConfiguration {
/* ... */
@Autowired CloudLogService logService;
@Autowired CloudAuditService auditService;
@Autowired AnalyticEngine analyticEngine;
@Autowired SecurityGuardian securityGuardian;
// Kafka spike project
@Autowired EventStreamRouter eventStreamRouter;
}

@Configuration()
@Import({
AuditorConfiguration.class,
LoggingConfiguration.class,
S3FileStorageConfig.class,
SecureGuardianConfiguration.class,
WebUIConfiguration.class
})
/* ... */
public class AcmeInboundEmitterConfiguration {
/* ... */
}
56

@Configuration()
/* ... */
@EnableBinding({
EmitterResponseEndpoint.class,
InstructionMappingSource.class,
InvalidOutboundInstructionEndpoint.class,
JacksonConfiguration.class,
ProcessedInboundInstructionEndpoint.class
})
@IntegrationComponentScan
@EnableRetry
@EnableJpaAuditing(dateTimeProviderRef = "dateTimeProvider")
@EnableConfigurationProperties(AcmeInboundEmitterProperties.class)
@EnableInstructionMapperInstruction
public class AcmeInboundEmitterConfiguration { /* ... */ }
57

@RestController @RequestMapping("/api/payment-processor")
public class InboundProcessorRESTController
implements InboundProcessorServiceAPIClient {
@Autowired PaymentRecordRepository paymentRecordRepository;
@Override
@GetMapping("/getPaymentInfo/{storeId}/{customerId}")
public ResponseEntity<Instruction> getTopPaymentInfoPerCustomer(
@PathVariable("storeId") String storeId,
@PathVariable("customerId") String customerId) {
PaymentRecord paymentRecord =
paymentRecordRepository.findTopByStoreIdAndCustomerId(
paymentHubId, customerId);
// Do the work -- generate the JSON response
return ResponseEntity.create(...).build()
}
}
58

Deploy to the cloud! (PCF)
> gradlew clean assemble test
> cf login dev.digital.tech.acme.com
> cf target -o acme-5150 -s dev1
> cf push build/libs/acme-bank-emitter-4.5.6.jar
-f manifest-development.yml
59

Challengers in Java VM
platform development space
61
➤ Go language and ecosystem
➤ Node JS
➤ Python ML space
➤ Other vendor-lock solutions
○ AWS Beanstalk
○ Programming language specific solutions
○ etc

GO language and infrastructure
Why would a business look at Go Language?
➤ No persistent required - no database
➤ High concurrency function (Goroutines)
➤ Compile down to native machine code (stronger type safety)
➤ API gateway and service aggregation
➤ Fast startup and responsiveness
62

Node JS
Why would a business rely on NodeJS on the server side?
➤ Serverless - temporal flow - short-lived data for transformation
➤ Stateless - no conversational state
➤ Massive scale and density
➤ Data Analysis and Machine Learning
(e.g. Serverless / AWS Lambdas or Azure functions)
63

Are Java containers too bulky for some situations?
Serverless function (FaaS) architecture are examples
➤ Need taking over traditional Java development solutions
➤ TTM (Time To Market) and feature-fast delivery
➤ Experimental, flexible and exploratory architectures
Java (and JVM) is not necessarily the solution for all requirements
Companies are waking up to these new ideas
64

66
Cloud Infrastructure Types
Application
Middleware
Runtime
Networking
Storage
Virtualisation
SaaS
Application
Middleware
Runtime
Networking
Storage
Virtualisation
PaaS
Application
Middleware
Runtime
Networking
Storage
Virtualisation
IaaS
Cloud provider controls these features
You control this features
Data Data Data

Software as-a Service
67
➤ SaaS is hosted by cloud provider
○ primarily designed for the end-user
○ lowest infrastructure overhead and maintenance costs
○ Deliver over web content and/or RESTful API
➤ SaaS has limited configuration
○ DSL - domain specific language
○ User interface / experience branding
○ Plugins

Software as a Service (SaaS) examples
Salesforce
salesforce.com
Google Apps
apps.google.com
Office 365
office.com
Dropbox
dropbox.com

Platform as a Service
➤ PaaS abstracts a framework across the multiple cloud providers
➤ PaaS supports cloud-native developers with API:
○ Common scalability
○ High-availability (load balancers)
○ Message data queues and event processing I/O
○ Data resilience (failure over / service discovery / eventual consistency)
○ Adaptive databases with replication sets
➤ Some PaaS solutions in theory allow cloud-native portability
○ Migrate application from one cloud provider to another (exit plan)*
69

Platform as a Service (PaaS) examples
Heroku
heroku.com
OpenShift
apps.google.com
Pivotal
Cloud
Foundry
pivotal.io/platform
Fortune 500 businesses develop cloud-native applications using a PaaS

Infrastructure as a Service
Customer takes (full*) responsibility for infrastructure provisioning
➤ Elastic instances
➤ Network connectivity between nodes, subnets, security
➤ Load balancing, NATs, IGW, availability and (auto-)scalability
➤ Monitoring, metrics and alerts
➤ Application deployment and auto-restart
Cloud host provider is responsible for physical hardware availability
*Sometimes, this is untrue: infrastructure that delegate to an AWS Fargate on EKS is an example
71

Infrastructure as a Service (IaaS) examples
Google
Cloud
Platform
cloud.google.com
Microsoft
Azure
azure.microsoft.com
Amazon
Web Services
aws.amazon.com
Fortune 500 businesses develop cloud-native applications using a PaaS

Docker machine
Linux operating system
Java Virtual Machine
What is a container of a container of a container?
Application
(Embedded Server)
73 73

eu-west-2
AZ1
Orchestration of nodes, clusters and virtual private clouds
AZ2
E*
74

External Container Technology
➤ Docker: the de-facto successful implementation of
containerisation technology, packaging of apps, libraries & OS
➤ Docker composition enables quick assembly, fast deployment
➤ Docker processes means that restarts are cheap.
○ (Okay, we need to throw in some Kubernetes in there!)
Whole premise of a redeployment of WAR and EAR files is gone!
75

76
Introduction to Kubernetes
(K8S)
➤ Kubernetes orchestrates containers
➤ Containers are Docker instances
➤ Support multiple cloud and bare-metal
environments
➤ A Greek term for “ship’s pilot” or
“helmsman”
➤ Google first create Borg and K8S is a
second version implementation
(vis-a-vis Fred Brooks)
➤ Kubernetes is open source and written
in the Go language

Key features of Kubernetes
➤ Elasticity support with horizontal scaling (automatic and manual)
➤ Resilience
➤ Automatic restart
➤ Scheduling across host providers
➤ Built-in load balancer
➤ Rolling upgrades (clever namespacing)
77

Namespace
➤ Method to
cluster for
environment
➤ Authorisation
➤ Policy
management
➤ Naming of pod
clusters
Kubernetes Terminology
Pod
➤ Managed
lifecycle
➤ Docker
Containers 1+
➤ Shared IP
➤ Same host
(AWS EC2
instance)
Label
➤ Annotation
principle
➤ Key-value
pairs for
Kubernetes
objects
➤ Enabler for
Blue / Green
deployments
Replica Set /
Deployment
➤ Replication
controller
➤ Desired
instance count
➤ Health check
➤ Management
of pods
➤ Load balancer
Persistent
Volume
➤ Network
available
storage
➤ Single or
multiple node
clusters

79
Pod
Container
JVM
Service A
Metrics
Discovery
Monitoring
Fault
Tolerance
Pod
Container
JVM
Service C
Metrics
Discovery
Monitoring
Fault
Tolerance
Pod
Container
JVM
Service B
Metrics
Discovery
Monitoring
Fault
Tolerance

Learn Kubernetes on your local workstation
Localhost development with Minikube (https://kubernetes.io/docs/tasks/tools/install-minikube/ )
Pros:
➤ Tool make your PC a single-node Kubernetes cluster
➤ Open source tool: Linux, Mac OS and Windows
➤ Lean and experiment - practice kubectl command line
➤ Proof of concept - evaluate advance extension features
Cons:
➤ Features that require multiple-node will not work in Minikube
brew cask install minikube
80

Learn Kubernetes from only one provider to learn all
Once you learn it, you can run it on any cloud provider
➤ GKE from Google Cloud Platform
➤ AKS from Microsoft Azure
➤ EKS from Amazon Web Services
81

Kubernetes CLI
Learn kubectl (Kubernetes control admin tool) from CLI
> kubectl get namespaces
> kubectl get pods -n peatspace
> kubectl run peatboot --image=peat/peatboot --port=8080
> kubectl logs peatboot-qz794
82

Whilst the Java EE world was in conflict,
the rest of us continued life with the
cloud-native DEV-OPS inspired evolution
...
84

85
The Phoenix Project - Kim, Behr & Spafford *2014

The Three Ways - Phoenix Project
86
➤ Enable fast left-to-right flow
○ from Development to Operations IT to Customer
➤ Enable fast, coherent and constant feedback
○ Create quality at source, embed knowledge & achieve safety
➤ Enable high-trust people culture
○ Scientific approach to experimentation and organisation learning

Dr. Venkat Subramanian
Author, Developer and Professor
“Java was born in a perfect storm”
“I’m betting on Java being one of the most
vibrant languages for asynchronous
programming.”
88

Jakarta EE 8 - Highlights
➤ https://jakarta.ee/
➤ Open-Source Cloud-Native Java
➤ Full compatibility with Java EE 8
➤ Open TCK
○ Licenses
○ Processes
➤ Active community
90

Microprofile and Jakarta EE
➤ Oracle reacted to the industry concern 2016
➤ Community created the Microprofile project 2016
➤ Oracle donated the Java EE to Eclipse Foundation 2017
➤ Eclipse Foundation created the Jakarta EE brand 2018
➤ Oracle transferred the intellectual property to Eclipse 2018
➤ 39 Source code repos and TCK transferred to Eclipse 2018
91

Jakarta EE and Microprofile status
➤ Oracle rush-released Java EE 8 in October 2017
➤ Eclipse Foundation only released Jakarta EE 8, September 2019
➤ Microprofile V3.0 released in July 2019
92

No change since last release v2.2
93
Open Tracing
(Swagger) 1.3
Open API
(Logging) 1.1
REST Client 1.3 Configuration 1.3
Fault Tolerance
(circuit breaker) 1.3
Metrics 2.0
JWT Propagation
(security) 1.1
Health Check 2.0
CDI 2.0 JSON-P 1.1 JAX-RS 2.1 JSON-B 1.0
New in v3.0

94
Open Tracing
(Swagger) 1.3
Open API
(Logging) 1.1
Fault Tolerance
Metrics 2.0
JWT Propagation
(security) 1.1
Health Check 2.0
New in v3.0
Is this impressive progress enough for
developers, designers, architects and DevOps?

Microprofile developer job adverts:
where are they?*
95
*On the 24th September 2019, I checked UK contract and permanent job hunting sites: jobserve.com,
cwjobs.com, totaljobs.com and indeed.com/uk. I found 0 jobs advertising Microprofile or Jakarta EE
technologies

Reactive
Programming
➤ Standardise
RXJava /
Reactor
➤ Oracle already
researching
Fibers
Jakarta EE - possible ways forward
Modularity
➤ Remove EJB
container
➤ Delivery
modular
specifications
➤ Abstract
Dependency
Injection
➤ Gather input
from Spring
Boot team
APIs
➤ Gain NoSQL
support
➤ Lambdas first
class citizens
➤ Standardise
event queue /
stream
(Kafka)
➤ Improve Java
➤ Watch Kotlin
Containerless
➤ Overdue
standard API
for Embedded
containers
➤ Standard JAR
file format
➤ Docker
container
metadata
Infrastructure
➤ Cloud
Provider
Bindings
➤ Single or
multiple node
clusters
➤ Discuss with
the CNCF

98
Open Tracing
(Swagger) 1.3
Open API
(Logging) 1.1
Fault Tolerance
Metrics 2.0
JWT Propagation
(security) 1.1
Health Check 2.0
New in Microprofile v3.0
NoSQL*
Event
Streaming*
Orchestration
Metadata (IaC)*
Serverless
(FaaS)*
My Preferences / My Wishlist*

IMHO Jakarta EE requires
➤ Standard Embedded Server Server API
○ Easy-to-use provisioning, execution and monitoring
➤ Standard Testing Framework
○ Seamless concise, easy-to-use and build standard testing
○ Acknowledge testing pyramid best practice
➤ Distributed Streaming - improved messaging semantics
○ talk with Kafka community and others
99

Jakarta EE must consider DevOps, be cloud aware
➤ Needs to be Cloud Environment aware
○ Where am I running? Docker, AWS, PCF
➤ Cloud metadata support
○ Talk with folk responsible for Docker, Kubernetes and PCF
➤ Infrastructure as Code Support
○ Talk with Hashicorp: Terraform, Vault; Ansible, etc
100

Jakarta EE support for alternative Java languages
Late 2019, but these are really nice-to-haves:
➤ Look at the growth of Kotlin especially DSL support
➤ Seriously, take advantage of Java 8 Lambdas!
➤ Add support Java 8 Streams, finally and go reactive
○ Look at RX Java and Spring Reactor framework e.g. Mono, WebFlux
➤ Keep abreast of whatever Brian Goetz is adding to Java!
101

Graal VM - The Future Now
Imagine that? Writing a VM in Java, what? Are you crazy?
102

Future Cloud-Native Java
Graal VM
graalvm.org
Next generation
Universal VM
Polyglot languages
JVM and non-JVM
JIT compilation
Native code
Quarkus
quarkus.io
Kubernete Native
JVM stack
Built-on Graal VM
Fast boot times
FN Project
fnproject.io
FaaS compute
platform
Multiple cloud
providers
Serverless
Docker support
Helidon
helidon.io
Reactive web server
Based on Netty
Microprofile support
Micro framework

(J)VM startup-time now is a thing (it matters)
Generate native images from Java*
Container complexity will increase
Container density will increase
105*or from Kotlin, Scala and your favourite alternative JVM language

Summary
➤ Cloud Native
➤ Java EE
➤ Microservices
➤ Cloud infrastructure
➤ Kubernetes
➤ Way forward for Enterprise Java
106

Where Do You Go Next?
➤ Get behind Jakarta EE and keep pushing
➤ Push one cloud-native app to the host
➤ Learn Kubernetes and orchestration
➤ Learn alternative languages such as Kotlin, Scala or Groovy
➤ Checkout the Graal VM platform
➤ Stay Free*
*Song title from The Clash, album Give ‘em Enough Rope
https://en.wikipedia.org/wiki/Give_%27Em_Enough_Rope
107

A West African proverb - anonymous griots
“However long the night,
the dawn will break”
108

Thank You!
xenonique.co.uk/blog/
@peter_pilgrim
201910021430
109

Shout outs and digital image attribution - Thank you!!!!
110
First, shout out to my partner in creative crime and life Terry Neason, singer,
chartreuse and diva: terryneason.co.uk and presentation tlcpowertalk.co.uk
Second, a shout to the amazing Negative Space. o/
Fantastic stock images https://negativespace.co/collection/autumn/
Dog. I got you!
Shout out to the following digital image photographers:

Cloud native java are we there yet go tech world 2019

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Cloud native java are we there yet go tech world 2019

Similar to Cloud native java are we there yet go tech world 2019 (20)

More from Peter Pilgrim

More from Peter Pilgrim (14)

Recently uploaded

Recently uploaded (20)

Cloud native java are we there yet go tech world 2019