GeistHaus
log in · sign up

Intro To RAML 1.0 | sap1ens.com

sap1ens.com

Pretty much every web developer has built HTTP APIs. How does it usually happen? If you have good practices established in your team you probably start with a whiteboarding session. Good one-hour exercise with your colleagues produces something that we call “API spec”. It might look like this: Great job everyone! Although, we forgot a few “minor” things: Error messages and error HTTP codes Authorization and authentication Schema for the entities Versioning … >_< And the most important, does it actually satisfy consumers (like front-end apps or other systems)? Multiply that by number of years you’re going to maintain that (∞) and the rate of adding new features… Looks really depressing. Our beautifully designed “API spec” quickly becomes a pile of unmaintainable mess. Is there a better way to do it?

0 pages link to this URL

No pages have linked to this URL yet.