|
|
|
|
|
|
by tmpz22
1406 days ago
|
|
|
The traditional line of thinking is: * you're building a web-ish application and need to store session data * you don't want to go through the overhead of building a strongly typed relational table * you know minimal operations stuff * just use redis, its easy to deploy, easy to code for, and available on all major cloud platforms as a managed service --- The problem is there are tradeoffs and session storage becomes a fundamental architectural decision once your application matures. So something you added as a once-off so you can get back to feature development is now a foundational pillar. |
|
|