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

  • Flocker v1.0 Provides Docker Volume Migration and Storage Abstraction

    At the London Microservice User Group July meetup, Kai Davenport presented a live demonstration of ClusterHQ’s Flocker v1.0 container data volume manager tool migrating a Docker storage volume between multiple containers running within a Docker Swarm.

  • Challenges When Implementing Microservices and Why Programming Style Matters

    Fred George talked about the Challenges in Implementing MicroServices and The Secret Assumption of Agile at the GOTO Amsterdam 2015 conference. InfoQ interviewed him about how make microservices as small as possible, challenges when implementing microservices and how to deal with them, why programming style matters, and what developers can do to develop their code writing skills.

  • DDD, Events and Microservices

    To make microservices awesome Domain-Driven Design (DDD) is needed, the same mistakes made 5-10 years ago and solved by DDD are made again in the context of microservices, David Dawson claimed in his presentation at this year’s DDD Exchange conference in London.

  • Scaling the Stack Overflow Monolithic App by Obsessing Over Performance

    At QCon New York 2015, David Fullerton presented a deep-dive into the monolithic C# / MS SQL architecture that powers the Stack Overflow website, which handles over 4 billion requests per month. Fullerton argued that by focusing on performance, scalability was included ‘almost for free’; and that by minimising the number of external application services, the need to pay ‘SOA tax’ has been avoided.

  • Monitoring Microservices and Containers: A Challenge by Adrian Cockcroft

    At GlueCon 2015, Adrian Cockcroft presented a list of rules for monitoring microservice and container-based applications. In addition to these guidelines, Cockcroft also highlighted a series of challenges for monitoring cloud-native container-based systems, and introduced his ‘Spigo/simianviz’ microservice simulation and visualisation tool.

  • RedHat Microservices Architecture Developer Day London

    Last week, RedHat hosted a "Microservices Architecture Developer Day" in London, and presented a set of technologies and patterns that can be used to create microservice-based applications using open-source solutions like Kubernetes, Docker, Fabric8 and Maven. Read on for more details about the day, including links to the presentations and demo videos.

  • Eric Evans on DDD, Microservices and Boundaries

    There is tremendous value in microservices, probably giving us the best environment we have ever had for doing Domain-Driven Design (DDD), Eric Evans stated in his keynote at this year’s DDD Exchange conference in London. Iteration is the most important key to good design and microservices is the second attempt, after SOA, to get things right.

  • Building 'Failure as a Service' at Netflix without the Simian Army

    At QCon New York 2015, Kolton Andrus discussed Netflix’s Failure Injection Testing (FIT) platform, which allows the injection and monitoring of arbitrary failure scenarios to a targeted group of customers using the Netflix production web services. FIT allows Netflix to maintain an ‘antifragile’ programming culture, which results in the creation of systems that are resilient to failure.

  • Taming Dependency Hell within Microservices with Michael Bryzek

    Michael Bryzek, co-founder and ex-CTO at Gilt, discussed at QCon New York how ‘dependency hell’ could impact the delivery and maintenance of microservice platforms. Bryzek suggested that dependency hell may be mitigated by making API design ‘first class’, ensuring backward and forward compatibility, providing accurate documentation, and automatically generating client libraries.

  • Twenty Minutes to Production with Zero Downtime using Docker

    At QCon New York 2015, Paul Payne discussed a project at Nordstrom that required modifying and re-deploying a live application service within twenty minutes, which was made possible due to the use of Go-based microservices, Docker container technology, and a continuous delivery methodology.

  • Stefan Tilkov: Skip the Monolith, Start with Microservices

    During the last months Martin Fowler among others have claimed that a microservices architecture should always start with a monolith, but Stefan Tilkov is convinced this is wrong, building a well-structured monolith with cleanly separated modules that later may be pulled apart into microservices is extremely hard, if not impossible in most cases.

  • Capgemini Apollo: An Open Source Microservice and Big Data Platform

    Capgemini are currently working on Apollo, an open source application platform built on top of the Apache Mesos cluster manager and Docker, which is designed to power next generation web services, microservices and big data platforms running at scale.

  • Q&A on New Relic Software Analytics Improvement

    New Relic has released a set of new features to its Software Analytics Platform. Service Maps is a real time visual map focused on services. Together with a tool for Docker monitoring, a database dashboard for NoSQL databases and an unified alerts platform, the company wants to reduce complexity in modern software architecture.

  • Q&A with Project Lead for Microservices-infrastructure at Cisco

    Cisco is currently working on an open source ‘microservice-infrastructure’ project, which will support the continuous deployment of microservice-based applications, and is built upon technologies such as Mesos, Consul and Docker. Development is occurring primarily in the open, via the CiscoCloud Github account.

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

BT