Is RAML the Ideal API Description Language for the Enterprise?

API modeling languages and documentation styles have been in flux for years. The RESTful approach’s recent triumph over SOAP was supplemented by the Swagger documentation, making implementation procedures human readable. REST, now estimated to be used by 90% of new APIs, is great for lean startups that can engineer their API for quick innovation with evolving trends. However, REST doesn’t fully meet the needs for enterprise business. With their large sizes, internal politics, and sheer vast consumer base, enterprise businesses require an API with a blueprint top-down model and simplified management style, appended by quicker design speed using inheritance across potentially hundreds of APIs. Supported by SOA Software, RAML is an API description language that meets these needs. It has been suggested that RAML may be the perfect solution for designing the next generation of enterprise level APIs.


Original Article


Bill Doerrfeld I am a consultant that specializes in API economy research & content creation for developer-centric programs. I study Application Programming Interfaces (APIs) and related tech and develop content [eBooks, blogs, whitepapers, graphic design] paired with high-impact publishing strategies. I live and work in Seattle, and spend most of my time as Editor in Chief for Nordic APIs, a blog and knowledge center for API providers. For a time I was a Directory Manager & Associate Editor at ProgrammableWeb, and still add new APIs to the directory every now and then. Let's connect on Twitter at @DoerrfeldBill, or follow me on LinkedIn.