Skip to main content

Tiered Deployment

A hybrid approach combining sidecar deployments for performance-critical tasks and a shared microservice for batch processing or less time-sensitive workloads.

tiered

Benefits

  • Real-time responsiveness where needed (sidecar).
  • Centralized microservice handles broader or shared tasks.
  • Balances resource usage by limiting sidecar instances to high-priority operations.
  • Helps balance performance and latency with cost and complexity.

Considerations

  • More complex deployment structure, mixing two patterns.
  • Must ensure consistent versioning between sidecar and microservice instances.
  • Potentially higher operational complexity and cost.

Use This Approach When

  • Certain application components require ultra-low-latency responses, while others do not.
  • Centralized AI or analytics is needed, but localized real-time decision-making is also required.
  • The system can handle the operational complexity of running multiple deployment patterns.
  • Balancing performance and latency with cost and complexity is the goal.

Example Use Case
A logistics application that calculates routing decisions in real time (sidecar) while a microservice component processes aggregated data for periodic analysis or re-training models.