> But why improve performance by switching to a language that's well suited to the task at hand when you can do it by switching to a language that's hip?
Because your question is loaded?
Re:Go from PHP engineer's perspective
by brianwawok on Thursday February 25, 2016 @09:05PM
(#11179391)
With some work you can write some Java that will easily take a message, parse it, do logic, and reply in under .1ms. Not that useful for a webapp though, databases are kinda cool.
Re:Go from PHP engineer's perspective
by williamdunne on Friday February 26, 2016 @07:40AM
(#11181056)
With Java you can receive an order, parse it, submit it to your trading engine, persist it, match it, and return the response in less than 4ms
Re:Go from PHP engineer's perspective
by brianwawok on Friday February 26, 2016 @10:22AM
(#11181788)
I worked on trading engines in a past life and worked with good ol Martin. You can do all of that in under a ms these days.
[1] My company ran into a problem where one of our Ruby service responses was taking something about 100ms. We ruled out the database, and the ruby code, and finally discovered that the problem was jumping back and forth between Ruby and C while generating the JSON response from model classes with customized `to_json` behavior. We solved it by traversing the structure in Ruby and turning it into Arrays and Hashes. Back down under 10ms!