Apigee experts published over 50 editorials in 2018 — including dozens here in APIs and Digital Transformation — to help developers, IT architects, and business leaders understand how to maximize the value of APIs and keep pace with constant technological change.
2018 was an AMAZING year for Google Cloud’s Apigee team. It was, in fact, another “best year ever.” We’re deeply grateful to the companies who use Apigee to accelerate their businesses with APIs.
Good API design separates APIs that merely expose assets from those that help developers get things done. As I’ve written before, and as we’ll explore in this article, good design includes the style in which web API URLs are constructed.
The Soviet era left Mongolia with a legacy of manual banking processes that requires huge quantities of paperwork. This means that customers need to visit branches frequently for simple things like changing a PIN number or requesting a credit card. Since we count 2.8 million of Mongolia’s 3.3 million citizens as our customers, this could mean long lines at the bank, with an average wait time of 25 minutes for each visit. We wanted to change that.
As I work with customers around the world and across verticals, I’m struck by a common pattern: many savvy business people and technologists grasp the value of the new application programming interfaces (APIs) they’re creating for external ecosystem use cases, such as providing partners access to data or functionality, but they often see both the APIs they already have and those they build for internal use in a different light — not as software products that let developers
APIs are a key way businesses operate at the speed and scale necessary for today’s economy. We designed Apigee, Google Cloud’s full lifecycle API Management platform, to give businesses control over, and visibility into, the APIs that connect applications and data across the enterprise and across clouds. Apigee was recently recognized by Gartner as a leader in the 2018 Magic Quadrant for Full Life Cycle API Management.
Are they basically just an evolved version of service-oriented architectures (SOA)? Since a microservice must be exposed via an application programming interface (API) for an organization to scale it to new developers, does that mean managing microservices is basically the same as managing APIs? As this article will discuss, the answer to both of these questions is a clear “no” — and companies looking to get the most from their microservices need to understand why.
If your cholesterol were to become too high, would you ignore the test results? Probably not, because when it comes to healthcare, many of us recognize that a data-driven approach helps keep a person healthy. So why is it that so few business decisions — perhaps fewer than half — are made using quantitative data? Sounds like some pretty risky disregard for corporate well-being.
API (application programming interface) designers and developers generally understand the importance of adhering to design principles while implementing an interface. No one wants to design or implement a bad API! Even so, it’s sometimes tempting to look for shortcuts to reach those aggressive sprint timelines, get to the finish line, and deploy an API. These shortcuts may pose a serious risk — unsecured APIs.
