API Management is a hot topic at the moment. Many have heard about it and have seen the flurry of products that have been introduced into the market in recent years. However, when speaking with our customers, it's clear to me that many do not know exactly what all the elements are that make up API Management. This can lead to a lack of understanding of the architecture and sometimes the benefits of API Management for their business. To help address this, we have created this post to help break down API Management into its constituent parts and help you see how your organisation might benefit.Continue reading
Back in the day, Web Services were the de facto standard for accessing "systems of record." Out of this grew the secured ESB architecture that is synonymous with enterprise architecture.
More and more, projects are utilising API Management in those architectures now and pushing on Web Services' door.
In this blog, I'll explain why social factors—as much as technical ones—are enabling API Management to make inroads into 'traditional' SOA architectures. I'll also show that API Management is much more than the "API Economy."
It’s hard not to notice the up-swell of API Management in the press in recent times. If you come from an EDI background you may dismiss API Management as not being relevant. I also often hear the contrary view: that EDI is old-school and that APIs are taking over.
I don’t believe either to be true.
There are plenty of Qualities of Service that EDI gives in spades that API Management simply doesn’t touch and vice-versa. In this blog I’ll review those differences and show how API and EDI are complementary technologies, not competitive ones. I'll also suggest where the future lies for these two differing technologies and that, actually, the comparison isn't EDI vs API—but should be API vs Web Services.