Saving fish by writing code! Applications developer in fisheries, specializing in webapps and moving 'enterprise-y' legacy systems to modern agile systems - Email or tweet me if you want to talk!
In the Java world, the load balancer approach Chris James describes is probably the best.
For development work, you can hot reload your app server with a tool like spring-loaded or JRebel.
If you tried the second in prod, I expect you'd get a memory leak sooner or later. Maybe some kind of classpath weirdness
With docker, what you get is a completely configured environment for your code to run. It's convenient because you can bundle environmental changes with code changes. Docker alone isn't going to handle zero downtime deploys. Here's an article that talks about zero downtime deploys with docker
Typically, after you reload too many classes too many times, what you get is a java.lang.OutOfMemoryError: PermGen exception. That's why on development environments, it is usually a good idea to boost the PermGen pool significantly. I run with -Xmx2048m -XX:MaxPermSize=1024m (PermGen is part of the heap, so make sure you have enough space in your heap for PermGen AND for all the other things that the heap will use)
I don't know if that ratio (heap/PermGen) is ideal, but it works.
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.
In the Java world, the load balancer approach Chris James describes is probably the best.
For development work, you can hot reload your app server with a tool like spring-loaded or JRebel.
If you tried the second in prod, I expect you'd get a memory leak sooner or later. Maybe some kind of classpath weirdness
With docker, what you get is a completely configured environment for your code to run. It's convenient because you can bundle environmental changes with code changes. Docker alone isn't going to handle zero downtime deploys. Here's an article that talks about zero downtime deploys with docker
Typically, after you reload too many classes too many times, what you get is a
java.lang.OutOfMemoryError: PermGenexception. That's why on development environments, it is usually a good idea to boost the PermGen pool significantly. I run with-Xmx2048m -XX:MaxPermSize=1024m(PermGen is part of the heap, so make sure you have enough space in your heap for PermGen AND for all the other things that the heap will use)I don't know if that ratio (heap/PermGen) is ideal, but it works.