Editor's note: This is a guest post from Ken Fromm and Paddy Foran at Iron.io. Iron.io's services are designed for building distributed cloud applications quickly and operating at scale.

Platform as a Service has transformed the use of cloud infrastructure and drastically increased cloud adoption for common types of applications, but apps are becoming more complex. There are more interfaces, greater expectations on response times, increasing connections to other systems, and lots more processing around each event. The next shift in cloud development will be less about building monolithic apps and more about creating highly scalable and adaptive systems.

Don’t get us wrong,...


On November 18th, a replication bug was found in Postgres that affected the most recent versions of every Postgres release. The corruption that this bug may introduce could go undetected, and it manifests itself as a follower potentially having an inconsistent view of the data. For example, data could be present in the primary and not on the follower, or data deleted or updated on the primary and not from the follower. The likelihood of triggering this bug is higher for write-heavy workloads, such as many OLTP applications seen at Heroku.

We always recommend placing applications in maintenance mode and scaling down workers when performing a follower based changeover, and following this...


Many of our customers have recently asked about our connection limit settings on our new Heroku Postgres tiers. Previously we allowed for 500 connections across all production databases, however now there is some variance in the number of connections allowed with only the larger plans offering 500. In individual conversations with customers we’ve detailed the reasoning behind this, and feel its worth sharing this more broadly here now.

For some initial background, our connection limit updates are actually aimed to be an improvement for anyone running a Heroku Postgres database, by both providing some guidelines as well as setting some expectations around what a database instance is...


Editor's Note: We are cross-posting this article from the Salesforce Blog. It shows how we are bringing Heroku to a new market and audience - Salesforce customers - using a new product and message. If you are a user of both Heroku and Salesforce and are interested in connecting them, check out Heroku1.


Apps are an essential part of the Internet of Customers. They are the dashboards to people’s lives. They allow your customers to be part of your business’ workflows, and for you to engage with them on an unprecedented level. Customer connected apps are the next phase of how companies are innovating and gaining competitive advantage.

Today, we are launching Heroku1, a complete service...


At our core, Heroku's goal is to make it easier for developers to build great apps. We do this by creating tools which allow developers to focus on writing code, rather than wasting time on managing infrastructure. To coincide with this week's Dreamforce event, we are launching several tools targeted at developers who write apps on Heroku that integrate with Salesforce.com.

If you aren't part of the Salesforce world, don't worry. We remain 100% committed to our core audience of web and mobile developers and will continue to release great new features and functionality like websockets and high-availability databases.

Force.com, a full stack platform for building...


Browse the blog archives or subscribe to the full-text feed.