2019-10-15 - the future of cloud-native Java - Bert Ertman
1 like181 views
The document discusses the concept of cloud-native computing, emphasizing its growth and importance in today's IT landscape. It contrasts traditional IT practices with cloud-native approaches, highlighting the benefits of microservices, CI/CD, and agile methodologies. Ultimately, it advocates for a cultural shift towards embracing cloud technology as a means for innovation and business agility.
2019-10-15 - the future of cloud-native Java - Bert Ertman
- 1. Are We Really Cloud-Native? Bert Ertman
- 3. What is Cloud-Native? answer: ‘Blah blah blah … Kubernetes!’
- 4. ‘Kubernetes is the Greek god of spending money on cloud services’ - @QuinniPig
- 5. About me: • Java/Cloud Postmodernist • Java Champion, JavaOne Rockstar Speaker, and a Duke’s Choice Award Winner • Book author for O’Reilly, speaker at many conferences Bert Ertman Fellow, VP Technology @BertErtman /bertertman
- 7. “The market for cloud services is growing faster than virtually every other IT market today, with much of this growth coming at the expense of the traditional, non-cloud offerings” source: Gartner Cloud is on the Rise…
- 8. TL;DR Java EE is dead, long live Cloud!
- 10. What is Cloud Computing?
- 12. ‘It’s like computers on the internet, right?’
- 15. ‘What is this Serverless witchcraft that you speak of?’
- 16. The Evolution of Compute Physical Virtualization Cloud Compute Containers Serverless
- 17. =
- 19. Serverless removes the ‘R’ from COMPUTER
- 20. ‘Whoaa… Serverless is like cows on the Internet?!!’
- 22. Middleware as managed services? • Database • Messaging • API Gateway • Storage • Web Server • …
- 25. What is happening in the world?
- 26. ‘Software is eating the world’ Marc Andreessen
- 27. We want to move fast, and yet not break things
- 28. Our answer so far… • Business agility = Microservices • Infrastructure = CI/CD + containers • Process = Agile + DevOps
- 29. …and this resulted in…
- 32. 80-90% of IT budgets are spent on maintaining existing systems Got change for my innovative ideas?
- 33. Is it really different? App Server virtual machine App inverted App Server a.k.a. fat jar a.k.a. Spring Boot virtual machine App
- 34. Is it different now? inverted App Server a.k.a. fat jar a.k.a. Spring Boot virtual machine App container
- 35. And now? container virtual machine container virtual machine container virtual machine container virtual machine container virtual machine
- 36. Modularization • Breaking up bigger things into smaller, more manageable, parts • Cohesion over coupling • Modularity is the ultimate agile tool!
- 37. Trade-offs of decomposition • How to test? • How to deal with configuration • How to deal with dependencies? • How to deal with versioning? • How to deal with latency and overhead • How to deal with monitoring? • How to deal with …
- 39. Now maybe? container virtual machine virtual machine virtual machine container orchestration platform container container container virtual machine virtual machine container container container
- 40. DevOps
- 42. Most traditional organizations… • Standardized technical infra components • Standardized hypervisor • Standardized operating system(s) • Standardized middleware • Standardized application development framework • Standardized programming language
- 44. What is an application?
- 45. 2009 answer… “A bunch of code I have to build & test together into a monolithic blob, which I then toss over the wall to an ops team, who hopefully get it to run on a fleet of servers. Then, I hope some work comes its way so I don’t waste too much $...”
- 46. 2019 answer… “Managed services in the public cloud, connected and customized with highly differentiated business logic, that run (and bill) only when actually needed.” La S
- 48. Cloud-Native is a DevOps journey! • Cloud-Native is the architecture for assembling cloud-based components in a way that is optimized for the cloud environment • It’s not about the servers, but the services • It’s about modernizing infrastructure and process, and transforming the organizational culture along the way
- 51. This is more like it! Lambda S3
- 52. Technologies or frameworks are not cloud-native, it is the way you use them
- 53. Getting the best from the Cloud • Potential for economic disruption • Ability to easily experiment with new technology or new business ideas • Focus on strategic value vs managing infrastructure and middleware
- 54. Friends don’t let friends build their own Kubernetes platform
- 55. Kubernetes Getting the best from the Cloud? vs. Managed Service
- 57. Is Java a natural fit?
- 58. Are Java programmers a natural fit?
- 59. But what does it take to become a Cloud Engineer? So you can do Java* programming?
- 63. AWS Release Pace • 2013: 280 new features • 2014: 516 new features • 2015: 722 new features • 2016: ~1000 new features • 2017: 1430 new features • 2018: ~2000 new features
- 65. Now let’s talk about culture…
- 66. Cloud-Native Culture Killers • Business does not trust IT, so no true BizDevSecOps • IT is a cost center • We only do cloud because it saves us money (we think)
- 67. Cloud-Native Culture FTW! • We have an IT-first strategy • We see Cloud as a potential for economic disruption • Cloud enables us to start experiments (forward thinking) and is our ability to innovate • Cloud enables a faster time-to-market • All our engineers are broadly skilled, and teams are fully mandated