• 00 Best Of
  • 01 The Unknown
    • 01 Introduction
    • 02 The Philosophical Layer
    • 03 An Abstract System
  • 02 Feet in the Cloud
    • 01 Cloud Computing Evolution
    • 02 Compute and Architecture
    • 03 Serverless Development
    • 04 Compute Unmanaged
  • 03 The Change Factor
    • 01 Wasteful Applicative Evolution
    • 02 The Inevitable
    • 03 Change Driven Design
    • 04 Breaking Change
    • 05 Future Changes
  • 04 Projection
    • 01 The Wheel of Change
    • 02 The Wheel’s Feedback
    • 03 Committed Planning
    • 04 The Winding Road
  • 99 The Letting Go
  • Table of Contents
  • 00 Best Of
  • 01 The Unknown
    • 01 Introduction
    • 02 The Philosophical Layer
    • 03 An Abstract System
  • 02 Feet in the Cloud
    • 01 Cloud Computing Evolution
    • 02 Compute and Architecture
    • 03 Serverless Development
    • 04 Compute Unmanaged
  • 03 The Change Factor
    • 01 Wasteful Applicative Evolution
    • 02 The Inevitable
    • 03 Change Driven Design
    • 04 Breaking Change
    • 05 Future Changes
  • 04 Projection
    • 01 The Wheel of Change
    • 02 The Wheel’s Feedback
    • 03 Committed Planning
    • 04 The Winding Road
  • 99 The Letting Go
  • Table of Contents
(C) 2022 Amir Ben Ari

02 Feet in the Cloud

The Container Store: Containerize by Default

02 Feet in the Cloud, 04 Compute Unmanaged
A database failure or a bottleneck is harder to resolve (failover, tuning or scaling) than a stateful/stateless application. A database is also a more “sensitive” component in the system. For both these reasons, the answer for should you use a container is it depends.

Posts navigation

1 2 3

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

 

Loading Comments...