3 ms·
Heroku : Ruby/Rack :: Google AppEngine : Python/WSGI But there's a huge problem -- AppEngine succeeds at seamless multi-tenant truly-distributed clustered host
by blasdel 17y ago
Heroku : Ruby/Rack :: Google AppEngine : Python/WSGI
But there's a huge problem -- AppEngine succeeds at seamless multi-tenant truly-distributed clustered hosting thanks to BigTable. Heroku needs to support standard Rails apps, so Postgres is the best they can do, and it's a huge hole in their offering.
You just can't make Postgres (or Oracle) scale on an ideal horizontal the same way you can distribute IP, DNS, HTTP proxying, HTTP serving, memcache, message queues, or bigtable. You can't expose Postgres as an ideal service that just keeps up with what you throw at it.
- alnayyir 17y ago>You just can't make Postgres (or Oracle) scale on an ideal horizontal the same way you can distribute IP, DNS, HTTP proxying, HTTP serving, memcache, message queues, or bigtable. Is there something about MySQL that exempts it from this scaling weakness that I'm not aware of? I'm not bull-baiting, I'm just covering the bases and wondering if there's some reason it's not presently under discussion. Part of the reason I ask is because I've been pushing for a shift to Postgres at work after we get some more pressing matters dealt with.
- johnnybgoode 17y ago> Is there something about MySQL that exempts it from this scaling weakness that I'm not aware of? No, there isn't. We're discussing Postgres since that's what Heroku uses.
- alnayyir 17y agoIn that case, I'll carry on with my Postgres evangelism. Thank you for your time.