Software engineering and development are changing because IT architecture and landscapes are changing. It used to be the case that organizations were building systems, and the main focus was on integration and how to maintain and evolve those systems. Microservices and other trends show us that this picture is changing: Now it is more about self-contained and independently deployable components which are part of an ecosystem of communicating components. The "glue" in this ecosystem are APIs, which are the only way how these components communicate. How does this shift in architecture affect software design and development? In this presentation we specifically look at how APIs affect both how components provide services, and how they consume them. The goal of this presentation is to allow software developers to better understand how APIs are an essential part of this rather fundamental shift in IT architecture.
Check the slidesErik is part of Axway's Catalyst team. The Catalyst team's mission is to help Axway customers do the right thing, and to do the thing right. We are helping organizations with their API strategy, their API programs, and their API platforms. In today's quickly evolving hybrid environments, having a well-designed platforms can turn IT into a differentiator that allows your organization to change whenever necessary.
