Application design for blade architecture Vs. SMP
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   john_Walsh
Posted On:   Tuesday, January 13, 2004 12:06 PM

Hi.


I'm looking into what differences a blade server approach will make to our current and future architectures. We currently deploy our apps on single, multiprocessor servers. What potential challenges, issues and opportunities will a move to a multiple blade server enviroment offer us. Will it require a change in how we approach our multi-threading designs? We are not a J2EE shop but do utilise Toplink for data caching and retrieval. We also reply heavily on RV for messaging.


Regards


John Walsh

Re: Application design for blade architecture Vs. SMP

Posted By:   Anjan_Bacchu  
Posted On:   Tuesday, January 13, 2004 01:40 PM

Hi John,


I am not a deployment and production maintenance kind of guy, but here are what we faced when we used clustered deployment.


Licensing : You have to be aware of the licensing per node issues -- it might cost you more.


Distribution Costs -- By distributing it across multiple nodes, a RPC call can call a lot more than across a CPU on the same system.


Deployment Issues -- Logging gets a little more difficult to manage, especially if you have multiple Logging files and you want to get some information from the log files on a regular basis.


Engineering -- you will have to engineer your software a lil more ruggedly since the chances of failure is now more distributed.


BTW, what is RV ?


There might be more but these are the issues we faced.


BR,


~A
About | Sitemap | Contact