18 lines
1.4 KiB
Markdown
18 lines
1.4 KiB
Markdown
# Stateful vs. Stateless Applications — Differences, Pros & Cons, Use Cases
|
||
|
||
|
||
|
||
## Metadata
|
||
- Author: [[Neal Davis]]
|
||
- Full Title: Stateful vs. Stateless Applications — Differences, Pros & Cons, Use Cases
|
||
- Category: #articles
|
||
- URL: https://neal-davis.medium.com/stateful-vs-stateless-applications-differences-pros-cons-use-cases-ad4b434576b8
|
||
- Archive: https://web-archive.alecodes.page/bookmarks?bf=1&search=&title=Stateful%20vs.%20Stateless%20Applications%20%E2%80%94%20Differences%2C%20Pros%20%26%20Cons%2C%20Use%20Cases
|
||
> [!tldr]
|
||
> Stateful applications remember user interactions and store data between sessions, while stateless applications do not retain any user information. This choice affects how applications are designed, their scalability, and the resources they require. Developers must weigh the pros and cons of each type to meet their project needs effectively.
|
||
|
||
## Highlights
|
||
Stateful applications save info about the user’s “state” by keeping track of what they do. [View Highlight](https://read.readwise.io/read/01j7pd95t5qyvwt98kv86bmcbf))
|
||
|
||
Stateless software applications are those applications that do not save information about previous interactions, user sessions, or events. These applications do not preserve context or state between requests in a stateless design. [View Highlight](https://read.readwise.io/read/01j7pdbyyxz2g1ems20te5d6ez))
|
||
|