การออกแบบ API แบบไร้สถานะกับมีสถานะ

When we talk about an API's 'state', we're referring to any data or context that the API remembers about a client or an ongoing interaction.

This remembered information can influence how the API processes future requests from that same client.

A stateless API is one where each request from a client to the server contains all the information needed to process that request.

The server doesn't store any client-specific data or 'session' information between requests. Every request is treated as if it's the first one.

Consider a simple currency conversion API. For each conversion, you provide the amount, source currency, and target currency.

The server calculates the result without needing to remember any previous conversions you made. Each call is self-contained.

Stateless APIs are highly favored for building scalable systems. Here's why:

• Easy Horizontal Scaling: You can add more servers (scale horizontally) without worrying about moving client sessions.
• Simple Load Balancing: Any server can handle any request, simplifying how traffic is distributed.
• Resilience: If a server fails, other servers can immediately pick up new requests without losing client state.

A stateful API remembers information about a client or interaction across multiple requests. The server maintains a 'session' or context for each client.

Subsequent requests from the same client rely on this stored state for proper processing.

A classic example of a stateful interaction is an online shopping cart. When you add items, the server remembers them even as you browse other products.

The server maintains your cart's state between your page views and actions.

While necessary for some interactions, stateful APIs pose challenges for scalability:

• Complex Load Balancing: Requests from a client must go to the specific server holding their state (session affinity).
• Failure Recovery: If a server with active sessions fails, all that client state is lost, impacting user experience.
• Resource Intensive: Servers must dedicate memory and resources to maintain each client's state.

Here's a quick look at the core differences:

• Stateless: Each request is independent; no server-side session data is stored.
• Stateful: Server remembers client information across multiple requests via sessions.
• Scalability: Stateless APIs are much easier to scale horizontally.
• Complexity: Stateful APIs add significant complexity to distributed systems.

Understanding the distinction between stateless and stateful design is crucial for building robust, scalable APIs.

Consider the benefits of statelessness in a large, distributed system.

In this lesson, we explored the critical concepts of stateless and stateful API design. We learned that stateless APIs treat each request independently, making them ideal for horizontal scaling and distributed systems.

While stateful interactions are part of many applications (like shopping carts), striving for statelessness in the API layer often leads to more scalable and resilient architectures. Next, we'll dive into other architectural patterns for scalable APIs!