Integration (Application?) Modernization with IBM Garage

Editor's Notes

• #3: This should be a familiar journey, although each company will traverse it in a different order: Most systems are initially on premise, joined together using a variety of integration patterns, including SOA, but also hub and spoke, and point to point. SaaS applications provide a way to implement core business functions without bloating the IT infrastructure with unnecessary concerns. Existing systems of record are moved to the cloud to save costs and/or simplify, and the cloud environment is used for all new applications too. Partners automate their engagement with the enterprise, traditionally using files, but latterly moving to APIs as a simpler way to create new function. Innovation really kicks in as independent systems of engagement are written mobile first, and the internet of things starts to instrument the consumers world. The world seems to have become much more complex, and in many ways it has, but from an integration point of view, there are many repeating patterns in which to find some consistency.
• #8: In chapter 1 of cloud, the emphases was mainly on the rapid value, easy stuff: Migrating relatively simple apps and workloads to IaaS to lower costs. And using public cloud to innovate with new technologies and extend existing apps. And even that has not been without challenges. Lift and shift everything to cloud and sort it out later models (like AWS) have resulted is massive unexpected costs for complex workloads, sometime as much as 5 times projected (costs: preparing, moving data, integrating to back office, etc.). Developing new apps and taping into SaaS from more vendors has created new tech silos, making it difficult to manage security, compliance, resiliency, and govern across vendors and clouds. Build 2: To see even higher value from cloud, we need to improve focus on modernization of existing applications. In fact, according to a recent Forrester study, the number 1 priority for enterprises digital transformation is modernizing existing mission critical apps, and those that have are seeing greater business agility and simplified access to data needed to create new insights more quickly.
• #13: In chapter 1 of cloud, the emphases was mainly on the rapid value, easy stuff: Migrating relatively simple apps and workloads to IaaS to lower costs. And using public cloud to innovate with new technologies and extend existing apps. And even that has not been without challenges. Lift and shift everything to cloud and sort it out later models (like AWS) have resulted is massive unexpected costs for complex workloads, sometime as much as 5 times projected (costs: preparing, moving data, integrating to back office, etc.). Developing new apps and taping into SaaS from more vendors has created new tech silos, making it difficult to manage security, compliance, resiliency, and govern across vendors and clouds. Build 2: To see even higher value from cloud, we need to improve focus on modernization of existing applications. In fact, according to a recent Forrester study, the number 1 priority for enterprises digital transformation is modernizing existing mission critical apps, and those that have are seeing greater business agility and simplified access to data needed to create new insights more quickly.
• #22: Talk about identifying good Garage opprotunities
• #25: Here is how we do projects in the Garage…consistently, using Garage practices, with DevOps engineered on Day 1