Heroku Blog
- News
- Last Updated: December 15, 2015
- David Zuelke
A year and half ago, we launched support for PHP on Heroku, built from the ground up with modern features designed to give developers a more elegant and productive experience on the platform. Last week, we made PHP 7 available on top of a new, reworked version of our PHP support, and our users are adopting PHP 7’s exciting new features and stellar performance improvements quickly—we’re already seeing PHP 7 being used in the …
- News
- Last Updated: April 12, 2024
- Hunter Loftis
At the tail end of 2015, JavaScript developers have a glut of tools at our disposal. The last time we looked into this, the modern JS landscape was just emerging. Today, it's easy to get lost in our huge ecosystem, so successful teams follow guidelines to make the most of their time and keep their projects healthy.
Here are ten habits for happy Node.js hackers as we enter 2016. They're specifically for app developers, …
- Engineering
- Last Updated: November 04, 2015
- Owen Ou
If your application is successful, there may come a time where you’re on an unsupported version of a dependency. In the case of the Heroku Platform API, this dependency was a very old version of Active Record from many years ago. Due to the complexity involved in the upgrade, this core piece of infrastructure had been pegged at version 2.3.18, which was released in March 2013. We're happy to announce that we've overcome the …
- News
- Last Updated: March 29, 2024
- Matthew Creager
Most modern mobile apps depend heavily on the app’s back-end. That’s because many of the expectations users have for mobile apps today — for the application to work regardless of network connectivity, to notify them when relevant content changes, to have integrations with the social networks they use, for appropriate levels of security, and a hundred other things — are reliant on the app’s back-end services.
The most common pattern for mobile back-ends we see …
- Engineering
- Last Updated: October 21, 2015
- Fred Hebert
HTTP routing on Heroku is made up of three main logical layers:
- The state synchronization layer ensures that all nodes in the routing stack are aware of the latest changes in domains, application, and dyno locations across the platform;
- The routing layer chooses which dyno will handle an HTTP request (random or sticky), performs logging, error-reporting, and so on;
- The HTTP proxying layer handles the validation, normalization, and forwarding of requests between clients and dynos.
This last part is the one the platform team is happy to open-source today with the Vegur library.
- News
- Last Updated: July 12, 2024
- Jesper Joergensen
As the world becomes more cloud-centric, and more of our apps and business depend on its capabilities, the trust, control and management of cloud services is more important than ever. Since the first days of Heroku — and Platform-as-a-Service in general — many companies have struggled to balance the impact and success of the cloud with the control offered by traditional software and on-premise infrastructure. Too often that balance tips back towards software, with companies …
Subscribe to the full-text feed.