Welcome to the Community

At Heroku we have long considered PostgreSQL to be a powerful and reliable open-source database for keeping data safe and accessible for serious applications with demanding workflows and use cases.

Over the years we’ve invested heavily in continuing to improve it, whether it’s by employing Postgres major contibutors, employing driver maintainers, funding core development, or being part of language communites such as Ruby and Python to help spread the good news that is Postgres. It’s that interaction with the developer and database communities that help us inform and influence the future of Postgres.

This work over the years has continued to advance Postgres to be a better database for all and even expand it beyond its relational roots. It's been a great database for us to build our offering on and has enabled us to continue to add further value such as our new operational expertise that's built right in or dataclips. It’s both this great database as well as the additional value that’s allowed us to see the great growth we’ve seen today, now running a fleet of over 750,000 Postgres databases.

All PostgreSQL users, hackers and service providers reap the benefits of any and all improvements to the project. It’s with that in mind that we welcome Amazon to this community and look forward to their contributions and collaboration to help further the PostgreSQL project.

OAuth as Single Sign On

Today, we're announcing the release of a key part of our authentication infrastructure - id.heroku.com - under the MIT license. This is the service that accepts passwords on login and manages all things OAuth for our API. The repo is now world-readable at https://github.com/heroku/identity . Pull requests welcome.

While OAuth was originally designed to allow service providers to delegate some access on behalf of a customer to a third party, and we do use it that way too, Heroku also uses OAuth for SSO. We'd like to take this opportunity to provide a technical overview.

Read more →

Interview with Heroku's Mattt Thompson: The Incredibly True Story of Why an iOS Developer Dropped His CS Classes and Eventually Learned How to Fly

Editor's note: This is a guest post from Rikki Endsley.

In this exclusive interview, iOS developer Mattt Thompson opens up about the moment when he realized he'd become a programmer, why he dropped his computer science classes, and what he does AFK.

Mattt and a Unicorn

Had Mattt Thompson followed in his parents' footsteps, he'd be a musician now instead of a well-known iOS developer working as the Mobile Lead at Heroku. Matthew “Mattt” Thomas Thompson was born and raised in the suburbs of Pittsburgh, Pennsylvania, by parents who are both musicians, play in the symphony, and teach music. Whereas his sister took to music growing up, Mattt kept going back to his computer. He says he couldn't help it. “I'd spend hours in Photoshop and GoLive, learning all of the tricks to making websites. These were the days before CSS, when <table>,<font>, and spacer.gif were state of the art.” Back then, he pictured himself as a designer, which is what he did for the web design company he and a developer friend started while still in high school.

Read more →

Introducing Heroku Postgres 2.0

Today we're excited to announce an evolution of what it means to be a database as a service provider. Along with new features such as the ability to roll back your database to an arbitrary point in time and high availability, we now provide an entirely new level of operational expertise that's built right in. This new level of service allows you to feel at ease while taking advantage of your database in ways you never expected. All of this is rolled into new tiers which make it as easy as ever to choose what’s right for you.

We are introducing Heroku Postgres 2.0 today, the result of these improvements. Let's dig in a little further on what's available today.

Read more →

Troubleshooting Down the Logplex Rabbit Hole

Adventures of a Heroku Routing Engineer

My name is Fred and I spend most of my time on Logplex. Since joining Heroku in March 2013, I've become the main developer on that product and handle most of the maintenance and support that goes with it. In this post, I'll explain what the Heroku routing team needed to do to make Logplex more stable, decrease our workload, and keep our mornings quiet and productive.

Read more →

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