32-bit vs 64-bit
    Annotations vs Decorators
    BigQuery vs Bigtable
    Block Storage vs File Storage vs Object Storage
    C vs C++
    Canvas vs SVG
    Constructor vs Init() vs Factory
    Containers vs Virtual Machines (VMs)
    DOM vs Virtual DOM vs Shadow DOM
    DQL vs DDL vs DCL vs DML
    Dagger vs Guice
    Data Mining vs Machine Learning vs Artificial Intelligence vs Data Science
    Flux vs Redux
    GCP API Gateway vs Cloud Endpoint
    GCP Cloud Run vs Cloud Functions vs App Engine
    GCP DataFlow vs Dataproc
    Google Analytics 4 vs Universal Analytics
    Google Internal vs Open Source
    HEIC vs HEIF vs HEVC vs JPEG
    Java vs C++
    Jetty vs Netty
    Kotlin vs Java
    LLVM vs JVM
    Linux vs BSD
    Microcontroller vs Microprocessor vs Computer
    Node.js vs Erlang
    POSIX vs SUS vs LSB
    Pass-by-value vs Pass-by-reference
    Proto2 vs Proto3
    PubSub vs Message Queue
    REST vs SOAP
    React vs Flutter vs Angular
    Rust vs C++
    SLI vs SLO vs SLA
    SRAM vs DRAM
    SSD vs HDD
    Software Engineer vs Site Reliability Engineer
    Spanner vs Bigtable
    Stack based VM vs Register based VM
    Stateless vs Stateful
    Static Site Generation vs Server-side Rendering vs Client-side Rendering
    Strong Consistency vs Eventual Consistency
    Subroutines vs Coroutines vs Generators
    Symlinks vs Hard Links
    TCP vs UDP
    Tensorflow vs PyTorch
    Terminal vs Shell
    Vi vs Vim vs gVim vs Neovim
    WAL vs rollback journal
    gtag vs Tag Manager
    stubs vs mocks vs fakes

Stateless vs Stateful

Updated: 2021-11-19


The functionalities of pure stateless services are quite limited, most likely we still need to save states to somewhere; if not stored locally, then they have to go to the database layer.

So it works like this: a client makes a request; the stateless service talks to the database to get some data; the service does some computation and send the response to the client. The data is not persisted on the service instance, and the next request may be load balanced to a different instance. If there's no cache, this is quite wasteful.

  • pros:
    • easy to scale horizontally
    • easy to load balance(e.g. simple round-robin)
  • cons:
    • state stored in databases, and round trips to the databases increases latency
    • need a caching layer to mitigate the latency problem
    • once the application outgrows the single database instance, either sharding or a NoSQL database is needed, which may sacrifice strong consistency


  • pros:
    • data is right on the server, no need to hit database, low latency
    • data can be persisted on the server after the request is handled, the requests from the same client can be routed to the same instance, so the following requests can reuse the data, or the "state"
    • can open up a persistent HTTP connection or a TCP connection
  • cons:
    • if the connection breaks the stickiness is gone, and the next request will be load balanced to another server
    • bad load balancing, easy to overwhelm a single server with too many connections