which is the best lang/technology for distributed computing? is there an option better than ejbs? i've seen a lot of posts regd. how painful it is to work with ejbs,on this site. but how well ejbs perform once implemented properly?
That depends on what exactly you mean by "distributed computing". The only ways EJB could be considered distributed is that they might be deployed on a server farm, thus making the app distributed, or that they are accessed from afar, e.g. over a network/the Internet. Does one of these fit your definition of distributed computing? There's also parallel processing. I wouldn't consider EJBs to be the best fit for any of these scenarios, although they're reasonable for the first and workable for the second. (Obviously this is very much my own opinion here.)
Originally posted by Ankur Jain: which is the best lang/technology for distributed computing? is there an option better than ejbs? i've seen a lot of posts regd. how painful it is to work with ejbs,on this site. but how well ejbs perform once implemented properly?
I know of a company in Los Alamos, NM that was looking into using web services as part of a grid computing paradigm. For widely distributed stuff (as opposed to, say, massively-parallel-all-on-the-same-backplane stuff), it seems like a prudent (open standards based) way to go about it and doesn't tie one to a particular language implementation...
I don't know what happened to them - this was ancillary to their core business model and was a means to an end for them. I had my doubts, and typing their url into my browser got Apache's 403 error:
You don't have permission to access / on this server."
Originally posted by Ankur Jain: which is the best lang/technology for distributed computing?
What is the best material for building? It all depends on the structure and the purpose of your project. Wood is excellent in may cases. Having said that you alluded to EJB so let's assume that by distributed computing you mean the garden variety J2EE application.
EJBs are excellent. Configuration was often complex and tedious however that is being solved in EJB 3.0 and it a very big way � following Hibernate model for Entity beans for example. The combination of entity beans, stateful and stateless session beans and asynchronous message driven beans is powerful. Consider all of the built-in distributed transaction management, passivation, pooling, clustering and so on.
Having said that, full-on J2EE applications require skilled practitioners. You should not use it without some exploratory development and emersion in Sun's blueprints or other best practice resouces is a MUST.
JINI? Yikes! Very ambitious technology that takes distibuted computing to a whole new level. Distributed Plug 'n Play objects. Drop in a FooBar in Japan and some computer in Belgium discovers it, interrogates it and starts using it to crunch weather data for display on a cellphone. Wacky stuff but plenty of very pratical down-to-earth applications.
Author and all-around good cowpoke
Joined: Mar 22, 2000
JINI? Yikes! Very ambitious technology
I consider JINI less ambitious and more suitable for distributed computing than EJB. However we may be dealing with a variety of definitions of "distributed computing" here. Bill
Joined: Sep 19, 2004
I think so. Boils down to my original paraphrase: what is the best material for building? The answer of course will differ between, say, football stadia and four-slice toasters. Distributed computing is a very broad topic with myriad technologies.