Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à A fun cup of joe with open liberty
Similaire à A fun cup of joe with open liberty (20)
Dernier
Dernier (20)
A fun cup of joe with open liberty
- 1. 1 A Fun Cup of Joe with Open Liberty Andrew Mauer ajmauer@us.ibm.com
- 2. 2 Let’s start with some fun … http://ibm.biz /liberty-bikes
- 4. 4 6 reasons why Open Liberty Just enough runtime Low operating cost Continuous delivery Zero migration Kubernetes optimized 80% disk and 56% memory saving 4x increased density over Tomcat & Spring Boot Zero-effort security fixing & zero technical debt 100% v2v & fixpack migration saving Self-tuned optimal perf, production-ready, kube-native Developer experience Container & kube-native experience, rapid inner loop Lightweight, highly- efficient runtime CI/CD-optimized operational experience Simple true-to- production developer experience
- 5. 5 What people are saying • "Light operation and efficient operation (restart time can be reduced compared to ND)” • "Ease of use small footprint ability to be built into a container” • "It's the best tool for the job.” • "Easy to manage, Cloud Ready a Smart Product with cool feature. Modular flexible and fast.” • "Simple, well supported, cloud and container friendly.” • "Liberty is a fast-to-configure application server with some advantages over other similar products.” • "Simplicity of use.” • "Now that we have experienced Liberty, we are spoiled and want to stick to those easy, non-impacting migrations."
- 6. 6 <feature>servlet-4.0</feature> <feature>jaxrs-2.1</feature> Kernel • You control which features are loaded into each runtime instance Just Enough Runtime jsonp-1.1 servlet- 4.0 http-2.0 appmgr Java EE jaxrs-2.1 jaxrsClien t-2.1
- 7. 7 Simple Config <server> <featureManager> <feature>jaxrs-2.1</feature> </featureManager> <webApplication location=“myweb.war” contextRoot=“/” /> <applicationManager autoExpand="true"/> </server> server.xml -Xmx1g -Dsystem.prop=value jvm.options WLP_OUTPUT_DIR=/usr/wlp-out/ server.env
- 8. 8 API Support • First shipped in WAS 8.5 in 2012 o Servlet + JSP + JPA • Web Profile 6 in 2014 • Java EE 7 in 2016 – first commercial product to certify • Java EE 8 in 2018 – first to certify • Jakarta EE 8 in 2019 – first to certify • Eclipse MicroProfile – first to deliver 1.0-1.4, 2.0-2.1, 3.0, 4.1 • Jakarta EE 9 – first vendor product to certify
- 9. 9 Jakarta EE or Java EE 8 appSecurity-3.0 jaxrs-2.1 jsonp-1.1 websocket-1.1 beanValidation-2.0 jaxrsClient-2.1 jsf-2.3 cdi-2.0 jdbc-4.2 jsp-2.3 ejbLite-3.2 jndi-1.0 managedBeans-1.0 el-3.0 jpa-2.2 servlet-4.0 jaspic-1.1 jsonb-1.0 ssl-1.0 appClientSupport-1.0 ejbHome-3.2 jacc-1.5 managedBeans-1.0 appSecurityClient-1.0 ejbPersistentTimer-3.2 jaxb-2.2 mdb-3.2 batch-1.0 ejbRemote-3.2 jaxws-2.2 wasJmsClient-2.0 concurrent-1.0 j2eeManagement-1.1 jca-1.7 webProfile-8.0 ejb-3.2 javaMail-1.6 jms-2.0 wmqJmsClient-2.0 Full Jakarta EE 9 Compatibility in Beta too!
- 11. 11 Health Check Metrics Fault Tolerance OpenAPI Config Open Tracing JWT JSON-B Rest Client CDI JAX-RS JSON-P Core Reactive Messaging Integrate Observe GraphQL Open Telemetry https://microprofile.io/ Open cloud-native Java APIs
- 12. 12 Spring Boot <featureManager> <feature>springBoot-2.0</feature> <feature>servlet-4.0</feature> <feature>websocket-1.1</feature> </featureManager> <springBootApplication location=“spring-petclinic-angular1 -2.0.0.jar /> 2018-07-10 20:55:32.739 INFO 1 --- [ecutor-thread-2] o.s.j.e.a.AnnotationMBeanExporter : Located MBean 'dataSource': registering with JMX server as MBean [com.zaxxer.hikari:name=dataSource,type=HikariDataSource] 2018-07-10 20:55:32.766 INFO 1 --- [ecutor-thread-2] o.s.s.petclinic.PetClinicApplication : Started PetClinicApplication in 21.042 seconds (JVM running for 28.16) [AUDIT ] CWWKZ0001I: Application Spring Boot application started in 23.782 seconds. [AUDIT ] CWWKF0012I: The server installed the following features: [jsp-2.3, springBoot-2.0, servlet- 3.1, ssl-1.0, transportSecurity-1.0, websocket-1.1, el-3.0]. [AUDIT ] CWWKF0011I: The server defaultServer is ready to run a smarter planet.
- 13. 13 API needs for the continuum of architectural styles Architectural style Functions Monolith Microservice API needs Smaller Larger Macroservice Liberty tWAS/JBoss Quarkus
- 14. 14 Liberty Zero Migration • Zero config migration - Write once, run forever • Zero app migration - No behavior changes in existing features - New behaviors in new features • Choose your Java - Java 14, 11, 8 - AdoptOpenJDK or Eclipse Adoptium - IBM Semeru Runtimes - OpenJDK - Oracle
- 16. 16 Developer needs • APIs to solve microservice use cases • Work with editor of choice • Fast ‘inner-loop’ experience • Work with build technology of choice • Integrate well with DevOps infrastructure • Simplify development for Containers & Kubernetes
- 17. 17 Fast iteration with dev mode • Boosts developer productivity • Immediate feedback for code and config changes • No re-build necessary • Hot deployment, testing and debugging • In containers for near-production testing mvn liberty:dev gradle libertyDev mvn liberty:devc gradle libertyDevc
- 18. 18 Tools • Open Liberty Tools for VS Code, IntelliJ & Eclipse • Start/Stop server • Run tests • View test reports • MicroProfile Starter • Create a new custom microservice project within the IDE • MicroProfile REST Client Generator • Generate a REST client based on an OpenAPI definition
- 19. 19 Developer productivity Repositories Build IDEs Dev Mode APIs Testing
- 20. 20
- 23. 23 Liberty in Containers Azure Kubernetes Service IBM Cloud Kubernetes Service Amazon Elastic Kubernetes Service Jelastic Google Kubernetes Engine Hosted Cloud Red Hat Open Shift Container Platform Pivotal Kubernetes Service Pivotal Cloud Foundry Private Cloud app and config liberty and java docker + + os config + FROM open-liberty ADD myapp.war /config/dropins/myapp.war = portable container
- 24. 24 Making the most of Docker O/S JVM App Server Application O/S JVM Application thin war fat jar
- 25. 25 25 Kubernetes optimized • Deliver faster without costly tuning exercises • Get optimal performance even as the environment changes • Simple Operator-based deploy and day-2 operations experience • Supported production-ready images • APIs for Kubernetes integration • Container-based usage tracking
- 26. 26 26 Demo: Developing with Liberty in the Cloud
- 28. 28 Memory 100% 332% 412% 1025% 269% 0% 200% 400% 600% 800% 1000% 1200% Open Liberty 20.0.0.3 Wildfly Full 19.0.0.Final Tom-ee 9.0.20.0 Payara Micro 5.201 Helidon 1.4.0 Percent of Open Liberty 20.0.0.3 (lower is better) Memory Footprint- Acmeair MS - Docker 100% 216% 0% 100% 200% 300% Open Liberty 20.0.0.3 Tomcat 9.0.30.0 Percent of Open Liberty 20.0.0.3 (lower is better) Memory Footprint during load - Petclinic using Docker (limit memory = 4g) Microservice Benchmark Application 2.5x-10x saving Spring Boot PetClinic Application 2x saving
- 29. 29 Throughput 100% 96% 44% 21% 21% 0% 20% 40% 60% 80% 100% 120% Open Liberty 20.0.0.3 Wildfly Full 19.0.0.Final Tom-ee 9.0.20.0 Payara Micro 5.201 Helidon 1.4.0 Percent of Open Liberty 20.0.0.3 (higher is better) Throughput - Acmeair MS - Docker 100% 52% 0% 20% 40% 60% 80% 100% 120% Openliberty 20.0.0.3 Tomcat 9.0.30.0 Percent of Open Liberty 20.0.0.3 Throughput - Spring Boot Petclinic- Docker Microservice Benchmark Application 2x over Tomcat Spring Boot PetClinic Application 2x over Tomcat
- 30. 30 30 Summary
- 31. 31 Summary • Agile runtime for modern cloud-native applications • Open source & open standards • Choose from latest MicroProfile and Jakarta EE • Zero migration - invest in creating new, not maintaining old • Optimized for containers and Kubernetes • Ready for any cloud
- 33. 33
- 34. Open Liberty © 2021 IBM Corporation 34 https://openliberty.io Useful Links Why choose Liberty for microservices https://ibm.biz/6ReasonsWhyLiberty Choosing the right Java runtime https://ibm.biz/ChooseJavaRuntime How to approach application modernization https://ibm.biz/ModernizeJavaApps Open Liberty site https://www.openliberty.io Open Liberty guides https://www.openliberty.io/guides @OpenLibertyIO