Timeline for Is stateless mode necessary before containerizing a monolithic application?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 6, 2019 at 13:14 | comment | added | Nachiappan Kumarappan | I agree with @karl with his strategy to get the services to become state less. Doing all at once would be a strict no for most businesses | |
| Oct 1, 2019 at 20:29 | comment | added | A-Dubb | @Karl that is a very true statement. A divide and conquer approach that migrates each service over seamlessly would do it. You could even use a DNS switch to test out the stateless variant of each service in production and then rollback to the state fly version of the service should any unforeseen regression or degradation in performance arise. | |
| Oct 1, 2019 at 16:32 | comment | added | Karl Bielefeldt | I really like this answer. The one thing I would add is you can do the stateless conversion incrementally. Making two or three services stateless that will benefit from it most, while the rest are stateful, is a lot better than having zero stateless services because you can't afford to convert all of them yet. | |
| Oct 1, 2019 at 14:47 | history | edited | Nachiappan Kumarappan | CC BY-SA 4.0 |
added 17 characters in body
|
| Oct 1, 2019 at 14:39 | history | answered | Nachiappan Kumarappan | CC BY-SA 4.0 |