In this article, authors reflect on Credit Suisse's adoption of SOA principles and patterns and the organization's transition from using tightly integrated mainframe programs to open SOA services with emphasis on the importance of interface contracts and service governance.
In this article, authors provide an overview of current SOA technologies and how to evolve in legacy environments. They also discuss the topics of SOAP vs. REST web services, Enterprise Application Integration and incremental transition to SOA in legacy environments.
Roy Fielding talks to Mike Amundsen about versioning on the Web, why hypermedia is a requirement in his REST style, and the process of designing network software that can adapt over time. 14
Chris Haddad explains why one should create a roadmap for an API, providing advice on avoiding common API pitfalls, creating business value and monetizing API assets. 1
This series takes the reader on a journey from determining the business case for APIs to a design methodology, meeting implementation challenges and maintaining public APIs on the Web over time.
Our understanding of SOA has changed over the last 15 years. We review and update the Principles of Service Orientation providing a more business-focused & less technology-specific perspective. 6
Ganesh Prasad proposes separating governance and management in SOA projects to make sure that right dependencies are used throughout the system in order to promote agility and reduce costs and risks.
What are the practical concerns associated with running microservice systems? And what you need to know to embrace the power of smaller services without making things too hard? 2
Many Web API designers claim their are RESTful, but their APIs have little in common with REST. What can be done to make a web service API truly RESTful? 8
Ganesh Prasad proposes minimizing service dependencies in a SOA implementation rather than avoiding point-to-point connections in order to obtain a more flexible system that can evolve over time. 1
Enterprise Application Development can be smartly standardized in order to take advantage of existing code and component based architecture. Mark demonstrates an approach to clarify this EA pattern. 6