Link Details

Link 950675 thumbnail
User 963819 avatar

By heidig
Submitted: Apr 05 2013 / 16:42

The growth of mobile and everything-as-a-service is making continuous delivery a necessity, not an option. Mobile drives continuous delivery adoption because of user expectations of frequent updates and because the app store model puts you in an uncomfortable position - and one you can't extract yourself from quickly - if you ship something that isn't working well. Behind almost every mobile app are hosted services, connecting to your existing systems and to third-party service providers. To be competitive and to take advantage of the mechanics and economics of delivering as-a-service, you want to roll out functionality quickly, experiment cheaply and gather real-time metrics about how your service is being consumed. Continuous delivery -- keeping your software in a release-ready state at all times, and rolling out new releases as often as makes sense for you -- is the way to solve these problems.
  • 1
  • 0
  • 117
  • 39

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (1)

Voters Against This Link (0)

    Apache Hadoop
    Written by: Piotr Krewski
    Featured Refcardz: Top Refcardz:
    1. Play
    2. Akka
    3. Design Patterns
    4. OO JS
    5. Cont. Delivery
    1. Play
    2. Java Performance
    3. Akka
    4. REST
    5. Java