Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Entering the next level - Migrating to cloud na...

Entering the next level - Migrating to cloud native platforms

Organizations are moving from centralized data centers to distributed cloud native platforms. Due to the complexity of such a migration, the organization will be running a hybrid multi-platform environment which spans from the old to the new world. It starts at the edge of a system, using functionality provided by an API Gateway or Platform.

Daniel Kocot

May 26, 2020
Tweet

More Decks by Daniel Kocot

Other Decks in Technology

Transcript

  1. Enter the next level - Migrating to cloud native platforms

    Daniel Kocot, Senior Solutions Architect 1
  2. Name: Daniel Kocot Role: Senior Solutions Architect / API Expert

    Email: Twitter: dk_1977 LinkedIn: [email protected] https://www.linkedin.com/in/danielkocot/ 2
  3. Reasons for modernization faster deployments some components need to update

    more frequently than others some components need different scale requirements 4
  4. Reasons for modernization faster deployments some components need to update

    more frequently than others some components need different scale requirements some components should be developed in a different technology 4
  5. Reasons for modernization faster deployments some components need to update

    more frequently than others some components need different scale requirements some components should be developed in a different technology codebase is too big and complex 4
  6. Cloud Native CNCF Definition, https://github.com/cncf/toc/blob/main/DEFINITION.md "Cloud native technologies empower organizations

    to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach. These techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and predictably with minimal toil." 5
  7. API first An API is the first (and often only)

    interface to users of an application 13
  8. API first An API is the first (and often only)

    interface to users of an application An API comes first — before the implementation 13
  9. API first An API is the first (and often only)

    interface to users of an application An API comes first — before the implementation An API is described (documented) or self-descriptive 13
  10. API Mediation Architectural layer to manage, protect and enrich an

    API Intercepting API traffic Concept of "outer" APIs 15
  11. API Mediation Architectural layer to manage, protect and enrich an

    API Intercepting API traffic Concept of "outer" APIs No business logic should be handled within this layers 15
  12. Bring in the patterns! Messaging APIs Hybrid integration GraphQL integration

    Event-Driven architecture Anti-Corruption Layer Strangler Pattern 29
  13. References Photo on title slide by on Photo on slide

    24 by on Photo on slide 25 by on Ian Parker Unsplash Markus Spiske Unsplash Jesiel Rubio Unsplash 40