J-Spring 2018 - A journey from Java EE to Cloud Native microservices
- 1. #jspring Vincent Oostindië - 31-05-2018 A journey from Java EE to Cloud Native microservices
- 2. Rabobank Internet Banking versus Rabobank Online, web and app 2
- 3. Rabobank’s Online Platform 2008 - 2018 3 Load Balancer deployment unit Linux box Linux box WAS / Linux deployment unit Linux box Linux box WAS / Linux Simple setup Session state Sticky load balancing Multiple domains & sites Independent units & boxes Easily scales horizontally
- 4. Linux Rabobank’s Online Platform 2008 - 2018 4 IBM WebSphere Application Server App Shared Libraries (API’s) App App App Portal Framework App App Plugins /* Everything in-JVM: super fast Portlets Page rendering In parallel Services Endpoint mapping Access control User profile User preferences Throttling Monitoring Generic functionality
- 5. It’s been a great ride so far… 5 7 Deployment units 400+ Applications 2100 TPS, easily 2 mln Logons per day And very few significant disturbances!
- 6. …but the time has come to move on! 6 3 main drivers Scalability limits DevOpsAging technology
- 7. Our future is in microservices, but… 7 …how are we going to scale out? deploy run monitor operate
- 8. We need a microservices platform! 8 2016 2017 Research Build our own PaaS Proof of Concept Selection Implementation late 2015 01-01-2018
- 9. We’ve selected Pivotal Cloud Foundry 9(Oh, and by the way, it runs in public cloud) As the microservices platform for the Rabobank as a whole
- 10. Lessons learned 10 We’re not in the platform business Developers come first Pick the right abstraction
- 11. On picking the right abstraction 11 Abstraction Flexibility Containers Apps VM’s Functions We believe that 84.962% of the DevOps teams, building microservices, should operate on this level.
- 12. Public Cloud Pivotal Cloud Foundry container Our promise: simplicity 12 MyApp cf push myApp cf scale myApp -i 2 MyApp container MyApp myapp.pcf-apps.rabobank.nl
- 13. How to migrate the Online Platform? 13 Two distinct tracks Linux box IBM WebSphere Application Server App Shared Libraries (API’s) App App App Portal Framework App App Plugins Apps Portal Framework
- 14. Migrating apps step 1 of 2: Logical services in separate EARs 14 EAR 1 Portal Framework Transactions Accounts Payments EAR 2 Addresses Orders Portal Framework Transaction Service Account Service Payment Order Service Credit Card Service Address Service
- 15. 15 Portal Framework Transaction Service Account Service Payment Order Service Credit Card Service Address Service Migrating apps step 2 of 2: Creating real microservices on PCF Transaction Service Account Service Payment Order Service Credit Card Service Address Service Real team autonomy! But also: many new challenges…
- 16. Migrating the portal framework: Breaking down the monolith 16 Access control Throttling Monitoring Page rendering Portlets Services User profile User preferences Endpoint mapping … … … … … … …
- 17. Migrating the portal framework: Breaking down the monolith 17 Proxy Trash Library Microservice
- 18. Internet access / Security layer / Single-sign on / API management The Rabobank Online Cloud Services 18 Public web Secure web APIs Pivotal Cloud Foundry Edge routing User preferences User & product services Virtual channel monitoring Employee services Page rendering Session store Apps Internal web
- 19. Edge routing 19 URL governance Defense in depth CSRF protection Red button procedure User authentication Expose the externally accessible parts of services through governed external URLs, but only if it is safe to do so
- 20. Edge routing 20 BalanceEdge router External Internal /actuator lookup URL registry User registry authenticate /api/balance: balance balance: customer, level 2 … balance: enabled bankieren.rabobank.nl /api/balance balance.pcf-apps.rabobank.nl forward
- 21. Edge router technology stack 21
- 22. Proud to be part! 22 70+ Teams 600+ Instances And growing fast! As of May 2018
- 23. Please rate this session in the J-Spring app #jspring