Red Hat 'Fedora-izes' JBoss With New WildFly Java Application Server

darthcamaro writes "The JBoss Application Server is no more. Just like Red Hat killed Red Hat Linux in 2003 to make way for Fedora, the same is now happening with JBoss and the new WildFly project. 'There was of course the application server, there are a number of JBoss commercial products, there was the community site, etc., so when you asked someone "What is JBoss?" the answer was varied,' Jason Andersen, director, product line management, at Red Hat, explained. 'What we wanted to do was cement the idea that JBoss is a portfolio of middleware products and not just the application server.'"

Comments

"The JBoss Application Server is now more."

[Cammi]

Umm .... what?

Re:"The JBoss Application Server is now more."

[Anonymous Coward]

That's ridiculous. Obviously they mean "now moor." As in, it's a Muslim invader of Spain a millennium ago.

Re:"The JBoss Application Server is now more."

[VortexCortex]

"JBoss Application Server is now more."
It means the price went up. Unsurprisingly since it has to do with 'Enterprise' -- That means two things at once: Expensive and Fantasy Utopia that is every nerd's dream.

Re:"The JBoss Application Server is now more."

[Local ID10T]

Wrong, its "noir moore", a retelling of the James Bond universe in 40's noire format.

That actually sounds interesting...

Re:Huh?

[IMightB]

Here's how I understand it. Tomcat would be "just an application server" stuff that runs on top of tomcat would be the middleware. So JBOSS includes a application server and a bunch of other useful stuff. JBOSS is/used to be a pay-redhat to use it, and therefore never really gained a big community. Redhat is just renaming it and releasing it to the Fedora community in hopes that it gains more users and therefore should translate into pay-redhat for support.

I just stick to Tomcat

[roman_mir]

I stick to Tomcat, never mind EJBs, don't need them. The fewer components and compilation steps the better AFAIC. You have to choose what to use for a connection pool and have a good grip on your own transaction handling of-course, but that's really not a problem, it's blown out of proportion.

Re:I just stick to Tomcat

[roman_mir]

Don't pay attention to that, J2EE is a crutch, it is an attempt to replace an actual architectural thought with a copy paste solution. It's not worth the trouble, it creates more problems than it solves and it forces people into a rigid pattern of thought that does not actually allow them to look at the real business problem they are trying to solve. The architect is reduced to a typist with J2EE, every step is predetermined, the so called 'scalability' is not in fact achieved, the only they it ends up doing is replicating the entire application across a set of servers and pushing the session objects into every node, that's the gist of their ability to 'scale'. It only scales vertically, it misses what ideas like MapReduce provide (for example), horizontal scalability.

Also J2EE recycles the same approach to data treatment from project to project, so everything is as slow as the slowest data access component (so they insert more and more layers between their entity beans and the physical database in hope they'll boost the performance) and in reality in most cases what is needed is an actual architectural solution that takes into account the specifics of the business problem, but that is completely avoided, totally neglected by the so called 'architects' that stick to the cut and paste J2EE paradigm. They completely forgot (if they ever knew) what the hell architect is supposed to do in the first place.

This is by the way how big shops like Oracle end up charging even more money by breaking the legs of the architectural team and then handing them yet another crutch, something like AquaLogic Data Services (Oracle Data Services now).

Today you can take a look at any so called 'enterprise' application and see tons and tons and tons of 'infrastructure' and almost no actual logic and in reality everything is just data in a database somewhere, and all the layers of manipulations and transformations are supposedly designed to 'scale' and in fact they are the bottleneck, they are the reason that the systems are slow.

But hey, it's enterprise, so you can always rely on the idiots that buy it to throw more money at the hardware when this shit inevitably grinds to a halt.

Jboss != Jboss AS != WildFly

[cuby]

JBoss started as a Java application server (AS). At some point it got much bigger and now is more like the Apache community. Lots of projects like Hibernate and Infinispan are part of it.
In the AS side of things, there were already 2 kinds of releases. Like Fedora, you have the 6 months(?) releases supported by the community and then, from time to time, you get the stable Red Hat EL to be used by clients with support contracts. WildFly will be much like fedora in this sense. Jboss AS will continue for the ones with support contract. Until now, if you used JBoss in a serious task, there was almost no difference in the quality between paid and unpaid versions, from now on, I think it will be a different story.