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 on Analyzing Response Time Distributions for Microservices

    At the microXchg conference, held in Berlin, Adrian Cockcroft presented “Analyzing Response Time Distributions for Microservices”. Cockcroft demonstrated how the combination of his Spigo microservice architecture simulation tool and the online Guesstimate Monte Carlo method tool can be used to visualise and experimentally simulate request response times within a complicated microservice system.

  • "Wait, What!? Our Microservices Have Actual Human Users?" The Importance of UI Architecture

    At the microXchg conference, Stefan Tilkov presented “Wait, what? Our microservices have actual human users?”. Tilkov proposed that current microservice discussions tend to be centered around backend topics. The presentation argued that it is of paramount importance to increase focus on how to structure what is arguably the most important part of a microservice application - the UI.

  • Microxchg Conference Day 1 Recap

    Today was the first day of the Microxchg 2016 conference in Berlin, Germany. More than 250 people from all around Europe gathered to learn and discuss about microservices, where and how to be used and their future. in this article, we examing what were the key takeaways from the first day of the conference.

  • AutoScout24’s Journey to Microservices: Christian Deger on Transformation, Principles and Technology

    At the Dublin Microservices User Group, Christian Deger presented “Highway to Heaven”, the AutoScout24 journey from deploying code into a monolithic application using a traditional IT development process, to utilising a microservice architecture with cross-functional teams. This technical and organisation transformation enabled the business to react more rapidly to changing market conditions.

  • Introducing ‘Gizmo’, a Golang-based Microservices Toolkit from The New York Times Development Team

    The New York Times development team have released ‘Gizmo’, an open source Golang-based microservices toolkit, which provides standardised configuration and logging, health check and metric endpoints with configurable strategies, and basic interfaces to define service expectations and vocabulary.

  • Microservices and Teams at Amazon

    The microservices pattern are changing how we build applications and team structure is extremely important to be successful in building and running these microservices, Chris Munns stated in a talk about how microservices at enterprise scale are built at Amazon at the earlier I Love APIs 2015 conference.

  • Using Microservices in the Internet of Things

    In this interview Fred George explains how the internet of things can exploit microservices and the challenges that the Internet of Things is posing and how to deal with them. InfoQ also asked him for advice for the software industry regarding the usage of microservices for the Internet of Things.

  • Defining, Reviewing and Implementing Service APIs with “goa”, a Go-based Microservice Framework

    Raphael Simon, senior systems architect at RightScale, has created “goa”, a Go-based HTTP microservice framework that allows the definition of a service API via a Domain-Specific Language (DSL) and the automated code generation of the corresponding “boilerplate” server and client code. InfoQ sat down with Simon and asked questions about the goa microservice framework.

  • Support for Microservices

    Fred George talked about what organizations can do to successfully deploy microservices at the GOTO Berlin 2015 conference. InfoQ interviewed him about business and IT interaction for microservices, what organizations can do to support teams in using microservices, benefits of microservices and what the future will bring for microservices.

  • Microservices at Spotify

    Kevin Goldsmith talked about how Spotify uses microservices to break down architectures and be innovative at the GOTO Berlin 2015 conference. He argues that Microservices are easier to test, deploy and monitor than monolithic applications. Spotify also aims to have as few as possible dependencies in their product, and microservices are very helpful for that.

  • Developing and Testing Microservices

    At the Agile Testing Days 2015 Jose Lima from Redgate software shared his experiences with microservices. InfoQ interviewed him about advantages and disadvantages of developing products with microservices, how applying microservices has improved the quality of products, testing microservices and the skills that testers need, and his learnings from developing and testing microservices.

  • Moving from a Monolithic to a Microservices Architecture

    Moving from a monolith to microservices the only value business stakeholders care about is reducing cost. It will not increase or protect revenue and neither scaling nor distribution are good reasons that will convince the business, Ian Cooper claimed in his presentation at this year’s Microservices Conference in London describing guidelines moving from a monolith to a microservices architecture.

  • SOA versus Microservices?

    Microservices and SOA are often compared and contrasted, with some people suggesting they are unrelated whereas others believe they are close relatives. In a recent article Matt Braiser joins the debate on the side of the latter group and gives his reasons for believing that microservices owe their existence to the success of SOA principles.

  • The Role of Configuration Management in a Containerized World

    The widespread adoption of Docker in infrastructure automation has led to a growing debate as to whether it supersedes configuration management. The consensus seems to be that both will co-exist in a complementary way.

  • Microservices and Integration from an Enterprise Perspective

    Common misconceptions in large enterprises that Kim Clark meets are that microservices are fine grained WSDL operations or that APIs are microservices. A reason for this is that they are confusing interface granularity with component granularity, Clark claimed in a presentation at this year’s Microservices Conference in London.

BT