APIs are the neural connections of the digital economy, allowing systems to connect, collaborate, and converse with meaningful data. But these connections don't start with fully working APIs; they start with API design.
When I started out in this business back in 1999, my first job was with a small and thriving consultancy in Rotterdam, Holland called 'Holland Object Technology' or 'HOT Objects' for short (may it RIP). One of the first conversations I recall having at this wonderful, creative little company was with my boss - a 6'6" former Dutch army sargeant with an incredible intellect and vast experience. "What's great about this business," he said, "is that you can have an idea for a steam engine in the morning - and watch it running on the lawn in the afternoon!"
He had captured the essence of what I really enjoyed about software engineering: the rapidity with which one could be creative, the almost magical speed (when compared with classical professions like 'real' engineering) with which one could conjure things of mere thought-stuff that actually did something useful (unlike the many dead essays I had written as English undergraduate).
Guest Post by Paul Bruce from SmartBear Software
Paul Bruce, Product Marketing Manager for the Ready! API family of products at SmartBear, shares his thoughts on the new RAPID-ML Plugin for Ready! API.
We’re excited to announce a new partnership with the good folks at RepreZen! Both SmartBear and RepreZen share a deep passion for great API design. We’ve combined the power of our platforms to simplify the process of designing and testing high-quality APIs from inception to production deployment.
With great excitement and anticipation, I'm happy to announce that RepreZen has been selected to participate in Startup Bootcamp FinTech, a premier accelerator program here in New York.
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.