Our app was quite small and manageable until we had to add a postcode lookup. Basically, our DB is about to jump from 1.2MB to 900MB, all because of a 2 million row database table.
This has 2 side-effects. 1. We need to upgrade our plan 2. During development Heroku db:pull and db:push is going to take an age. Goodbye fast and light data deployments to our staging area. The first point we're happy with with, it's nice to give back to the awesome folks at Heroku :) It's point 2 that's the killer. It's going to slow us down sooo much. One longer term solution might be for taps to support exclude patterns on push/pull. E.g heroku db:push --exclude="postcode*" We could then pretend that the table doesn't exist by excluding it from push/pull activities. A shorter term solution might be using Amazon RDS, but I think it's $80 minimum for an always-on database Another solution is to create a dedicated Heroku app that holds this data, and presents a service that our app can use. This means setting up another app, telling the developers about it, managing it, backups etc. A bit of a pain really, but it would work in the short term. Has anyone actively been through the loop of developing an app with this much data on Heroku? Any more ideas on how to address the problem? Tobin -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
