BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Microservices Content on InfoQ

  • 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.

  • Lessons Learned From Scaling Services at Google and eBay

    Randy Shoup shared his experiences to the QCon London audience in scaling services at Google and eBay, giving advice on building and operating services. A successful services strategy requires end-to-end service ownership, decentralized decision-making and standardization efforts focused on protocols of communications and supporting infrastructure.

  • Phil Calcado on Lessons Learnt During SoundCloud's Microservice Migration

    At QCon London 2015 Phil Calcado shared lessons learnt from SoundCloud’s move from a monolithic to microservices architecture, and stated that the core requirements for building a microservice platform include developing capabilities for rapid provisioning, basic monitoring and rapid application deployment.

  • Microservices and the Goal of Software Development

    The goal of software is to sustainably minimize lead time to positive business impact, everything else is detail, Dan North claimed in a presentation at the QCon London conference describing ways of reasoning about code and how this leads him into an architecture style that may fit microservices.

  • Microservices and Evolutionary Architecture

    Service-Oriented Architecture (SOA) made us think about breaking up monolithic systems into individual services but also encouraged building producer driven monster services with centralised control. With microservices we are going back to the underlying notions of why SOA made sense, Rebecca Parsons claimed in a presentation at the QCon London conference.

  • 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.

  • Google Releases gRPC, a HTTP/2 RPC Framework for Microservices

    Google has opened sourced gRPC, a RPC framework used internally to connect cloud microservices. gRPC comes with support for 10 languages, making it attractive for creating back-end cloud services for mobile applications.

  • 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.

  • A Service View of Business Driven DevOps

    Over the years Steve Jones has had a lot to say about Business SOA. Recently he's turned his attention to DevOps and believes there are some important lessons that DevOps can learn from SOA and Business Architecture.

  • Bad Practices Building Microservices

    When adopting a microservices architecture, using an external architect to create the design of a service instead of helping a team make their own decisions about design and implementation is one of several traps or bad practices that Vladimir Khorikov has experienced in his work.

  • Don’t Share Code Between Microservices

    Reasons for building microservices are often about using isolation as a means to handle change. Sharing code between services couples your services to each other reducing the effectiveness of the isolation and the ability to handle change, David Dawson writes in a series of blog posts questioning the Don’t Repeat Yourself (DRY) principle in connection with microservices.

  • 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.

  • Prana: A Sidecar Application for NetflixOSS-based Services

    Netflix has released Prana, an open-source "sidecar" application the company developed to allow heterogeneous microservice applications to use the NetflixOSS JVM-based platform support libraries.

BT