As far as I know the beta is closed, but if you're willing to wait memcached will be rolled out to the general public "soon" (from what Oren has said). I agree with everyone else, it sounds like that is your best bet for something that's fast. I'd also look at something like redis if you want to do something outside of heroku.
-Terence On Wed, 2010-03-10 at 08:22 -0800, Daniele wrote: > Thanks Chris, > the memcached solution is right but: > > - it is in private beta (by the way I will send a mail to join the > beta) > - i don't know how much it will cost by I suppose that it will be too > much (form me) to just handle some Kb > > What's I'm doing is a micro firewall that act as a filter before every > request. So what I need it to keep a moderate size array in memory, > read and write it *quickly*. > Any suggestion are welcome. > > On 10 Mar, 16:38, Chris <[email protected]> wrote: > > > Daniele, > > If you really need a global variable to be accessible across servers > > then memcached works good as long as it doesn't matter if that global > > variable gets expired. You need to store the variable persistent in a > > database. Pull it from memcached if it's there, if not then hit the > > database. (Alternatively, depending on the variable, just re-create > > it if it's expired and doesn't need to be persisted somewhere.) > -- 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.
