3 ms·
The difference is that your runtime state is reset and you must architect your application to keep fast startup time which is not always a good thing. OSGI does
by vbezhenar 8y ago
The difference is that your runtime state is reset and you must architect your application to keep fast startup time which is not always a good thing. OSGI does not reload classes, it loads new classes, you can't reload class for an existing object. It's the same restart, you just leak memory.
- tomjakubowski 8y ago> The difference is that your runtime state is reset and you must architect your application to keep fast startup time which is not always a good thing. Seems like slow startup time would be just as bad, if not worse, for a workflow that involves killing the server and bringing it back up again from scratch to test changes. So I think that either way it's a good idea to architect your application, at least in "development mode", to have a fast startup time.
- twblalock 8y ago> The difference is that your runtime state is reset and you must architect your application to keep fast startup time which is not always a good thing. These are good things for serverless, which is what the article is about -- runtime state in a serverless application is bad, and fast startup is good. Serverless instances are intended to be interchangeable and ephemeral. You should be able to start new instances and they should be able to do the same work as the existing instances -- that only works well if they are stateless. Any necessary state should be stored in a database or blob store or some other external state management system.
- XMPPwocky 8y agoPlus, having runtime state around from a previous version (or versions!) of the app sounds utterly terrifying