The Commoditization of the Software Stack: How Application-first Cloud Services are Changing the Game

The shift towards cloud computing is accelerating as more and more applications are blending with cloud services at deeper levels. The traditional boundaries between applications and cloud are shifting from virtual machines to containers and functions. The integration boundaries are also shifting, moving away from pure database and message broker access to a more blended approach where the mechanical parts of the application are running within the cloud. This new architecture commoditizes the full software stack but the business logic, allowing developers to offload more application logic and management responsibilities to cloud services. However, this can hinder flexibility and limit portability if not done through open APIs and standards. In this talk, we will explore the evolution of cloud-native principles from compute abstraction to integration abstractions for all languages. We will discuss how this evolution allows for migrating, porting, and reusing not only applications, but also patterns, anti-patterns, skills, and experiences. We will also examine the challenges and opportunities of this transformation, including the shift towards application-first cloud services, the role of open-source projects, and the future of cloud-native development. Join us to learn how to take advantage of the latest cloud-native technologies and practices to build scalable, flexible, and portable applications.

Transcript

1. @bibryam Bilgin Ibryam Product Manager, Diagrid The Commoditization of the Software Stack: How Application-first Cloud Services are Changing the Game
2. Bilgin Ibryam 2 • Product Manager at Diagrid • Former Architect at Red Hat • Former Committer at Apache Camel • Blogger and Author ◦ Camel Design Patterns ◦ Kubernetes Patterns @bibryam https://k8spatterns.io
3. Are we still building Microservices? 3
4. Agenda 4
5. Early-cloud era 5
6. 6 Monolithic applications
7. 7 Static infrastructure
8. 8 No clear boundaries
9. Internal architecture 9
10. 10 Visualising software architecture Source: https://en.wikipedia.org/wiki/4%2B1_architectural_view_model 4+1 model C4 model
11. 11 Internal and external views
12. 12 Domain-driven design
13. 13 Hexagonal architecture
14. 14 Onion and clean architectures
15. 15 Microservices and 12-factor apps
16. Compute-first cloud era
17. 17 Distributed application frameworks Microservices’ middleware ESB
18. 18 Application-oriented compute Sink into the infrastructure App layer
19. 19 Application-oriented boundaries
20. Application compute cloud 20
21. Compute bindings 21
22. Open compute bindings 22
23. CNCF projects and SDLC 23 Code Build & test Provision & deploy Release Operate Observe Organize Ops Devs Incubating projects Graduated projects
24. External architecture
25. 25 External architecture
26. 26 Integration bindings
27. 27 Integration deployment options
28. 28 What is Dapr?
29. 29 Dapr architecture Source: https://github.com/dapr/docs
30. 30 Dapr community momentum 22k GitHub stars 5.6k Discord members Contributing organizations include: +1M Docker Hub monthly pulls 2.5k Contributors +290k Unique docs views/mo +100 Components 3 year contributor growth 10/157 Largest CNCF project
31. 31 Integration portability
32. Application-first cloud
33. 33 Application-first cloud services
34. 34 Application-first cloud ecosystem
35. 35 What’s next?
36. Are we still building Microservices? 36
37. Takeaways 37 ✓ Focus on differentiating business logic and reuse undifferentiated commoditized capabilities. ✓ Use open compute and open integration bindings based on de-facto standards enabling portability. ✓ Portability is not about applications. It is about patterns, practices, tools, and ultimately… people.
38. @bibryam Thank You https://k8spatterns.io https://www.diagrid.io