A verbal contract isn't worth the paper it's written on. | ||
| --Samuel Goldwyn | ||
How you go about designing your service interface will go a long way towards the long-term success and overall stability of your service. As we have seen in the previous chapters, a well-built service should only reveal its location, available operations, and the messages it exchanges with clients. The service's internal plumbing should remain safely tucked away from those who intend to consume the interface. We will spend the majority of this chapter looking at how to practically implement a series of key schema and endpoint patterns.
In this chapter you will learn the following topics:
Good practices for building schemas that coincide with the service type you've chosen
When and how to build canonical schemas
The benefits and limits of schema reuse
Translating data types and node characteristics into client code
Ways to use generic schemas in your solutions
Strategies for building...