Understanding API
- Posted by Frank on January 10th, 2010 filed in Basic Information
- Comment now »
Before buckling down to work and trying to write APIs, it is important to analyze a bit the meaning of the word interface which can be very broad. In terms of API, interface means that the API resides between at least two different subjects. This means that there are always at least two sides using it. The two groups are always separated, either compiling the program separately or developed in completely different groups without interaction and not necessarily with the same goals and needs.
This separation is what exactly implies the rules for designing and maintaining an API. If the product was developed by a tight team, building it at once, there would be no need to interface since it is definitely going to work. In the practical world, things are not done this way. Products are produced from completely independent projects and developed by different teams not necessarily aware of the other’s existence. Projects are built independently but the need to communicate is still there. Hence the need for a stable link that can be used for such communication.