Wednesday November 25th

3 Kicks

Economics of Continuous Deployment

CI is great, you'd think then that continuous deployment would be just as awesome. Clients automatically get access to the latest build, and you as the developer don't even have to think about it. That's what Ayende and his team thought as well, until they discovered the hidden economic issues behind this delivery model.


An annual license fee should solve the economic problem of continuous integration. This will allow developers to work on major features and bugs in the current features.

I agree, however I think another option would be to make use of release tags and provide access to tagged builds based on license. If you tag your releases and push fixes to those release branches, that will allow users to get updates without having access to the latest features in a newer version. This allows someone to pay once for their product, yet still receive timely updates without paying a subscription.

Commenting on Stories is limited for now and will open up to those recommended by the community. Learn how
Loading DotNetKicks...
brought to you by the Kicks Network