This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: On updating
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
This post got a lot of attention from the curly brace crowd. When I asked "So how do you run a 24x7x365 Java/C# application server?", I got a bunch of responses. They all involved having multiple application servers (load balanced), and updating each in sequence while doing server configuration tricks to ensure that the app server being updated didn't get accessed. So I have a simpler question. Say - like this server - you have one app server you want to update without downtime. Let's say that said update involves shape changes to various objects that may or may not be in memory. So how do you keep that up while updating it? Sure, I get the notion of sequential updates.... but say the server (like most of them out there, to be honest) isn't a suite of load balanced systems. What then?