If you’re reading this post, chances are that you’ve heard the terms “API” and “microservice” being thrown around increasingly over the last few years. They’re both incredibly important in modern day web applications, and considering how they’re used, it’s almost as if the two terms are interchangeable — although that’s not quite the case. Read more
Serverless, GraphQL, Go, microservices… disruptive tech offers great benefits, but is “boring” tech better from a pragmatic viewpoint?
If it ain’t broke, don’t fix it. No need to reinvent the wheel. The KISS (Keep It Simple, Stupid!) principle. There are plenty of expressions and the like out there that advocate embracing the tried and tested over the complex and newfangled, but sometimes the siren song of cutting-edge technology is just too much to resist. Read more
There are hundreds of pre-built solutions for everything API, whether it’s authorization, documentation, or some other functionality. While there’s a wide range of choices for your API gateway solutions — especially in recent years — the very best ones can cost quite a chunk and aren’t always tailored to your needs. Read more
The Internet runs on complexity – the sum total of internet communication is really a multitude of communications between disparate APIs, each transforming the data in a unique way. No single API can do everything, and frankly, no one API should ever even try to. Read more
If you’d spent the last five years collaborating on over 100 enterprise API projects, what do you think the biggest takeaways might have been?
At our 2018 Platform Summit, we had Frederic Pozzi, Vice President of Digital Sales at Axway answer this question — except there was no hypothetical element since he has spent the last five years working on over 100 enterprise API projects. Read more
