Today we are releasing a reference architecture and sample app for running e-commerce apps on Heroku, with a simple pattern for integrating customer, order and product data with Salesforce via Heroku Connect. The documentation and open source repo can be found on GitHub. The key: Any transaction recorded in Heroku Postgres can be seamlessly integrated with Salesforce via Heroku Connect.

Salesforce for E-Commerce

Many Salesforce customers are looking to extend their Salesforce deployments with e-commerce on Heroku. Whether running a single storefront, launching new concepts and brands, or innovating to improve core retail functions, these e-commerce experiences require orchestration...


Editor's Note: Heroku Pipelines is now Generally Available. Learn more about Continuous Delivery at Heroku.

At Heroku we're building a solid platform for delivering apps in a deliberate, reliable manner. We know that reasoning about the state and progress of code changes, testing and verifying what's deployed, and tracking what works can all be difficult — especially for non-engineering team members.

So we’re proud to introduce Heroku Flow, a new and flexible way to structure, support, and visualize Continuous Delivery for Heroku apps from development to production. Heroku Flow does for Continuous Delivery (CD) what pull requests have done for code review: make CD visual, easy...


Last year, we launched the original Performance dyno, designed to support the largest apps running at-scale with more consistent service and faster response times. Today, with the goal of continuing to support our fast growing customers with more flexibility to choose the type of dynos best for their applications, we are excited to announce improvements to our performance dyno lineup:

  • Performance-L — an improved and more powerful version of the existing Performance dyno, renamed the Performance-L dyno
  • Performance-M — an entirely new dyno and smaller sibling to the Performance-L dyno

The Performance-L dyno now has 14GB of RAM, 133% more RAM than the previous version, answering a request...


Today we're releasing some exciting improvements to the Heroku beta Docker support announced 3 months ago: Automatic configuration of local containers running data stores (like Postgres, Redis and MongoDB) and support for many more languages including images for Node.js, Ruby, Go, Java, Scala, Clojure and Gradle. This helps you use local containers to run, test and deploy Heroku apps that have complex service dependencies with minimal setup and configuration.

Heroku Docker support brings to your machine the Linux containerization technology that we have operated for many years. These local Docker containers make on-boarding, development and testing of apps simpler and faster, and with...


In a recent patch we improved Rails response time by >10%, our largest improvement to date. I'm going to show you how I did it, and introduce you to the tools I used, because.. who doesn’t want fast apps?

In addition to a speed increase, we see a 29% decrease in allocated objects. If you haven't already, you can read or watch more about how temporary allocated objects affect total memory use. Decreasing memory pressure on an app may allow it to be run on a smaller dyno type, or spawn more worker processes to handle more throughput. Let's back up though, how did I find these optimizations in Rails in the first place?

A year ago Heroku added metrics to the application...


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