O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Integration (Application?) Modernization with IBM Garage

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Carregando em…3
×

Confira estes a seguir

1 de 47 Anúncio
Anúncio

Mais Conteúdo rRelacionado

Mais recentes (20)

Anúncio

Integration (Application?) Modernization with IBM Garage

  1. 1. IBM Garage Integration (Application?) Modernization with IBM Garage Andrew Ferrier EMEA Architecture Lead, IBM Garage andrew.ferrier@uk.ibm.com @andrewferrier
  2. 2. Partner App Developer Business “Developer” Integration On-Premise Partner(s) Partner Apps Integration Developer Integration SaaS CRM Marketing HR Accounts Finance API management Gateway Cloud(s) Integration Developer Apps Micro- service(s) Integration SoE IoT Mobile API Economy App Developer Social Private Cloud Gateway Analytics ERP Integration Integration APIs What does integration look like today? Application Developer
  3. 3. IBM Garage But… there are pressures. The integration space is changing as customers focus on Innovation and particularly App Modernization projects. 3
  4. 4. IBM Garage Where it started; the Enterprise Monolith… 4 Browser IBM HTTP Server DB2 Database WebSphere ND WAR Store UI Catalog Service Cart Service Search Service Orders Service
  5. 5. IBM Garage Then came SOA; for efficiency and reuse… 5 Services Registry (WSRR) Inventory Service Order Service Search Accounts Carts Orders Billing Products Warehouses Catalog Service
  6. 6. IBM Garage Need for cloud-ready scale and speed have moved us to microservices… 6 RDBMS Accounts Service RDBMS Store User Interface Recommendation Service Graph DB Search Service Product Details Service Doc/NoSQL Orders Service Hadoop Shopping Analytics Cached Calls
  7. 7. Migrate Modernize Build Lift and shift applications and workloads Update using containers and microservices Build new cloud native applications emphasis to-date Cloud entry point Modernizing existing applications Greater business agility Outcomes Modernize Update using containers and microservices Innovation (aka Build) Create new cloud- native applications Chapter 2: Modernization Build with new technology Driver Lower costs Driver IBM Cloud / April 2019 / © 2019 IBM Corporation
  8. 8. IBM Garage But… this application modernization requires our integrations to modernize too. It’s now possible to run microintegrations in individual containers, so… 8
  9. 9. IBM Garage App Modernization requires Integration Modernization (and vice-versa)…. 9 (for more: http://ibm.biz/AgileIntegArchLinks) Containerization As-Is Centralized ESB Replatform & Repackage Fine-grained integration deployment Application autonomy Polyglot runtimes Decentralized integration ownership Refactor Integration as a microservice runtime
  10. 10. Traditional integration Modern integration Deployed in the data centers Cloud-based deployment, IPaaS model Centrally owned and managed Decentralized ownership, unified management SOR-centric and provider focused User-story centric and consumer focused A separate architectural layer in the solution between the backend and frontend An aspect in the solution that connects across all architectural layers Integration development is considered slow-speed IT, focusing on renovating and standardizing Integration development is agile and considered fast-speed IT, focusing on innovating and exploring
  11. 11. USER CLOUD SERVICES (AI, Analytics) CLOUD NATIVE APPLICATIONS APPLICATION DATA INTEGRATION ENTERPRISE APPLICATION DATABASE AAS ANALYTICS TRANSFORMATION & CONNECTIVITY ENTERPRISE DATA SECURITY DEVOPS EVENT STREAMING ENTERPRISE MESSAGING HIGH-SPEED DATA TRANSFER COMMON MANAGEMENT SERVICES MONITORING & LOGGING API MANAGEMENT BROWSER DEVICE PUBLIC NETWORK PROVIDER CLOUD NETWORK PRIVATE CLOUD NETWORK ENTERPRISE NETWORK NATIVE CAPABILITIES INTEGRATION CAPABILITIES EDGE SERVICES 2 3 4 5 6 7 8 9 10 11 12 10 11 1 SAAS APPLICATIONS MANAGED CONTAINER PLATFORM LEGEND Application Infrastructure Data Store Security Analytics Users DevOps Management Scalability Modern Integration Reference Architecture (for more: https://www.ibm.com/cloud/garage/architectures/mo dernIntegration )
  12. 12. What things might we need to modernize? IBM Cloud / April 2019 / © 2019 IBM Corporation Integration Characteristics Traditional Modern Architecture Closed/Monolithic Open/Fine grained components DevOps Waterfall/ Controlled Lifecycle Agile/ Automation/ CICD Infrastructure On prem Multi cloud
  13. 13. IBM Garage Integration (Application?) Modernization will impact more than just your architecture… People? Process? Deployment Infrastructure? 13
  14. 14. IBM Garage 14 Example: Major Car Rental Company • Problem Statement: • Digital Channel initiative successfully implemented with mobile and web apps • Agile programming using microservices and APIs • The agility runs into a bottleneck when the native apps are dependent on the APIs into the SORs which are running on traditional integration products with central governance and waterfall development methods. • Objectives for modern integration • Refactor backend API logic into more granular functions and into microservices based integration flows, perhaps to be run within the scope of the digital app. • Apply IBM Garage method to the integration development team and look into decentralizing the integration capability ownership.
  15. 15. IBM Garage 15 Example: Global Building Materials Manufacturer • Problem Statement: • Native applications (web and mobile) are accessing enterprise information through a API Management SaaS platform and a DBaaS. • Data is replicated from the SORs to the DBaaS component based on integration flows running in an ESB which encountered timing and sequencing constraints. • API logic is implemented in the SOR database itself via complex SQL stored procedures which ran into scalability and performance issues, not to mention the flexibility of changing stored procedure logic. • Objectives for modern integration • Use event streaming pub sub to replicate data events in the SOR in near real time into the DBaaS component • Refactor the stored procs logic into micro integration flows that run on lightweight integration runtimes to be invoked at the granular level by the native apps
  16. 16. IBM Garage 17 Apply the Strangler Pattern…
  17. 17. IBM Garage So how does all this relate to the IBM Garage? 18
  18. 18. IBM Garage Planning the Integration Modernization Phases Traditional Cloud-ready Traditional Cloud- native Containerized enterprise middleware Traditional enterprise middleware VMs Traditional enterprise middleware Containerized enterprise middleware Cloud – CaaS/PaaS Integration Microservices Cloud n ative s ervices C ost optimization Transformation Cloud-enabled Containerized enterprise middleware Cloud - CaaS Decentralized Fine grained On premises Container Platform Central ESB Services Central ESB Services Central ESB Services IBM Garage Since 2014, we have developed a worldwide network of Garages… X San Francisco Nice New York Tokyo Austin Copenhagen Munich Raleigh Milan Madrid São Paulo Dubai Melbourne Singapore Toronto London ibm.com/ garage Visit
  19. 19. IBM Garage 20 IBM Garage for Cloud We empower companies small and large to disrupt and transform by delivering cloud- based solutions in the minimum possible time using the IBM Cloud and the IBM Garage Method for Cloud. SPEED of start-up SCALE of an enterprise
  20. 20. IBM Garage 21 Foundations of the IBM Garage People Cloud New ways of working Global network Your team, our team, and an ecosystem of expertise customized to the opportunity: • Designers • Architects • Developers • … including you? • … backed by IBM A catalog of workflows workflows powered by: by: • Hybrid Cloud • AI and Automation • Data science, Analytics • Blockchain • Technology integration • IoT A prescriptive, adaptive methodology using: • Design Thinking • Agile • Lean startup Our workspaces inspire inspire ideas and enable change: • Purpose-built, worldwide IBM Garages
  21. 21. IBM Garage Activities Initial Framing Session Design Thinking Architecture Minimum Viable Product Build-up Build Out Client outcomes Align on your vision vision and desired business outcome. Confirm executive sponsor, product owner. Align LOB and IT on on user experience and roadmap to meet your vision. Agree on next MVP business experiment. Assess and align minimum viable architecture. Test hypothesis via learning–driven production release. Achieve the stated business mission. Become self– sufficient in achieving business results with the IBM IBM Garage Method. Method. Scale production environment/app. 22 Take your idea to reality with speed. Applies to: Innovation | Modernization | Data & AI | Operations and more
  22. 22. IBM Garage The Garage experience is a co-creation experience 23
  23. 23. IBM Garage The IBM Garage Method Get to know your users Define and design your MVP Continuous delivery pipeline Production system Continuous learning to drive business decisions Code using autonomous squads using rank ordered backlogs Sponsor users Playbacks Test automation Small batches Continuous integration Feature toggles Automated operations Squads of: Product Owner Architect Designer Developer We’ve taken the best practices from Design Thinking, Lean Startup, and Agile to provide prescriptive guidance on applying the practices for specific outcomes in most our published IBM Garage Methodology.
  24. 24. IBM Garage What patterns do we see? 25 This is where “integration modernization” sits
  25. 25. IBM Garage 27 What might an “Integration” Modernization Project look like? • Use Design Thinking to define the scope of the project from a user perspective to ensure there is user value from the project. • Run an architectural workshop to define the technical approach to modernization. • Do some other application modernization work. • Set up a container platform if required (e.g. IBM Cloud Pak on OpenShift). • Migrate/Refactor an existing integration pattern from the Data Center into the Platform (e.g. APIC) • Create a lightweight integration microservice to embed in the native app (e.g. a stateless flow) • Define DevOps flow for refactored integration components. • etc… • Release!
  26. 26. IBM Garage Summary 28 • Application Modernization requires Integration Modernization, and vice- versa. They do not exist in isolation. • Integration should now be thought of as just another implementation technology (programming language?) for microservices / containers. • It’s a long journey. The IBM Garage can help define the right MVP to get you started and co-create with you to help you learn.
  27. 27. IBM Garage Thanks! Any questions? andrew.ferrier@uk.ibm.com @andrewferrier 29
  28. 28. IBM Garage 30
  29. 29. IBM Garage 32 Thanks! Any questions?
  30. 30. IBM Garage 33
  31. 31. IBM Garage 34
  32. 32. IBM Garage 35
  33. 33. IBM Garage 36
  34. 34. IBM Garage 37
  35. 35. IBM Garage 38
  36. 36. IBM Garage 39
  37. 37. IBM Garage 40
  38. 38. IBM Garage 41
  39. 39. IBM Garage 42
  40. 40. IBM Garage 43
  41. 41. IBM Garage 44
  42. 42. IBM Garage 45
  43. 43. 46
  44. 44. IBM Garage 47
  45. 45. IBM Garage 48

Notas do Editor

  • 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.
  • 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.



  • 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.



  • Talk about identifying good Garage opprotunities
  • Here is how we do projects in the Garage…consistently, using Garage practices, with DevOps engineered on Day 1

×