RepreZen API Studio started with the goal of enabling deep interoperability, by unifying data representations across APIs. The core of the product was the API modeling language that became RAPID-ML. API Studio provides the tooling: the RAPID-ML editor, live documentation and diagram views, sandbox testing and code gen framework.
In Part 1, we talked about the hypermedia mosh pit that erupted when Roy Fielding leveled some blunt criticism at non-RESTful interfaces advertised under the banner of REST, and went on to list some principles of hypertext-driven API design.
There’s a great deal of interest in microservices architecture. Forward thinking tech companies have provided the thought leadership; startups and enterprise IT have taken an interest; and technology vendors, this one included, have all jumped on the bandwagon.
Today, Amazon announced the AWS API Gateway at AWS Summit in New York. Now the most important API management capabilities -- authorization, access control, traffic management, monitoring, analytics, version management and SDK generation -- are a virtual plank in the AWS platform as a service.
Reprinted from original publication on http://blog.smartbear.com
A lot has been written about the Hypermedia Constraint, a.k.a. HATEOAS. I’ll avoid the acronym because… well, because it’s a horrible acronym. I’ll follow Roy Fielding’s example and call it the Hypermedia Constraint.