Can you refer to some of the customers who are using your service?
Also can you elaborate the pricing difference between Heroku offering
vs direct offering from your website?
Is the service offering same in both the cases or any difference is
there?

Dash

On Nov 3, 8:16 am, Cashton Coleman <[email protected]> wrote:
> We can also provide 100% fault-tolerant MySQL services for your app. Check
> us out athttp://www.cleardb.com
>
>
>
>
>
>
>
>
>
> On Thu, Nov 3, 2011 at 6:08 PM, Martin Wawrusch <[email protected]> wrote:
> > xeround.com comes to mind, and perhaps simpleworker.com (iron.io)
>
> > On Thu, Nov 3, 2011 at 9:05 AM, Kerri Miller <[email protected]>wrote:
>
> >> A couple quick ideas to explore..
>
> >> - is the memory limit the same on workers as dynos?
>
> >> - could you thread out the computations to different workers?
>
> >> - don't use Heroku's postgres, but an Amazon RDS or similar 3rd-party
> >> DB, to get around the connection limitation
>
> >> -k-
>
> >> On Thu, Nov 3, 2011 at 8:20 AM, Matthew Pocock
> >> <[email protected]> wrote:
> >> > Hi,
> >> > We are trying to develop a heroku app. Its data is stored in postgres.
> >> From
> >> > the control panel of the app, admins can kick of jobs that do bulk
> >> > mainipulation of the database. These processes potentially use a lot of
> >> > resources, which doesn't work very well at all on heroku. For example,
> >> one
> >> > of the analysis runs may need 2G memory for some matrix math. The web
> >> > front-end is light-weight and scalable.
> >> > We considered offloading the heavy lifting to an AWS instance. However,
> >> this
> >> > will need to talk to the same postgresql database as the heroku app
> >> does,
> >> > and the docs say, "No, connecting to your database from machines
> >> outside of
> >> > Heroku is not supported". The only other option we can see is to host
> >> an AWS
> >> > instance in the same datacenter that our heroku app interacts with
> >> through
> >> > REST, and manage our own database and vm lifecycle, but then we aren't
> >> > really gaining much over hosting the entire she-bang ourselves.
> >> > If you have any ideas, I'd love to hear about it. Are there any guides
> >> to
> >> > integrating components deployed on AWS with heroku? Any war stories?
> >> > Thanks,
> >> > Matthew
> >> > --
> >> > Dr Matthew Pocock
> >> > Integrative Bioinformatics Group, School of Computing Science, Newcastle
> >> > University
> >> > mailto: [email protected]
> >> > gchat: [email protected]
> >> > msn: [email protected]
> >> > irc.freenode.net: drdozer
> >> > skype: matthew.pocock
> >> > tel: (0191) 2566550
> >> > mob: +447535664143
>
> >> > --
> >> > 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.
>
> >  --
> > 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.
>
> --
> Cashton Coleman, CEO
> SuccessBricks, Inc.
> [email protected]
> IL: +972 54 562 2193
> US: 1 469 828 3439 x500

-- 
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.

Reply via email to