4 ms·

Is it? Concurrent connection handling at scale is a major problem, and plenty of Fortune 1000 companies would jump at the chance to have even 5% fewer instances

Is it? Concurrent connection handling at scale is a major problem, and plenty of Fortune 1000 companies would jump at the chance to have even 5% fewer instances deployed. 366 rps in a test scenario doesn't scratch the surface of what I need, and I'm not doing anything I'd consider crazy scale. When you need to support hundreds of thousands of rps, small improvements can be very noticeable.

bpicolo 8y ago
> plenty of Fortune 1000 companies would jump at the chance to have even 5% fewer instances deployed. Becoming a Fortune 1000 company isn't "most apps"
mkirklions 8y ago
I'll tell you what. When I'm a fortune 10,000 company, we can afford to rewrite the web app.
- ddorian43 8y ago
  But do they rewrite ? Twitter did. Facebook didn't.
  - chipotle_coyote 8y ago
    Facebook wrote a new PHP VM and forked the language, so while it may not technically be rewriting...
  - tomnipotent 8y ago
    > Facebook didn't. You have no idea what you're talking about. Not only did they produce TWO different implementations of PHP (HHVM and Hack), a vast majority of their infrastructure is NOT in PHP (which is mostly reserved for the front-end/web tier).
    - ddorian43 8y ago
      I know. Still, cheaper than rewrite.