News Stay informed about the latest enterprise technology news and product updates.

Ancestry.com's top lessons learned from continuous software development

7/8

Don't break your team's system functionality

Source:  Sergey Nivens/Fotolia

If a team breaks system functionality, it has failed to meet the objective of a Continuous Delivery model.

In an Agile environment, we want to develop and deploy code as fast as possible, but everyone must be a good citizen. This means not introducing incompatibility issues. A good way to ensure continued functionality is to invoke test suites of dependent components.

By observing these principles, teams may deploy at any time, and release features independently. Foremost, deployable code must adhere to existing customer contracts (e.g. internal/external dependents) and continue to function with older dependencies until a new feature is exposed. Likewise, code should be intelligent enough to switch to a new contract when it's exposed by a dependency.

View All Photo Stories

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchMicroservices

TheServerSide.com

SearchCloudApplications

SearchAWS

SearchBusinessAnalytics

SearchFinancialApplications

SearchHealthIT

DevOpsAgenda

Close