Disqus - Latest Comments for jamesheroku

Re: Heroku | Announcing Heroku PostgreSQL Database Add-On

james@heroku — Wed, 10 Nov 2010 20:19:23 -0000

Heroku is an open platform with which you can use any database offering you like, including your own custom solution or any of the solutions in the add-ons catalog. These currently include MySQL from Amazon's RDS, MongoDB from MongoHQ, CouchDB from Cloudant, Redis from RedisToGo, and more).

If you wish to use Heroku's PostgreSQL service, you are choosing the largest battle-tested SQL-as-a-service offering in the world with tens of thousands of apps across thousands of customers today.

Every dedicated Heroku PostgreSQL plan includes these features:
- fully monitored and managed 24/7
- performance optimized (pre-configured for Heroku environment, multi-volume EBS RAID striping, etc.)
- fully integrated into your app's Heroku runtime environment
- integrated tooling for easy data backup/restore, and import/export
- secure and easy tooling for direct ingress using the psql client
- integrated workflow for provisioning and migrating databases as you scale
- daily backups for disaster recovery
- technical support

Re: Heroku | An update on Heroku Node.js support

james@heroku — Tue, 21 Sep 2010 02:17:07 -0000

We wish Node.js support could be done sooner too. There are complex dependencies on other work in our pipeline, and we're committed to doing it right.

Re: Heroku | An update on Heroku Node.js support

james@heroku — Mon, 20 Sep 2010 17:02:34 -0000

Thanks for the feedback Donalds. We are working on major improvements there as we speak.

Re: Heroku | Node.js Support (experimental)

james@heroku — Wed, 28 Apr 2010 20:08:52 -0000

This has actually been in the works for quite a while; we're psyched about node.

Re: Heroku | Node.js Support (experimental)

james@heroku — Wed, 28 Apr 2010 20:08:34 -0000

Using node and ruby in the same app is absolutely the intention. Right now, the way to do it is as a composite app.

Not all of the long-connection features are supported today, but they will be. Email the beta list and start using it so we can get your feedback!

Re: Heroku | Update & Roadmap

james@heroku — Wed, 28 Apr 2010 19:46:37 -0000

For those of you who asked for node.js, we've had it in the works for quite a while. Check out today's post:
http://blog.heroku.com/arch...

Re: Heroku | Node.js Support (experimental)

james@heroku — Wed, 28 Apr 2010 19:45:21 -0000

Detailed documentation is available to beta users. Short version: beech is currently for node only; they will likely be integrated later as this part of the platform matures.

Re: Heroku | Update & Roadmap

james@heroku — Wed, 28 Apr 2010 02:58:24 -0000

The best way to make this happen is to ask MadMimi to get started on their Heroku add-on. We'll add them to our list though, thanks.

Re: Heroku | Update & Roadmap

james@heroku — Tue, 27 Apr 2010 20:12:02 -0000

Revenue is growing at huge rates, similar to the traffic graph above. Company is in excellent condition financially, more news on that front soon.

Re: Heroku | Announcing Huge Growth and New CEO

james@heroku — Thu, 15 Oct 2009 05:00:09 -0000

Thanks for your comments Harry. You're absolutely right - we've got a new status site we're going to be using moving forward:
http://status.heroku.com/

We did have a brief issue yesterday affecting some apps, and unfortunately we hadn't launched this site yet. We have just completed our analysis, and posted the details to the status site.

Moving forward, we will use that site as the main channel for service status updates. It is hosted on a separate provider from Heroku's main operations.

Re: Heroku | Background Jobs with DJ on Heroku

james@heroku — Wed, 15 Jul 2009 21:07:13 -0000

Thanks! We are working hard on SSL. SNI may not be viable for a couple of reasons, but a solution is in the works. We'll post more as soon as we've finalized the plan.

Re: Heroku | Commercial Launch

james@heroku — Mon, 27 Apr 2009 23:50:09 -0000

SSL on a custom domain that is CNAMEd to Heroku is not currently possible, due to a fundamental limitation in the SSL protocol. This is an unfortunate problem that affects all cloud platform providers like ourselves. More info.

We have a couple of workarounds in the works, but neither are available yet.

Re: Deploying Multiple Environments on Heroku // Elijah Miller

james@heroku — Mon, 27 Apr 2009 15:04:26 -0000

Thanks for the awesome write-up! FYI, you can name git remotes when you create an app like this:

$ heroku create myapp-staging --remote staging

Re: Heroku | Commercial Launch

james@heroku — Sun, 26 Apr 2009 04:11:15 -0000

Thanks Michael!

Re: Heroku | Commercial Launch

james@heroku — Sun, 26 Apr 2009 04:10:40 -0000

Martin - thanks for spreading the word!

For repository size, the compiled slug size is displayed for your app during git push. For database size, we have a more detailed metrics view to be rolled out shortly.

There are soft limits on bandwidth, details on this and other service limits will be rolled out this week.

Blessings are going away, the equivalent now is entering your billing information (even for free add-ons). This is our way of preventing abuse (more info). Opening the ports for outgoing email is going to be an add-on feature very shortly.

Re: Heroku | Commercial Launch

james@heroku — Sun, 26 Apr 2009 04:05:16 -0000

Charlie - exactly right you are. Stay tuned. In the meantime, you can always run your own CouchDB or Tokyo Cabinet in EC2, and provide the config info to your apps on Heroku via config vars.

Re: Heroku | Commercial Launch

james@heroku — Fri, 24 Apr 2009 23:10:05 -0000

Thanks! We've had a couple of similar inquiries about database sizes, we'll shoot you an email to gather some more info from you.

Re: Heroku | Commercial Launch

james@heroku — Fri, 24 Apr 2009 13:42:16 -0000

Kevin, you're thinking exactly along the right lines. Yes, you're right, it does get pretty complex very quickly, even for the simple case, and that's why we have to take our time crafting the right solution. But we've figured out what we hope is a solid way to do it, that keeps it simple but allows a lot of flexibility. Looking forward to rolling that out in the near future.

Re: Heroku | Commercial Launch

james@heroku — Fri, 24 Apr 2009 13:39:33 -0000

Rob - thanks so much for your excitement about Heroku! We're glad it's working well for you, and excited to have you as a customer.

Re: Heroku | Commercial Launch

james@heroku — Fri, 24 Apr 2009 13:38:12 -0000

Tom - glad to hear it. Yes, you can run whatever you like on your own EC2 instances and hook them into your Heroku app. Traffic between your instances and Heroku will be ultra-low-latency intra-AWS traffic (no bandwidth charges).

We are likely able to accommodate your database though, we'll shoot you an email to gather some more details from you.

Re: Heroku | Commercial Launch

james@heroku — Fri, 24 Apr 2009 13:35:25 -0000

Thanks for the suggestion.

Re: Heroku | Commercial Launch

james@heroku — Fri, 24 Apr 2009 13:34:53 -0000

Eric - thanks for your comment and enthusiasm about Heroku. Yes, reliability as a commercial platform is of paramount importance to us. As paid services are rolled out across our user base over the next several days, you will see some additional changes rolled out to address these issues.

A support site with knowledge base and a complete ticketing system, a status blog, our terms of service, and our SLA should together provide a solid support and reliability foundation.

Re: Heroku | Commercial Launch

james@heroku — Fri, 24 Apr 2009 05:08:42 -0000

Glad to hear it!

Re: Heroku | Commercial Launch

james@heroku — Fri, 24 Apr 2009 04:24:56 -0000

500 errors always indicate a problem with your app. 503 errors, which serve the Heroku fail whale, indicate a problem on our side, usually that the platform is having trouble with your app.

Having multiple dynos (even just 2) is important for a production app for redundancy, performance, and concurrency. Yes, our routing mesh will route requests intelligently, so in some cases having more dynos will reduce/eliminate issues.

Re: Heroku | Commercial Launch

james@heroku — Fri, 24 Apr 2009 04:21:35 -0000

Thanks Paul. With the exception of the large group of beta users who have been testing dyno scaling for us, everyone is running on one dyno only by default. So your app has likely been running on just one dyno.

Load metrics and performance analysis tools are in the works, but for now you'll want to do what you would do for any Rails app - use the logs, response time, and/or a performance analysis tool like New Relic's RPM to understand your app's performance profile and scalability.

At this time you have to issue a command/API call to scale to a different level of dynos. Auto-scaling is complex, because the heuristics are different for every app. We are testing some great features designed to address this though.