Category:APIDesignPatterns:Evolution

From APIDesign

(Difference between revisions)
Jump to: navigation, search
(New page: First version of an API is never perfect. All the time there is a need to evolve, extend use-cases and provider more functionality. Doing this in BackwardCompatible way ensures tha...)
Current revision (21:14, 29 September 2010) (edit) (undo)
 
(One intermediate revision not shown.)
Line 1: Line 1:
-
First version of an [[API]] is never perfect. All the time there is a need to evolve, extend use-cases and provider more functionality. Doing this in [[BackwardCompatible]] way ensures that usages of previous version of the [[API]] still remains valid and greatly reduces [[Cost of Ownership]] and turns the [[API]] into [[Good Technology|good one]]. The [[APIDesignPatterns]] listed in this category are well suited for [[Evolution]]:
+
First version of an [[API]] is never perfect. [[API]]s need to be ready for being insufficient and imagine potential direction of future changes. All the time there is a need to evolve, extend use-cases and provide more functionality.
 +
 
 +
Doing this in [[BackwardCompatibility|backward compatible]] way ensures that usages of previous version of the [[API]] remains valid in future. This greatly reduces [[cost of Ownership]] for users of such [[API]]s.
 +
 
 +
Evolution of an [[API]] requires well though plan. One needs to be ready for extending already existing pieces. Usage of proper [[APIDesignPatterns]] patterns listed at this category will make such future, unknown changes easier:
 +
 
 +
[[Category:APIDesignPatterns]]

Current revision

First version of an API is never perfect. APIs need to be ready for being insufficient and imagine potential direction of future changes. All the time there is a need to evolve, extend use-cases and provide more functionality.

Doing this in backward compatible way ensures that usages of previous version of the API remains valid in future. This greatly reduces cost of Ownership for users of such APIs.

Evolution of an API requires well though plan. One needs to be ready for extending already existing pieces. Usage of proper APIDesignPatterns patterns listed at this category will make such future, unknown changes easier:

Retrieved from "http://wiki.apidesign.org/wiki/Category:APIDesignPatterns:Evolution"
Personal tools
buy