3 ms·
I had real world experience with OSGi 10 years ago and it was terrible. The JVM still had permgen leaks from loading and unloading stuff so any OSGi deployment
by liveoneggs 7y ago
I had real world experience with OSGi 10 years ago and it was terrible. The JVM still had permgen leaks from loading and unloading stuff so any OSGi deployment was bound to just OOM on permgen eventually. My container had poor (or I didn't understand it well enough) ways to define boot ordering and dependencies within the services (like docker-compose's restart: always and depends_on: stuff) so you would get service-C starting before service-A, which would fail for unrelated reasons but the JVM would go ahead and start listening on port 8080! Bring on the traffic to your broken stuff.
- LoSboccacc 7y agoI'm in a OSGi platform today and have to say it's still a broken mess beyond the fact that the world moved from big irons 25 years ago making this whole exercise in in-jvm-microservices pointless, messing with the classloader breaks most of the good things of the Java platform classloader deadlocks? check debugger having a stroke trying to use the correct source between all the overlapping libraries at different version within the classloader tree? check hot code road unable to figure out all the instances of services to replace causing weird class cast exceptions of classes over themselves? check having to create library projects that include interfaces from independent services because in the OSGi tree you can't have cross dependents? check I hate the thing with passion and move into real microservices fast enough
- liveoneggs 7y agothrow it all away and get into the real thing https://spring.io/projects/spring-boot https://spring.io/projects/spring-boot