Winning with open Infrastructure with Christopher Aedo
summary
Argues that infrastructure means repos, communication platforms and orchestration not just compute and storage, and calls that developer dial tone. Recommends starting with OpenStack-based providers to avoid vendor lock-in and not building a private cloud unless at significant scale. Advises large legacy shops to rearchitect incrementally, breaking monoliths into microservices and containerize one app at a time. Notes IBM is investing in libraries, samples and tutorials on developer.com/code.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:10Choosing a provider
- 3:05Transformation
- 4:39Microservices
- 5:44Developer advocacy
- 6:59Improving developer lives
related talks
14mKeynote: Open Source & Operational Excellence
30mOn-premise data centers do not need to be legacy
23mPaul Cormier, Red Hat | Red Hat Summit 2020
15mKeynote: Not All Clouds Are Created Equal
07mKeynote: Pushing the Boundaries of Open Source for a Brand New Edge
11mPaul Cormier, Red Hat | CUBE Conversation, April 2020
33mWhat the Cloud?
15mState of the Infrastructure