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

  • Microservices Premium

    In a recent article Martin Fowler tries to answer the question about when to consider using microservices, hoping that developers understand that there is an inherent complexity involved in making such an architectural change. Sometimes staying with a well-designed monolith may be more appropriate.

  • Avoid a Canonical Data Model

    Standardizing on common models for business objects that are exchanged within an enterprise, e.g. Customer, Order and Product together with the attributes and associations they have, might seem compelling but for Stefan Tilkov this creation of Canonical Data Models (CDMs) is a horrible idea which he strongly advices against.

  • Adrian Cockcroft: Microservices Revisited

    Recently Adrian Cockcroft gave an interview to ActiveState's John Wetherill about microservices. In it he talks about how polyglot fits into microservices and the impact on him when he head that companies such as Target and Macy's, as well as Homeland Security had adopted that architectural approach.

  • A Service is a Logical Construct Built by Microservices

    A service is a logical construct owning a business capability and made up of internal autonomous components or microservices that together fulfil the responsibilities of the service, Jeppe Cramon suggests continuing a previous series of blog posts clarifying his view on building services around business capabilities and bounded contexts.

  • Yelp Engineering: Using Services to Break Down a Monolith

    The Yelp engineering team have stated that moving to a service-oriented architecture has allowed them to scale their development process and maintain a rapid pace of software delivery as the team and codebase has grown. This has been achieved by focusing on distributed systems education, creating a set of basic service design principles and implementing a supporting infrastructure.

  • Characteristics of Microservices, Applications and Systems

    The assumption that a large system must have a single environment, often with a one-to-one mapping between a project’s scope and the system built are challenged today Stefan Tilkov explains when looking into ways to split a large system into smaller parts and comparing the characteristics of systems, applications and microservices.

  • What is so Special about Microservices? An Interview with Mark Little

    Mark Little discusses the anatomy of microservices, how they can be used, and why you may want to temper your enthusiasm to get them to production.

  • Udi Dahan on Defining Service Boundaries

    Udi Dahan, a SOA consultant, held the presentation Finding Service Boundaries – Illustrated in Healthcare at NDC London 2014, providing advice on establishing the service boundaries in a SOA or microservice architecture.

  • Immutability Changes Everything Including Microservices

    As computation and storage are cheap today, keeping immutable copies of lots of data becomes affordable, and by doing this, the coordination challenges can be reduced.

  • Microservices, Containers and Docker

    Working with a microservices architecture creating small services with a need for light-weight mechanisms, independent deployment, scalability and portability, a container technology like Docker can provide an ideal environment for deployment of these services with respect to speed, isolation management, and lifecycle.

  • State of the Art in Microservices

    Moving to Continuous Delivery and speeding things up, the rate of change have increased at the same time as the cost, size and risk of change has reduced, an DevOps and agile transformation, and a containerization that is very compelling for businesses of nowadays, Adrian Cockcroft explained in his keynote at the recent Docker conference in Amsterdam.

  • Monoliths from a Microservices Perspective

    There is a strong trend for microservice based architectures and frequent discussions comparing them to monoliths, Robert Annett explains and defines a monolith as an architectural style or a pattern using three basic viewtypes for characterization.

  • What is the Web?

    Mark Nottingham, chair of the HTTP Working Group, asks the question What is the Web? As he mentions, this simple question has some complex and perhaps unexpected answers depending upon your perspective. A common approach would be to say that it has to be rooted in the Web browser, but that has some interesting consequences, not all of which are useful for non-browser stakeholders.

  • The Future of Microservices

    Microservices are not new ideas and we will over the course of 3-5 years end up rebuilding WS-* the same way Web Services did rebuild all from CORBA unless we learn from our mistakes and improve to prevent them from being made again, Greg Young stated in a presentation at the Microservices Conference in London.

  • Microservices as a Service-Oriented Delivery Model

    Microservices are valuable, but to break things up properly creating the right boundaries we need to understand our business and its processes Jeppe Cramon stated in a presentation at the Microservices Conference in London.

BT