Heroku Redis GA and Introducing Heroku Data Links

Today we’re pleased to announce general availability of Heroku Redis with a number of new features and a more robust developer experience. By giving developers a different data management primitive, we’re helping them meet the needs of building modern, scalable applications. The classic example of using multiple data stores in an application is the e-commerce site that stores its valuable financial information in a relational database while the user session tokens are saved in a key-value store like Redis. This is one of the use cases where Redis has proven to be instrumental in solving problems like caching, queuing and session storage, just to name a few.

In addition to making Heroku Redis generally available, we’re pleased to introduce something new: Heroku Data Links. The explosion of applications and distributed application architectures -- things like microservices and service-oriented architectures -- means that now more than ever, developers and organizations have valuable data living in disparate data stores. The truly transformative applications and organizations are the ones that can quickly pull all of the data across all of their heterogeneous data stores such as Redis and Postgres, to provide insights back to their own customers or internal users. Heroku Data Links gives developers all of the benefits of data federation across multiple data sources without the hassle of building out a new system. Information is pulled across data stores on-demand via SQL, allowing developers or anyone in the organization to draw insights quickly and easily.

Read more →

New Dynos and Pricing Are Now Generally Available

Today we are announcing that Heroku’s new dynos are generally available. This new suite of dynos gives you an expanded set of options and prices when it comes to building apps at any scale on Heroku, no matter whether you’re preparing for traffic from Black Friday shoppers or deploying your first lines of code. Thanks to everyone who participated in the beta and provided feedback and bug reports.

What does this mean for you? Beginning today, all new applications will run using these new dynos. You can migrate your existing paid applications to the new dynos at any convenient time until January 31, 2016, when we will sunset the traditional dynos. We will begin migrating free applications to the free dynos after July 15th, 2015.

Read more →

Heroku Button for Private Repos

Last year, we launched Heroku Button to make it simple for developers to deploy open source code to new Heroku apps. Open source contributors can add Heroku Buttons to GitHub READMEs, tutorials and blog posts and make their projects instantly deployable to Heroku, as apps fully provisioned with add-ons and other required configurations. Two months ago we introduced Elements where more than 1700 public Heroku Buttons are profiled alongside add-ons and top buildpacks.

Today, we're happy to announce Heroku Buttons for projects maintained by your team in private GitHub repos. This new feature uses Heroku's GitHub integration to securely deploy code referenced by buttons on private repos.

Buttons for private repos makes it simple to maintain private frameworks and quickstart template apps. Private repo buttons are great for:

  • Onboarding new developers, contractors, and agencies to complex codebases with many dependencies that requires lengthy setup. Error-prone multi-step README getting-started sections can be replaced with a Heroku button that instantly configures an app on Heroku and deploys repo contents.
  • Ensuring consistency when new projects are begun. Your team can maintain template apps for relevant languages, complete with app.json files specifying add-ons and config that comply with requirements for team projects.
  • Profiling best practices by featuring buttons that deploy software and projects you are proud of in company newsletters and docs for colleagues to experiment with and learn from.

Read on for details on how to add Heroku Buttons to private GitHub repos.

Read more →

The Next Twenty Years of Java: Where We've Been and Where We're Going

1995 was the year AOL floppy disks arrived in the mail, Netscape Navigator was born and the first public version of Java was released. Over the next two decades, Java witnessed the multi-core revolution, the birth of the cloud, and the rise of polyglot programming. It survived these upheavals by evolving with them, and it continues to evolve even as we celebrate Java's twentieth birthday this year.

Read more →

Heroku Review Apps Beta

Today we’re announcing a feature that is going to change the way teams test and evaluate code changes. Continuous delivery works best when all team members — designers and testers included — can efficiently visualize and review the result of proposed changes. With Review Apps enabled, Heroku will spin up temporary test apps for every pull request that’s opened on GitHub, complete with fresh add-ons and other config required to make the app run. Instead of relying only on code reviews and unit tests run by CI, teams can use Review Apps to immediately try out and debug code branches in a production-like environment on Heroku. Review apps speed up team decision-making so that you can deliver better apps faster, and with greater confidence.

The Review Apps feature builds on the GitHub Integration announced in February and combines two things in this world that are good and righteous:

  • Heroku apps and the ease and speed of creating them from app.json templates
  • GitHub pull requests for reviewing and discussing changes to source code

This is great if you’re using GitHub Flow to propose, discuss and merge changes to your code. Because pull request branches are deployed to new apps on Heroku, it’s quick and simple for you and your collaborators to test and debug changes proposed in the PR and decide whether it’s ready to merge, needs more work or to close it because it’s not the experience you want.

Read on below, or check the Dev Center docs for details.

Read more →

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