An interesting trend is emerging in the world of Web APIs, with various engineers and companies advocating for dedicated APIs for each consumer with particular needs. Beyond any ideal design of your API, reality strikes back with the concrete and differing concerns of varied API consumers. You might need to optimize your API accordingly.
MyHeritage is a rapidly-growing destination used around the world to discover, preserve and share family histories. There is increasing demand for our services, accessed both internally and externally by our partners via the FamilyGraph API. Millions of API calls are made every day providing a huge challenge in terms of performance, scalability and security.
More than ten years ago, software architect Kevin Perera invented a design method for architectures that was called "metadata-driven design and development". In this article, Aaron Kendall explains how to use this design method and outlines similarities as well as differences to current techniques like RESTful services or HATEOAS by implementing a metadata-driven mobile application.
In this article, Mark Foster — one of the editors of the ALPS specification — explains what semantic profiles are and how they can transform the way Web APIs are desgined and implemented.
Erik Wilde talks to Mike Amundsen about Profiles, Description, Documentation, Discovery, his Sedola project and the future of Web-level metadata for APIs.
In the fast growing world of APIs and microservices, finding just the right API when you are developing a web, or mobile application, is always a tedious task.
Suman Pradhan has written about developing the CORE approach to helping architects and developers build sustainable solutions that match the business needs.
After a flurry of activity from thier open working group Swagger 2.0 was officially released in September 2014. Since then responsibliity for leading Swagger would be handed over to SmartBear.
RAML, or the RESTful API Modeling Language, is a relatively new spec based on the YAML format- making it easily read by both humans and machines. 2
This series focuses on three key areas of "meta-language" for Web APIs: API Description, API Discovery, and API Profiles.
Designing a good API is hard work and it’s easy to feel overwhelmed when it’s your job to make one. 1
While the process of implementing Web APIs has become common, the tooling for describing, discovering, and understanding the meaning of the tens of thousands of API-based services has yet to settle. 1