Hacker News Reader

>Ultimately, you hit the ceiling of what you can do with it, and you have to migrate off (if you’re a business that is trying to grow, anyway).

I read this post and the one that was linked to and I still don't understand what the problem was that they faced with Google App Engine. A few specifics would have been helpful.

View on HN

So he hinted at it with, "App Engine was stateless". You can't hold a model in memory on the server with App Engine. You can if you own the server.

Also, App Engine has request length limits (like many platforms). This means you can't hold a persistent connection for real time communication, and you can't run long tasks. Even using App Engine Backends or Tasks are time-limited to about 10 minutes, and your long-running task will often be killed unexpectedly.

Last I checked, App Engine was using an old version of Go, and I don't know if they'll ever move off Python 2.7.

As a platform App Engine is great, but it's not the perfect fit for everything.

Disclosure: I used to work for Workiva.

Thanks for the clarification. He advocated stateless anyway, but the other limits you describe could make things hard and preclude any type of actor model.

Reply on news.ycombinator.com