2 ms·
I think this would depend on your specific use case. If you're app is basically managing data (managing bookmarks, note taking, etc...) then a stateless archit
by statictype 11y ago
I think this would depend on your specific use case.
If you're app is basically managing data (managing bookmarks, note taking, etc...) then a stateless architecture makes sense
If your app is reacting to data in real-time to do some work (monitoring system, chat system, sending alerts on conditions) then using a statefull service makes total sense.
- jkarneges 11y agoFor some use cases it does make sense, but even realtime/push systems can be made relatively stateless by isolating the stateful parts (e.g. into a message broker). The way I see it, nothing we design is truly stateless. There are stateful pieces everywhere (such as TCP, beneath HTTP). What we can do is minimize the effects that the stateful pieces may have on other parts of the system.