Going towards multi-cloud microservices with Go Cloud

How to deploy applications to multiple clouds without the hassle of writing specific code for each cloud? Go Cloud provides idiomatic interfaces that abstract storage or database access which makes switching cloud providers a piece of cake.

Transcript

1. cosee GmbH, Markus Zimmermann, @markus_zm Going towards multi-cloud microservices with Go Cloud
2. About me Cloud Developer Master Thesis about npm Security Co-organizer Gophers Darmstadt
4. Team cosee
5. Competition! #gocosee Terms: bit.ly/idontwanttogotojail
6. Today’s (glorious) blather. Why is Cloud cool? Why Multi-Cloud? Multi-Cloud Microservices Go Cloud Demo Takeaways
7. Section one Why is Cloud cool?
8. Photo by Jeremy Perkins on Unsplash
9. Reasons for Success of Cloud Computing Cost Savings Scalability Ease of Use Automation Higher Productivity
10. Source: Rightscale Cloud Report
11. Section two Why Multi-Cloud?
12. Source: Techcrunch
13. Source: Bloomberg
14. Multi-Cloud Failover
15. Vendor Lock-in
16. Industry Standard vs. Vendor Standard Source: xkcd
17. Cloud-agnostic tooling Container Orchestration Cloud Provisioning Continuous Deployment
18. “Cloud is about how you do computing, not where you do computing” Paul Maritz, CEO of VMware
19. Multi Cloud Strategy 86 % of enterprises employ a Multi-Cloud strategy Source: Max Lawton – unsplash https://www.techrepublic.com/article/why-86-of-enterprises-employ-a-multi-cloud-strategy-and-how-it-impacts-business
20. Section three Multi-Cloud Microservices
21. Multiple Clouds
22. Architecture
23. Clean Architecture Principle Source: Mattia Battiston, under CC BY 4.0, https://github.com/mattia-battiston/clean-architecture-example
24. Abstraction Layer Cloud Providers
25. Section four Go Cloud
26. Abstraction with GoCloud Library
27. Current Cloud Provider Support
28. Current Features Blob Storage Configuration Connection to MySQL Databases Server startup & diagnostics
29. Go Cloud API Overview
30. Dependency Injection with Wire //+build wireinject func setup(c *Config) *App { wire.build( NewDB, NewRuntimeConfig, NewStorage, NewApp, ) return &App{} } func main() { c = &Config{} app = setup(c) }
31. Section five Demo
32. Demo Architecture
33. Provisioning
34. Section six Takeaways
35. Still Alpha Not yet for production! Only supports the two major cloud providers Solves vendor lock-in problem BUT not multi-cloud resiliency API already looks promising
36. Summary Cloud portability could be the future Abstract provider-specific code Automatically provision infrastructure Use cloud-agnostic tooling
37. for listening! Source: Tomasz Sroka – unsplash Thanks
38. blog.cosee.biz cosee.jobs