BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage SOA Content on InfoQ

  • Managing Technology with CORE Strategy & Architectural C’s & P’s

    Suman Pradhan, who has worked in healthcare, financials and technology sectors, has written about developing the CORE (Consolidate, Optimize, Refresh and Enable) approach to helping architects and developers build sustainable solutions that match the business needs. In this article he discusses CORE and compares and contrasts with other software architectural techniques.

  • Randy Shoup and Andrew Phillips Answer Questions on Microservices

    Following the online webinar "Exploring the Uncharted Territory of Microservices" organized by XebiaLabs, which we covered in The Benefits of Microservices, Randy Shoup and Andrew Phillips answered a number of questions on microservices asked by participants.

  • Metadata-Driven Design: Designing a Flexible Engine for API Data Retrieval

    Bulk data is commonly accessed via files & FTP. As the world moves toward APIs to facilitate collaboration, what are the requirements for data APIs? This article describes a meta-data driven architecture for bulk data ingestion. Two APIs operate in parallel to provide data changes as well as the data records themselves. An example demonstrates how API responses are parameterized using meta-data.

  • Fifteen Years of Service-Oriented Architecture at Credit Suisse

    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.

  • Service-Oriented Architecture and Legacy Systems

    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.

  • REST-y Reader

    Rounding out our first Web APIs series Mike shares books he recommends for those who want to learn more about designing, implementing, and maintaining APIs for the Web.

  • Roy Fielding on Versioning, Hypermedia, and REST

    Roy Fielding talks to Mike Amundsen about versioning on the Web, why hypermedia is a requirement in his REST style, the process of designing network software that can adapt over time, and the challenge of thinking at the scale of decades.

  • Making the Case for an API Roadmap

    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.

  • Article Series: Web APIs: From Start to Finish

    This series takes the reader on a journey from determining the business case for APIs to a design methodology, meeting implementation challenges, and taking the long view on maintaining public APIs on the Web over time. Along the way there are interviews with influential individuals and even a suggested reading list on APIs and related topics.

  • Updated Principles of Service Orientation

    Our understanding of SOA has changed over the last 15 years including new aspects such as Service Execution Context and a re-defined notion of the Service Contract. This paper reviews and updates the Principles of Service Orientation based on the first OASIS SOA RAF standard bridging the gap between business and technology and eliminating technology-specific wording in their formulation.

  • How SOA Governance (and SOA Management) Should Actually Be Done

    Ganesh Prasad proposes separating governance and management in large SOA projects to make sure that right dependencies are used throughout the system in order to promote agility, lower operating costs and reduced operational risks.

  • Sam Newman: Practical Implications of Microservices in 14 Tips

    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? At last GeeCon 2014 in Krakow, Sam Newman tried to answer those questions by giving 14 tips about how microservices can interface, how the can be monitored, deployed, and made safer.

BT