4 ms·
I see your point, it makes sense to me in application development. However, regarding a web request, for me it's totally fine to throw it away :). Same as the s
by skor 7y ago
I see your point, it makes sense to me in application development. However, regarding a web request, for me it's totally fine to throw it away :). Same as the statelessness of REST.
- TylerE 7y agoWell, I don't what to tell you except that that is a very shallow view. Every non-trivial web app I've ever worked with has tons of persistent state. DB connection pools. Translations. Configuration. Recreating that on every request is just wasteful.
- jimbokun 7y agoFor a quick and dirty proof of concept, do these things really matter? Have you measured the overhead and impact on performance compared to other development stacks?
- FpUser 7y agoWhat happens when your "quick'n dirty proof of concept" has to become production? Rewrite? As for the other stacks: I do what everyone says not to do. I write stateful servers in native compiled languages with no GC. So far I've yet to encounter any scalability problems. They simply do not exist when said servers are runninig on 32 core monsters with gobbles of RAM and not slowed down by interpreters, garage collection and bazillion of abstraction layers. Sure I could not serve Facebook using this, but hey it works just fine for the 90% of the rest and that is where I make my money ;)
- wolco 7y agoPHP's caching system doesn't make it recreating from nothing on every request. PHP can take advantage of connection pools but rarely does it make sense to hold a connection open.