Component Distribution - always treat it as a last resort?
posted 1 year ago
I heard one of the senior architects in my company before tell me to treat component distribution as a last resort. So if EJB were created for such, why were they created if component distribution is not encouraged anyway? just got confused here. I remembered this because I am currently in a dilemma of whether to redesign an app having performance problems. Options are either create EJBs for it and put them in another server or purchase another server to have a load balanced setup.
Well, Ejbs were introduced as distributed transactional server side components, but of course that doesn't mean you have to use a distributed architecture just because you want to use EJBs - just think about ejbs local interfaces.
I agree with that senior architect:avoid to distribute tasks and processes if you can.