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

From Cloud-Hosted to Cloud-Native

From Cloud-Hosted to Cloud-Native

Originally presented at QCon London 2023.

----

You’ve committed to the journey of running in the cloud. However, you realize it’s not quite as simple as moving or writing a new application on a cloud offering. Between a diverse service catalog, greater developer autonomy, rapid provisioning, surprise billing, and changing security requirements, you might find that hosting applications on the cloud does not make the most of the cloud.

In this session, Rosemary will outline the patterns and practices that help you move from cloud-hosted to cloud-native architecture and maximize the benefit and use of the cloud. From essential application and infrastructure considerations to dynamically observing cost and managing security, you can use these learnings to approach a cloud-native architecture.

Rosemary Wang

June 08, 2023
Tweet

More Decks by Rosemary Wang

Other Decks in Technology

Transcript

  1. cloud-native build and run scalable applications in modern, dynamic environments

    such as public, private, and hybrid clouds. github.com/cncf/toc/blob/main/DEFINITION.md 3 @joatmon08
  2. cloud hosted build and run scalable applications in modern, dynamic

    environments such as public, private, and hybrid clouds. github.com/cncf/toc/blob/main/DEFINITION.md 5 @joatmon08
  3. cloud-native considerations • adaptability • observability • immutability • elasticity

    • changeability 7 @joatmon08 *balance delivery and future-proofing
  4. • Decouple artifact dependencies • Decouple configuration and secrets •

    Use dependency injection • Write abstract (end-to-end) tests • Update to stable (-1) version 13 @joatmon08
  5. • Map dependencies • Tag and add metadata • Enable

    audit and access logs • Aggregate telemetry • Standardize and index telemetry • Assess push versus pull 20 @joatmon08
  6. • Automate infrastructure as code • Decouple state and configuration

    • Reload / restart for changes • Optimize provisioning • Distribute data 27 @joatmon08
  7. • Evaluate idle versus active resources • Minimize the “traffic

    trombone” • Optimize warm-up and runtime • Assess volume versus frequency 34 @joatmon08
  8. • Assess benefit • Review previous considerations • Choose an

    intermediate step • Refactor application / infrastructure 41 @joatmon08
  9. cloud-native build and run scalable applications in modern, dynamic environments

    such as public, private, and hybrid clouds. github.com/cncf/toc/blob/main/DEFINITION.md 43 @joatmon08