Baratine is an asynchronous facade that can be placed in front of an existing library without modifying its code base, thus exposing the library as a microservice available to any language, and simplifying the requirement to have a nonblocking scalable web service. This article shows how Baratine’s POJO platform takes an API-centric approach to building high performance microservices.
Healthy organizations exhibit similar patterns of behavior, organization and improvement efforts. In this series we explore some of those patterns through testimonies from their practitioners and through analysis by consultants in the field who have been exposed to multiple DevOps adoption initiatives.
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.
In this article, Aaron Kendall uses the "metadata-driven design and development" approach by Kevin Perera to show how to rapidly create a mobile application that can evolve during runtime.
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.
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