The API (R)Evolution

A short API retrospective, from SOA to digital transformation and beyond

APIs have and continue to be the de facto standard for building and connecting modern applications. In the simplest terms, APIs let software talk to other software—which means they put more developers to work developing more applications in less time.

Though enterprises have used APIs for years, there’s been a shift in the way these interfaces are viewed within organizations. Many competitive, forward-looking businesses now think about APIs not just as an integration technology to connect apps and data but as software products that empower developers to unlock new digital business models and opportunities.

Indeed, the adoption, design, and management of APIs is increasingly driven not by IT middleware requirements but by strategic business goals relevant to all leaders in the organization.

Continue reading this post on Medium.

State of Microservices: Are You Prepared to Adopt?

Webcast replay

The allure of microservices is clear: shorter development time, continuous delivery, agility, and scalability are characteristics that all IT teams can appreciate. But microservices can increase complexity and require new infrastructure—in other words, they can lead teams into uncharted territory.

Join Gartner’s Anne Thomas and Google Cloud’s Ed Anuff as they present an in-depth look at the state of microservices.

They discuss:

  • what a microservice is and what it isn’t
  • trends in microservices architecture
  • the relationship between microservices, APIs, and SOA architecture
  • connecting, securing, managing, and monitoring microservices

Watch the webcast replay now.

To learn more, read the Apigee eBook, "Maximizing Microservices."  

Is Microservices SOA Done Right?

Webcast replay

How does microservices differ from the service oriented architecture we saw a decade ago? Find out in this webcast replay, in which Pivotal's Matt Stine and Apigee's Alan Ho discuss:

  • real-world examples of microservices best practices
  • microservices anti-patterns and traps
  • recommended tools and technology to help with microservices implementations


Modernize SOA with APIs

Webcast replay

Service-oriented architectures were not built to handle the demands of a modern, digital organization. In this webcast replay, you'll learn how one large enterprise modernized its distributed SOA by deploying Apigee Edge Public Cloud. The existing infrastructure manages SOAP, XML-based services, and some REST APIs built on an IBM integration stack (including WebSphere and DataPower).

Consultant Robert Broeckelmann Jr. joins Apigee's Dino Chiesa to discuss lessons learned from deploying an API management solution in a large enterprise, including:
  • the architectural justifications
  • requirements and use cases
  • best practices for modernizing your SOA architecture



How the API Tier Trumps Monolithic Web Architecture

The evolution to today's unified app interaction channel

Previously in this video series, we discussed the differences between APIs and SOA, and how SOA simply wasn't designed for horizontal scale. 

In our latest fireside chat, I sat down with my colleague Brian Pagano to discuss how we progressed from a monolithic web architecture to today's unified app interaction channel architecture.

Each step in the evolution is not simply a bolt-on to a previous architecture; a modern API architecture requires thinking "outside in," and it requires consideration of the needs of people beyond certain trust boundaries. An API tier requires a completely different way of thinking about exposure and consumption.


For more on the evolution of the modern API architecture and the difference between APIs and SOA, download the free eBooks, "APIs are Different than Integration" and "Beyond ESB Architecture with APIs."


Scaling to a Quarter-Million Requests per Second

Two-speed IT and the importance of an outside-in approach

In the previous video in this series, we discussed the differences between APIs and SOA, and the importance of choosing the right tool for the right job.

In our latest fireside chat, I sat down with my colleague Brian Pagano to continue our discussion on how SOA simply wasn’t designed for horizontal scale—the kind that’s required to handle the hundreds of thousands of requests per second that modern mobile apps can generate.

For more details on two-speed IT, download the free eBook, "Two-Speed IT with APIs."

The "A" in SOA Doesn't Stand for "App"

The impedance mismatch between delivering modern apps and SOA

Most readers probably know that the “A” in API stands for “application” and that the “S” in SOA stands for “services.”

So what does that mean to you when contemplating whether to adopt an API-based strategy or a services oriented architecture (SOA) strategy?

Apigee’s Ed Anuff and Brian Pagano, two self-described “old SOA guys,” recently sat down together to discuss the differences between APIs and SOA, and the importance of choosing the right tool for the right job.



For more details on the impedance mismatch between delivering modern apps and SOA, download the free eBook, "Beyond ESB Architecture with APIs."