Dana Miller6 said:So, I was digging through some old files and stumbled upon this massive Benchmark that got released last year by The Middleware Co.—you know, those guys who basically live and breathe J2EE solutions and high-level consulting. They decided to go head-to-head with a comparison between Middleware's own take on the java pet Store 2.0, which is their beefed-up version of Sun's classic java pet Store using J2EE and EJBs, versus the whole .NET pet-shop setup. And honestly, here is what they’re claiming...😁So, look, I’ve laid out all the nitty-gritty details regarding how the database implementation and access actually work in both scenarios, along with all those revisions and tweaks we made to beef up the original pet Store application. You really need to sit down and read through the whole document from start to finish before you start throwing shade or critiquing anything—and please, let's keep the "religious wars" out of this, alright? No need to get all dogmatic about which tech is better. Here’s the link to the full report (it's a PDF): So, I’ve been staring at these performance numbers all morning, just absolutely spiraling down the rabbit hole of this whole J2EE vs. NET showdown, and honestly? It’s kind of wild how much people love to argue about it when the reality is so much messier. You look at these benchmarks and everyone starts shouting about one being faster than the other, but they’re missing the forest for the trees, you know? Like, sure, if you're running some hyper-optimized little script, maybe one pulls ahead by a millisecond, but we aren't building toy apps here! We're talking about massive, enterprise-level architecture where things actually get complicated. I was reading some stuff earlier—probably should have been working—about how the middleware layer handles the heavy lifting, and it really makes you think about whether anyone is actually looking at the full stack or just obsessing over raw throughput. It's like people comparing two different muscle cars without ever checking if they actually have enough gas to get out of the driveway. One might be faster on a straightaway, but the second you hit a corner or add some weight, the whole dynamic shifts. Anyway, I'm just rambling now, but I really feel like the benchmark obsession is a bit of a distraction from the actual dev experience and how these systems scale when things inevitably go sideways in production. It's all fun and games until your server starts sweating under real load!I'm gonna try to throw in one of those charts showing the results right here in this post, too.
Evo: I can't believe I'm even looking at this, but check out this graph—it’s absolutely wild how much the load spikes when you actually start pushing the system. It’s one of those things where you think everything is running smoothly, just cruising along like a Sunday drive on a California highway, and then suddenly, boom, the numbers go vertical and you realize you're staring down the barrel of a total meltdown if you don't scale up immediately. Honestly, seeing the data laid out like this just hammers home how fickle these environments can be, especially when you're dealing with massive traffic hits that catch you totally off guard! (you just gotta grab that link and paste it right into the address bar in either Netscape or IE).
Yo, Dana Miller6! After reading through that document you put together, we can all basically stand up and shout it from the rooftops: the King (yeah, I'm talking about J2EE) is officially naked!👋 👋 👋 👋
So, if you actually sit down and try to make sense of what he's putting out there, what you're really looking at is...
Look, I’m just going to say it because someone has to: J2EE is getting absolutely smoked by .NET right now. It’s a total blowout. Honestly, watching the two go head-to-head feels like watching a heavyweight champ stumble around while some hungry newcomer just breezes in and lands a perfect knockout blow every single time. It’s not even close anymore! You look at the way everything is moving, the sheer momentum behind the Microsoft ecosystem, and you realize that J2EE is basically just spinning its wheels in the mud while .NET is cruising down the highway. It’s just one of those things where if you aren't paying attention, you're missing the entire show, and the show is clearly leaning heavily toward the Microsoft side of things. Honestly, when you look at everything—I mean, we're talking about the whole nine yards here, from raw speed and how well it scales up to just how dead simple it is to actually write the code—it’s pretty obvious that the .NET solution is the way to go, because you end up writing way fewer lines of code to get the exact same functionality. 😉
So, look, I’ve brought up that whole Pet-shop situation before, but honestly, that guy just tore me apart for it! He went off on me, claiming the Pet-shop thing was nothing more than some sneaky, calculated move by Microsoft designed specifically to make .NET look like it was breathing down J2EE's neck, even though the actual reality on the ground was totally different. The whole timeline of this Pet-shop saga basically went like this: first, Sun Microsystems rolls out their version of the Pet-shop app just to hype up J2EE, right? And then, wouldn't you know it, Microsoft shows up with .NET and rewrites the exact same application from scratch using their own tech. Microsoft starts making all these bold claims, insisting their version was superior, faster, and way easier to build. Then, of course, you had those pathetic Java critics popping up...
I mean, honestly, it’s just like... yeah. Totally. Some guys were actually out there whining that it wasn't even fair for Microsoft to use stored procedures in their example, acting like the whole comparison was rigged from the start. But then, Dana Miller6 stepped in with this killer comparison that basically shut down every single one of those pathetic Java-obsessed haters by building an entirely new application and running a fresh set of tests that...
It’s pretty much an open-and-shut case at this point—they’ve absolutely proven it. Yeah, exactly!
Honestly, looking at everything, it just seems pretty clear.I mean, honestly, looking at everything that went down, the .NET solution was just lightyears ahead—like, a trillion times better than that whole mess of a J2EE (half)solution.
I'm sorry, I didn't catch that! It looks like you only sent "i"—did you mean to type something else? I'm ready whenever you are, just hit me with the full thought and we can get this show on the road!Autumn vibes.
Alright, my fellow forum junkies, here’s the deal: I am officially inviting you all to absolutely tear me apart for even bringing this up! Seriously, go wild! I want to see you roasting me, roasting the company that actually put this comparison together, and especially roasting Microsoft for basically "buying" this whole study—you know, because we all know how much they love to pay for results that favor them, right? Honestly, feel free to pile on with any other jokes that come to mind, because let's be real here: there is just no way in hell Microsoft could ever outshine anyone else, especially when you're talking about the "sacred" Sun Microsystems. Go ahead, give me hell!😁
Look, anyone with even a shred of common sense is going to sit down, dig into Dana Miller6's analysis, and really, truly weigh whether or not this person is just going to keep spouting absolute nonsense around here. I mean, obviously, you can't expect anything resembling logic from Patrick Morris3, slycrane94, or John Palmer4—their brains are basically fried at this point. But for everyone else? Well, there’s still a tiny, flickering glimmer of hope left. 😉)
Daniel Fowler9🙄