Hacker News new | ask | show | jobs
by brianm 1201 days ago
This is... EJBs. It is probably less painful to use, but the model is pretty much the same. Fascinating.
3 comments

I was thinking the same thing, which leads me to say "This is where I came in." That is to say, I have seen what happens next. Maybe it time for retirement.
Man I was thinking the exact same thing. We have looped around back to J2EE EJB's. Wow, so Google copies Enterprise Java! Kinda funny to see the old stuff re-branded as the shiny, new stuff - albeit in another language.
EJB3 wasn't that painful, it was actually quite nice. Ran one of the largest porn sites out there on JBoss4 tech and it worked really really well.
Hah, wave. That is a name (latchkey, not jboss) I have not heard in a very long time :-)

I was thinking of the EJB 1 & 2 era xml wiring of all the things.

hi brian! long time as well. i hope you're well. =)
Any links that described how they scaled their services?
3 medium sized dell frontend servers running jboss4 and one beefy backend mysql server. we ran our own bare metal because this was before 'cloud' services would allow porn sites to operate.

the ejb3 caching was so efficient that we really only needed one server, we just had the other two as backup so that we could do CI driven rolling deploys integrated with the load balancer. we used jgroups mcast to expire entities in the cache. jvms were carefully monitored and all the settings were heavily tuned for our environment.

the hardest thing about all of it was simply packaging it all up into a war file correctly. it is all knowledge that i've long since forgotten how to do.