On Fri, Mar 12, 2010 at 12:42 AM, schapirama <[email protected]> wrote: > Hi Tobin, > >> 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. > > That's definitely the solution I'd pick if I were you: a separate > component with a RESTful API to do the lookups. It will certainly add > the extra latency in the HTTP requests that you have to make, but I > think that the cost is well covered by the extra simplicity, as long > as the interface from this service to the outside world remains > stable. It'd make your deployment and DB migration easier and faster > (as you mention), and simplify development and debugging of your main > app.
And you can use memcached to hold the info on the client app to reduce the latency for repeated requests (if it makes sense), so then you pay the nice folks at heroku some money, too ;) > In fact, if this lookup service is generic enough, you may offer it as > a service for other apps running on Heroku that may need it... > > - A > > -- > 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. > > -- 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.
