Re:What I Wish I Had Known Before Scaling Uber [video]
by threeseed on Wednesday September 28, 2016 @06:24PM
(#12601832)
The point is that unless you use JVM hot reloading (not recommended in Production) you will need to take down your whole app to upgrade that JAR. Now what if your microservice was something minor like a black word filter. Is adding a swear word worthy of a potential outage ?
[ Parent
| on HN ]
Re:What I Wish I Had Known Before Scaling Uber [video]
by nine_k on Thursday September 29, 2016 @11:42AM
(#12606126)
If you run multiple instances of your server and follow certain reasonable practices, you can take down old-version instances one by one and replace them with new-version instances, until you have upgraded the entire fleet.
Alternatively, you can deploy the new version to many machines, test it, then make your load balancer direct the new traffic to the new instances, until all old instances are idle, and then take down these.
Re:What I Wish I Had Known Before Scaling Uber [video]
by benx on Monday October 03, 2016 @03:58AM
(#12625948)
And in microservices you can just pick whatever stack you feel is the best for just that task