Published July 17, 2015

Enterprise Makeover Part 4/6: cloud-native development on Heroku

In the fourth part of the Enterprise Makeover series I explain why we decided to use Heroku to run our production services.

4th episode’s highlights::

  • do probability/impact risk analysis of your service portfolio to decide what solution may work for you
  • developers should be able to easily create new environments on demand 
  • consider automating your PaaS setup even if it requires one or two clicks in the admin interface

About the series

Microservices, the Web, cloud, and Continuous Delivery heavily influenced how modern teams build software systems. In this series you’ll learn how we used those concepts to rebuild the frontend stack of several Norwegian newspapers.

The series is composed of 6 episodes describing Enterprise Makeover journey and shows how we significantly reduced cycle time and created fun work environment that let’s great developers be great. We will present all videos over the next 3 weeks. If you would like to see the slides of the full presentation go here.

Read all the articles about Enterprise Makeover

Enterprise Makeover Part 1/6: creating lean enterprise
Enterprise Makeover Part 2/6: use the Web, don’t abuse it!
Enterprise Makeover Part 3/6: rethinking Agile practices
Enterprise Makeover Part 4/6: cloud-native development on Heroku
Enterprise Makeover Part 5/6: Continuous Delivery orchestration
Enterprise Makeover Part 6/6: organizational change and summary

 

Published July 17, 2015