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.
In this article Vijay Algarasan, a Principal Architect at Asurion, discusses how he and his teams have encountered microservices at various engagements and some lessons they have learned as a result. This has resulted in them building up a series of anti-patterns and some associated patterns, which Vijay believes are more widely applicable to all practitioners of microservices
This article contains an extensive interview on the microservices adoption process, the technologies used, the benefits and difficulties of implementing microservices, with representatives from Gilt, Hailo and nearForm.
Suman Pradhan has written about developing the CORE approach to helping architects and developers build sustainable solutions that match the business needs.
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.
Bulk data is usually accessed via files & FTP. As collaboration migrates to APIs, what are the requirements for data APIs? Here we describe a meta-data driven architecture for bulk data ingestion.
In this article, authors reflect on Credit Suisse's adoption of SOA principles and the organization's transition from mainframe programs to open SOA services with interface contracts and governance. 4
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.