Slide 9: Solution and Architecture Approaches

Three Architecture Approaches - Each with Different Adoption Implications:

  1. CLOUD ENABLING
    • Modernizing existing systems for cloud environments
    • Taking legacy systems and making them cloud-compatible
    • Adoption Impact: Users familiar with current system
    • Lower disruption → Higher voluntary adoption potential
    • Lifecycle Fit: Works well for Trending Behind → Mainstream
    • Best for: Legacy modernization with user continuity
    • Examples: Containerization, API wrapping, lift-and-shift
  2. CLOUD NATIVE
    • Built for cloud from scratch using modern patterns
    • Microservices, containers, 12-factor applications
    • Adoption Impact: May require new user workflows
    • Must demonstrate clear value for voluntary adoption
    • Lifecycle Fit: Ideal for Leading Edge → Mainstream
    • Best for: Greenfield projects with innovation requirements
    • Examples: Kubernetes-native apps, serverless, cloud-first design
  3. CLOUD AGNOSTIC
    • Portable solutions that work across multiple cloud platforms
    • Avoiding vendor lock-in through abstraction
    • Adoption Impact: Consistency across environments
    • User experience consistent → Easier adoption
    • Lifecycle Fit: Requires Mainstream tooling for stability
    • Best for: Multi-platform, multi-environment requirements
    • Examples: Platform-independent containers, open standards, portable IaC

Visual

Cloud enabling
  • Refactoring
  • Containerization
  • API wrapping
Adoption friction35%
Cloud native
  • Microservices
  • 12-factor apps
  • Kubernetes patterns
Adoption friction75%
Cloud agnostic
  • Portability
  • Abstraction
  • Multi-platform IaC
Adoption friction40%
Speaker notes
  • "Architecture decisions are adoption decisions"
  • "Cloud Enabling often gets higher voluntary adoption because users know the system"
  • "Cloud Native can be powerful but requires thinking about user change management"
  • "Cloud Agnostic helps when users work across multiple environments"
  • "Choose based on 'best tool for the job' philosophy aligned with your needs"

Transition: "Let's look at how lifecycle stage and architecture approach connect - because you can't choose just any architecture at any lifecycle stage."

Navigation