The document presents insights on cloud-native microservice implementation using Helidon, a set of Java libraries designed for developing microservices. It covers important aspects such as principles of cloud-native development, the architecture of Helidon, and its integration with GraalVM for optimized performance. The presentation emphasizes the advantages of cloud-native apps, including scalability, flexibility, and lower costs, while also discussing the role of MicroProfile in enhancing enterprise Java for microservices.

1. © OPITZ CONSULTING 2019
¢¢¢ Digitale Service Manufaktur
© OPITZ CONSULTING 2019
Sven Bernhardt, Senior Solution Architect
Cloud-Native
Microservice
Implementation

2. © OPITZ CONSULTING 2019 Seite 2
Agenda
1
2
3
4
5
Cloud-Native apps development
Helidon overview
Helidon Deep-Dive
Helidon & GraalVM
Conclusion
Cloud-Native Microservice implementation using Helidon

3. © OPITZ CONSULTING 2019 Seite 3
Cloud-Native apps development
1
Cloud-Native Microservice implementation using Helidon

4. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 4
Why should I care about Cloud-Native development?
¢ Cloud is a competitive advantage (if used the right way)
¢ Increased speed / idea-to-market
¢ Increased scalability
¢ Increased flexibility
¢ Lower total cost of ownership (CAPEX à OPEX)

5. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 5
Characteristics of Cloud-Native applications
CNCF Definition of Cloud-Native:
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.
These techniques enable loosely coupled
systems that are resilient, manageable, and
observable. Combined with robust automation,
they allow engineers to make high-impact
changes frequently and predictably with
minimal toil.
Source: https://github.com/cncf/toc/blob/master/DEFINITION.md

6. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 6
Cloud-Native is an approach to build and run
applications that fully leverage the advantages of Cloud
Data
Single
Deployment
Unit
Traditional app development approach Cloud-native app development approach
UI
Logic
Data Access
UI
Logic
API
Data
UI
Logic
API
Data
Single
Deployment
Unit
Single
Deployment
Unit

7. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 7
Principles for Cloud-Native app development: 12-factor
app
¢ Codebase - One Codebase Tracked in
Version Control, Many Deploys
¢ Dependencies - Explicitly Declare and
Isolate Dependencies
¢ Config - Store Config in the Environment
¢ Backing services - Treat Backing
Services as Attached Resources
¢ Build, Release, Run - Strictly
Separate Build and Run Stages
¢ Processes - Execute the App as One or
More Stateless Processes
¢ Port binding - Export Services via Port
Binding
¢ Concurrency - Scale Out via the
Process Model
¢ Disposability - Maximize Robustness
With Fast Startup and Graceful Shutdown
¢ Development/Production
Parity
¢ Logs - Treat Logs as Event Streams
¢ Admin processes - Run
Admin/Management Tasks as One-off
Processes

8. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 8
Maturity model for Cloud-Native applications
• Microservices architecture
• API-first design
• Fault-tolerant and resilient design
• Cloud-agnostic runtime implementation
• Bundled metrics and monitoring
• Proactive failure testing
• 12 Factor App methodology
• Horizontally scalable
• Leverages platform for high availability
• No permanent disk access
• Self-contained application
• Platform-managed ports and networking
• Consumes platform-managed backing services
Cloud Native
Cloud Resilient
Cloud Friendly
Cloud Ready

9. © OPITZ CONSULTING 2019 Seite 9
Helidon overview
2
Cloud-Native Microservice implementation using Helidon

10. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 10
Helidon – Set of Java libraries for developing µServices
¢ Open Source
¢ Hosted on Github (https://github.com/oracle/helidon)
¢ Support via Slack (https://helidon.slack.com)
¢ Apache 2.0 license
¢ Supported active project
¢ Innovative
¢ Supports standards
¢ Microprofile 2.2 & 3.0

11. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 11
µService frameworks landscape
Dropwizard

12. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 12
Core differences Helidon SE and Helidon MP
¢ Microframework
¢ Tiny Footprint
¢ Functional style
¢ Reactive
¢ Simple & transparent
¢ GraalVM Native Image
¢ Microprofile 2.2 / 3.0 conform
¢ Small footprint
¢ Declarative style
¢ Dependency Injection
¢ Java EE specs: CDI, JAX-RS, JSON-
P/B

13. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 13
Helidon architecture
Netty
Helidon SE
WebServer Config Security
Helidon MP
CDI JAX-RS JSON- P/B
Extension

14. © OPITZ CONSULTING 2019 Seite 14
Helidon Deep-Dive
3
Cloud-Native Microservice implementation using Helidon

15. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 15
Simple, functional & lightweight µFramework
¢ Developed in a modern, reactive way
¢ No injection magic used
¢ No special runtime needed; JDK used as default runtime
Reactive Web
Server
Health Check gRPC
Config Metrics Reactive DB Client
Security Tracing

16. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 16
Helidon SE core components
Reactive Web Server
¢ Simple, functional routing
model with reactive flow API
¢ Built on Netty
¢ OpenTracing, Metrics &
HealthChecks
¢ JAX-RS, JSON-P Support
¢ Static content support
Config
¢ Flexible, typed config model
¢ Multiple data sources
¢ Multiple formats
¢ Hierachical model
¢ Dynamic updates
¢ Extensible
Security
¢ Authentication
¢ Authorization
¢ Outbound Security
¢ Auditing
¢ Built-in Providers
¢ Extensible

17. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 17
Microprofile: Optimizing Enterprise Java
for a Microservices Architecture
¢ Open Source community spec for Enterprise Java µService
¢ Hosted at Eclipse Foundation
¢ Participants: Oracle, IBM, Microsoft, Red Hat, Payara and others
¢ Advantages:
¢ Community-driven
¢ Lightweight, iterative apporach
¢ No reference implementation, just Specs and APIs
¢ Links:
¢ https://microprofile.io
¢ https://start.micorprofile.io

18. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 18
Helidon MP core components
¢ Helidon supports Microprofile 3.0 spec
Open Tracing Open API REST Client
Fault Tolerance Metrics
CDI JSON-P
gRPCMP Config
JWT Auth JPAHealth Check
JAX-RS JTAJSON-B

19. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 19
Frameworks Extensibility: CDI Extensions
¢ Extensions in Helidon are based on CDI
¢ Extensions are available to be used with Helidon MP
¢ Currently there are Extensions for:
¢ HikariCP data sources
¢ Oracle Univerrsal Connection Pool (UCP) data sources
¢ Jedis Client
¢ Oracle Cloud Infrastructure (OCI) Object Storage clients
¢ Java Transaction API (JTA)
¢ Java Persistence API (JPA)

20. © OPITZ CONSULTING 2019 Seite 20
Demo Helidon SE & MP
Cloud-Native Microservice implementation using Helidon

21. © OPITZ CONSULTING 2019 Seite 21
Helidon & GraalVM
4
Cloud-Native Microservice implementation using Helidon

22. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 22
GraalVM
¢ High performance polyglot VM
¢ Built on the global standard JavaSE
¢ Components
¢ GraalVM Compiler
¢ GraalVM Native Images
¢ Polyglot capabilitites (Node, Ruby, R and Python)
¢ LLVM Interpreter (C, C++)
¢ Language implementation framework

23. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 23
GraalVM architecture

24. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 24
GraalVM Native image – Optimized, native executbale
for the respective target plattform
¢ Advantage of GraalVM Native image:
¢ Shorter startup time
¢ Lower memory footprint
¢ Reduced container image size
¢ Helidon supports two profiles
¢ Local profile
¢ Docker profile

25. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 25
GraalVM Native image limitations
¢ Dynamic class loading
¢ Reflection
¢ Dynamic Proxy
¢ Java Native Interface (JNI)
¢ Unsafe Memory Access
¢ Class Initializers
¢ Invoke Dynamic Bytecode / Method
Handlers
¢ Lambda Expressions
¢ Synchronized, wait and notify
¢ Finalizers
¢ References
¢ Threads
¢ Identity Hash Code
¢ Security Manager
¢ JVMTi, JMX or other native VM
interfaces
¢ JCA Security Services
Source: https://github.com/oracle/graal/blob/master/substratevm/LIMITATIONS.md

26. © OPITZ CONSULTING 2019 Seite 26
Demo Helidon & GraalVM
Cloud-Native Microservice implementation using Helidon

27. © OPITZ CONSULTING 2019 Seite 27
Conclusion
5
Cloud-Native Microservice implementation using Helidon

28. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 28
Why should I care about Microprofile or frameworks like
Helidon for µServices development?
¢ Complete, gigantic ecosystem
¢ Provides features in form of
implemented libraries
¢ Supports features like:
¢ Service Discovery
¢ Loadbalancing
¢ Integration with Monitoring systems
¢ Just describes a Standard
¢ Set of APIs and specs without a
specific reference implementation
¢ Focus on implementing business
functionality
¢ More infrastructure-related stuff is
not supposed to be handeled by
the µService implementation

29. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 29
Spring Boot and Microprofile are not that disparate!
¢ Example: REST-capabilities in comparison
¢ Getting started:
¢ Additional areas that are covered similarly, e.g. Resiliency and Operations
REST Service Spring MVC JAX-RS
Dependency Injection Spring IoC & DI CDI
API Documentation Spring REST Docs MP Open API
REST Client Spring MVC Feign MP REST Client
JSON Binding / Processing BYOL (Jackson) JSON-P / JSON-B
https://start.microprofile.io/https://start.spring.io/

30. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 30
Do we again have a Spring vs. Java EE discussion?
¢ NO!
¢ Which framework to choose highly depends on
¢ Use case
¢ Infrastructure
¢ People
¢ Application landscapes are more homogeneous, e.g. communiation
happens using standardized protocols (HTTP)
¢ µServices are isolated from each other
¢ Implementation techology does not matter
¢ Team decision
¢ „You built it, you run it!“

31. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 31
Is Helidon worth looking into it?
¢ Definitely!
¢ One framework, two flavours, many use cases
¢ Flexible, extensible framework (CDI Extensions)
¢ Easy to getting started
¢ Active community (Slack, Stackoverflow, FAQ)
¢ If needed, professional support from Oracle

32. © OPITZ CONSULTING 2019 Seite 32
Q & A
Cloud-Native Microservice implementation using Helidon

33. © OPITZ CONSULTING 2019 Cloud-Native Microservice implementation using Helidon Seite 33
Materials / Resources
¢ Website: Pivotal Cloud-Native
¢ Website: Helidon.io
¢ Website: Microprofile
¢ Presentation, Dmitry Kornilov: Developing Cloud-Native µServices using
Project Helidon
¢ Presentation , Dmitry Kornilov: Building Cloud-Native applications with
Helidon
¢ Helidon presentations Oracle Code One 2019
¢ Helidon Tutorial, Peter Nagy

34. © OPITZ CONSULTING 2019
¢¢¢ Digitale Service Manufaktur
@OC_WIRE
OPITZCONSULTING
opitzconsulting
opitz-consulting-bcb8-1009116
WWW.OPITZ-CONSULTING.COM
Seite 34
Thanks for your attention!
Sven Bernhardt
Senior Solution Architect | Oracle ACE Director
OPITZ CONSULTING Deutschland GmbH
Kirchstrasse 6, 51647 Gummersbach, Germany
Phone: +49 172 2193529
Mail: sven.bernhardt@opitz-consulting.com
@sbernhardt
https://svenbernhardt.wordpress.com
Cloud-Native Microservice implementation using Helidon