Category:APIDesignPatterns:Evolution
From APIDesign
(Difference between revisions)
(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...) |
|||
| 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 [[ | + | 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 [[BackwardCompatibility|backward compatible]] 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]]: |
| + | |||
| + | |||
| + | [[Category:APIDesignPatterns]] | ||
Revision as of 12:51, 15 November 2008
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 backward compatible 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 one. The APIDesignPatterns listed in this category are well suited for Evolution:
Pages in category "APIDesignPatterns:Evolution"
There are 33 pages in this category.
ABC |
C cont.DEFGIL |
MOPRV |
Follow
