Comments on: Industry Ignorance http://blog.anthonychaves.net/2009/01/22/industry-ignorance/ Life is software and jujitsu Mon, 01 Feb 2010 17:22:12 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Patrick Peralta http://blog.anthonychaves.net/2009/01/22/industry-ignorance/comment-page-1/#comment-9401 Patrick Peralta Sat, 24 Jan 2009 02:29:19 +0000 http://blog.anthonychaves.net/?p=106#comment-9401 Hey Anthony, Don't let the trolls at the JoS forums get you down. Half of them are professional cynics who like to do nothing but bitch about the industry ;) Hope to make it out to the meeting next week... -Patrick Hey Anthony,

Don’t let the trolls at the JoS forums get you down. Half of them are professional cynics who like to do nothing but bitch about the industry ;)

Hope to make it out to the meeting next week…

-Patrick

]]> By: Nati Shalom http://blog.anthonychaves.net/2009/01/22/industry-ignorance/comment-page-1/#comment-9400 Nati Shalom Fri, 23 Jan 2009 23:14:14 +0000 http://blog.anthonychaves.net/?p=106#comment-9400 I'll be watching your blog closely from now on:) BTW when is your next Boston meeting? I'll be in the east coast in two weeks time (8th of Feb) - if it makes sense I'll be happy to present on one of the topics - Dynamic scaling on the web tier could be a good candidate if your interested. I’ll be watching your blog closely from now on:) BTW when is your next Boston meeting?
I’ll be in the east coast in two weeks time (8th of Feb) – if it makes sense I’ll be happy to present on one of the topics – Dynamic scaling on the web tier could be a good candidate if your interested.

]]> By: Anthony Chaves http://blog.anthonychaves.net/2009/01/22/industry-ignorance/comment-page-1/#comment-9394 Anthony Chaves Fri, 23 Jan 2009 15:39:43 +0000 http://blog.anthonychaves.net/?p=106#comment-9394 Hi Nati, Thanks for the response. I wasn't aware of Max's blog, though I subscribe to some of the others he lists. The presentations were helpful as well. What you describe about dynamic scalability is exactly the kind of topic we'd be interested in hearing about at BostonSUG. It takes a concept we're familiar with and takes it a few steps further. Demos and walk-throughs would make a discussion on this topic outstanding. Thanks again, Nati! Hope to see you commenting around here more in the future. I've got a lot of interesting topics to write about this year. Anthony Hi Nati,

Thanks for the response. I wasn’t aware of Max’s blog, though I subscribe to some of the others he lists. The presentations were helpful as well.

What you describe about dynamic scalability is exactly the kind of topic we’d be interested in hearing about at BostonSUG. It takes a concept we’re familiar with and takes it a few steps further. Demos and walk-throughs would make a discussion on this topic outstanding.

Thanks again, Nati! Hope to see you commenting around here more in the future. I’ve got a lot of interesting topics to write about this year.

Anthony

]]> By: Nati Shalom http://blog.anthonychaves.net/2009/01/22/industry-ignorance/comment-page-1/#comment-9393 Nati Shalom Fri, 23 Jan 2009 12:03:20 +0000 http://blog.anthonychaves.net/?p=106#comment-9393 Hi Anthony Looks like you established an interesting group on one of my favorite topics - Scalability. I'd be happy to assist in which ever way possible. I'd recommend looking at the following list of resources that was published by Max Indelicato (my blog included at the top) <a href="http://blog.maxindelicato.com/2009/01/17-distributed-systems-and-web-scalability-resources.html" rel="nofollow">17 Distributed Systems and Web Scalability Resources</a> WRT to the web scaling diagram that you laid out i'd like to add that some of the challenges that we dealt with recently is how to make web applications dynamically scalable and self healing (without human intervention). Essentially what we did is add an agent in front of the load-balancer that listen for new web-containers. We wrapped the web-containers with SLA driven containers that monitors the load on each container. If a certain web container breached its SLA - a new container is brought up. The agent automatically add this server to the load-balancer which in return split the load to the additional server. Similar things happen when one of the servers stop responding. A new machine with new web-container is brought up automatically to replace the server. In the meanwhile the load-balancer is updated of this change. You can see more on that <a href="http://www.gigaspaces.com/wiki/display/XAP66/6.6+Documentation+Home" rel="nofollow">here</a> You can see a live demo <a href="http://www.gigaspaces.com/tempfiles/webcasts/cloudtoolsweb/GigaSpacesCloudTools3.html" rel="nofollow">here</a> HTH Nati S www.gigaspaces.com/cloud Hi Anthony
Looks like you established an interesting group on one of my favorite topics – Scalability. I’d be happy to assist in which ever way possible.

I’d recommend looking at the following list of resources that was published by Max Indelicato (my blog included at the top) 17 Distributed Systems and Web Scalability Resources

WRT to the web scaling diagram that you laid out i’d like to add that some of the challenges that we dealt with recently is how to make web applications dynamically scalable and self healing (without human intervention). Essentially what we did is add an agent in front of the load-balancer that listen for new web-containers. We wrapped the web-containers with SLA driven containers that monitors the load on each container. If a certain web container breached its SLA – a new container is brought up. The agent automatically add this server to the load-balancer which in return split the load to the additional server. Similar things happen when one of the servers stop responding. A new machine with new web-container is brought up automatically to replace the server. In the meanwhile the load-balancer is updated of this change.
You can see more on that here

You can see a live demo here

HTH
Nati S
http://www.gigaspaces.com/cloud

]]>