There are many different team topologies that can be effective for DevOps. Each topology comes with a slightly different culture, and a team topology suitable for one organisation may not be suited to another organisation, even in a similar sector. This article explores the cultural differences between team topologies for DevOps, to help you choose a suitable DevOps topology for your organisation.
More than ten years ago, software architect Kevin Perera invented a design method for architectures that was called "metadata-driven design and development". In this article, Aaron Kendall explains how to use this design method and outlines similarities as well as differences to current techniques like RESTful services or HATEOAS by implementing a metadata-driven mobile application.
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.
Following the webinar Exploring the Uncharted Territory of Microservices organized by XebiaLabs, Randy Shoup and Andrew Phillips answered a number of questions on microservices asked by participants.
In this article, authors provide an overview of current SOA technologies and incremental transition to SOA in legacy environments. They also discuss web services & enterprise application integration. 6
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 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.
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