@headius I’d guess a case of “we took our app written in X and rewrote it in Y and it’s better” which would be true for any value of X and Y
The @PayPal numbers for their Java to Node move are absurd. A JVM app doing 1.8 pages/s isn't slow...it's broken. https://www.paypal-engineering.com/2013/11/22/node-js-at-paypal/ …
-
-
-
@manhattanmetric They started the Java version first, at least. But wtf... five engineers took over 6 months to build their account page?! -
@headius If they were using Spring, I can believe 5 engineers x 6 months. That framework seems optimized for slowing down development… -
@manhattanmetric Yeah, it's obvious the JVM-side app had some serious *architectural* flaws. Set up for failure, I reckon.
End of conversation
New conversation -
-
-
@headius maybe PayPal is trying to run a JVM on raspberry pi -
@slowteetoe@headius I think even a Pi should do better. IBM remote-controls cars using WebSphere Liberty on Pi. -
@deanrl@slowteetoe Probably true. The Java numbers at PayPal indicate to me they've got a serious *engineering* problem.
End of conversation
New conversation -
-
New conversation
-
-
-
@headius that’s absurdly broken, and it’s not like 3.3 for Node is what I’d call working. They’re, what, 2 orders of magnitude out? -
@garyfleming At least!
End of conversation
New conversation -
-
-
@headius Aside from preposterous numbers and apples-to-oranges, there's just not enough data. -
@thricejamie Yeah, seems like a lot of node-based second systems get press lately. JVM app should be able to destroy a node app. -
@headius I guess what I learned from that article is eBay is bad at Java.
End of conversation
New conversation -
-
-
@headius@peakscale if only they had node on day 1 -
@ripienaar@peakscale And they even state that the Java app built on their legacy Spring-based framework. Blame probably lies there. -
@headius@ripienaar@peakscale I think the conclusion is that anyone coming to you with benchmarks and no details isn't worth listening to
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.