Good point and thank you for your comment 🤎! 100% agree that REST APIs should be stateless. What I try to say here is that many legacy services that provide APIs do not react well to being restarted frequently.
So even though they provide a 'stateless API', the server applications themselves take a long time to start up - which is often linked to them having some kind of implicit state, such as DB connections, local caches, session management, etc.
Does that make sense? If so, I will try to rewrite that section to make it clearer - but if not, happy to discuss further first!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good point and thank you for your comment 🤎! 100% agree that REST APIs should be stateless. What I try to say here is that many legacy services that provide APIs do not react well to being restarted frequently.
So even though they provide a 'stateless API', the server applications themselves take a long time to start up - which is often linked to them having some kind of implicit state, such as DB connections, local caches, session management, etc.
Does that make sense? If so, I will try to rewrite that section to make it clearer - but if not, happy to discuss further first!