Fonte: javaLobby Active Grid

J2EE Obsoleto...?

With the launch of their new web service platform, ActiveGrid is spreading the news that both J2EE (although they do seem to use the terms Java and J2EE rather interchangeably, heh…) and .NET are yesterday’s legacy systems when it comes to developing enterprise level horizontally scalable web services.

Peter Yared, ex-Sunite and one of the founders of ActiveGrid, said in a one-hour-long audio interview that the only way J2EE can scale is up, by getting more powerful computers, and systems written on it can only scale in the way they’re designed to, while their transaction grid system can easily scale horizontally and it’s not necessary to consider scaling when designing systems with this technology.

If this were true, then it could possibly mean the end of Java on the server. But I have to say, the claims sound exagerated at least since, after all, can’t we do for Java what ActiveGrid did for LAMP? Isn’t it all about proper libraries?

Some of the other points they claimed were an advantage of the LAMP stack is language independence, which I have to say is indeed a good thing, but this doesn’t exclude Java from being performant & scalable even when acting alone.

ActiveGrid’s prime product is an IDE for their stack that does however promise to make server application development a rather simpler and less costly proposition and this alone could make it a serious threat to Java. The question is, will IDEs like Java Studio Creator be able to succesfully compete with this? Or does Java need a radical new approach, both in libraries and IDEs, to designing web services and applications?

Sebastian Ferreyra

Active Grid

5 Respostas

marcelomartins 18 de mai. de 2005

Essa galera não tem mais o que fazer não?

marcelomartins 18 de mai. de 2005

E mais, vamos imaginar fazer busca de informações no banco de dados e recebe-las em XML…

cv1 18 de mai. de 2005

O diagrama nao deixa duvidas: isso eh uma furada total e completa. Alias, qualquer arquitetura que foca no uso de objetos distribuidos, e nao em minimizar ao maximo possivel a distribuicao de processamento por requisicao pela rede, ta ferrada.

jprogrammer 18 de mai. de 2005

Isso é mais um serviço de marketeiro…

mcampelo 18 de mai. de 2005

Qualquer arquitetura que coloca XML no meio já me deixa assustado.

Sofri muito com isso no último projeto Java por onde passei. Era XML por tudo que é lado, aplicando XSLTs para colocar no formato que o cliente do Middleware esperava.

Pelo amor de Deus, esqueçam XML … principalmente quando você está fazendo a comunicação entre 2 processos Java …

[]'s
Marco Campêlo

5 Respostas

Topicos relacionados