logoNEURAL COOK
SearchAll PostsTagsNotesAuthor
instagramtwitterfacebookyoutubelinkedinmailgithubrss
Copyright © 2026 All rights reserved.
•
VIKI
Built with Vikramaditya Singh
Built with
VIKI - A posts created with Next.js and Tailwind.css
About
API Gateway
Batching
Cache
CAP
Consistent Hashing
Counting At Scale
CQRS
CRDT
Database Scaling
Database Selection Strategy
Event Sourcing
Handling Failure
Vertical vs Horizontal Scaling
Id Generation
Indexes
Kafka
Kubernetes
Large Files
Load Balancing
Proxy
Real Time Push
Redis
Scaling Reads
Stateless vs Stateful Systems
Scaling Writes
System Design

Stateless vs Stateful Systems

A stateless applications doesn’t save the client data from one session for use in the next session.

Whereas a stateful application saves data from one session for use in the next session.

# Scaling Stateless Applications

Can simply add more instances to your infrastructure to handle an increase in load. Similarly, you can easily remove the unused instances to optimize resource utilization and save costs.

# Scaling Stateful Applications

Stateful systems require sticky sessions or data replication across instances.

PreviousScaling ReadsNextScaling Writes
CONTENTS
Scaling Stateless ApplicationsScaling Stateful Applications