BT

InfoQ Homepage Microservices Content on InfoQ

  • Protocols are Important: Martin Thompson at QCon London

    The protocols we use should be studied and practiced more, they are really important in many aspects, Martin Thompson claimed in his presentation at QCon London 2019, where he first looked back at the evolution of mankind and argued that protocols is the most significant human discovery, and then did a critical analysis of the protocols and ideas we use today.

  • A Description of RSocket and Its Communication Model: Robert Roeser at QCon London

    RSocket is an asynchronous network communication protocol where communication is modelled as multiplexed streams of messages over a single network connection. In a presentation at QCon London 2019, Robert Roeser explained the reasons for creating RSocket and the communication model it uses. In the same presentation, Ondrej Lehecka described two use cases, and Andy Shi ran a demo using RSocket.

  • Helidon V1 Brings API Stability and MicroProfile 1.2 Support

    Oracle has released version 1.0 of Project Helidon, an open-source collection of Java libraries to build microservices, with greater API stability than beta versions and support for the MicroProfile 1.2 spec. Helidon comes in two programming models: Helidon SE and Helidon MP.

  • A Critical Look at Event-Driven Systems: Bernd Rücker at QCon London

    There is currently a hype in adoption of event-driven systems. Sometimes they are almost seen as the “magic thing” in our strive for decoupled systems, Bernd Rücker noted at the recent QCon London 2019. In his presentation he took a critical look at three common hypotheses around event-driven systems: events decrease coupling, Orchestration needs to be avoided, and Workflow engines are painful.

  • Recommendations When Starting with Microservices: Ben Sigelman at QCon London

    During the years Ben Sigelman worked at Google, they were creating what we today call a microservices architecture. Some mistakes were made during this adoption, which he believes are being repeated today by the rest of the industry. In his presentation at QCon London 2019, Sigelman described his recommendations to avoid making these mistakes when starting with microservices.

  • Building Services at Scale at Airbnb: QCon London Q&A

    The re-architecture to SOA at Airbnb improved the performance of the services and site reliability. Faster build and deploy times led to increased developer productivity, and improving clarity and boundaries for ownership increased efficiency. Jessica Tai, a software engineer at Airbnb, presented Airbnb’s Great Migration: Building Services at Scale at QCon London 2019.

  • The Importance of Event-First Thinking

    For global businesses to meet today’s architectural challenges with constant change and extreme scale, we need to go back to the basic principles of system design. The common element in the problems we face is the notion of events driving both actions and reactions, Neil Avery writes in a series of blog posts describing why events are so important and the advantages of an event-first approach .

  • Airbnb's Migration from Monolith to Services

    Jessica Tai spoke at QCon San Francisco 2018 about Airbnb's move from a Ruby on Rails monolith architecture to a service-oriented architecture. The company has expanded from 200 engineers in 2015 to 1,000 and has less downtime due to rollbacks and has improved performance with page load times up to 10x faster.

  • Debugging Microservices Running in Containers: Tooling Review at KubeCon NA

    At KubeCon NA held in Seattle in December 2018, several tools for debugging containerised microservices were presented throughout the conference sessions and the sponsored booths demonstrations. A notable separation appears to be occurring within the market, between "active" and "passive" debugging tools. Two examples within these categories are Rookout and Squash, respectively.

  • Using Contract Testing for Applications with Microservices

    When using microservices, integration points between services are a hotbed for bugs. With consumer-driven contract testing, the consumer defines the contract and verifications are made against it within the providers build/test lifecycle. Contract testing fits well into a microservice workflow and kills your integration bugs, argued Maarten Groeneweg at the European Testing Conference 2019.

  • Testing Complex Distributed Systems at FT.com: Sarah Wells Shares Lessons Learned

    The complexity in complex distributed systems isn’t in the code, it’s between the services or functions. Testing implies balancing finding problems versus delivering value, said Sarah Wells at the European Testing Conference. Testers often have the best understanding of what the system does; they have a good hypothesis about what went wrong, and are able to validate it pretty quickly.

  • Experiences Moving from Microservices to Workflows at Jet.com

    The Order Management System (OMS) at Jet was originally developed using a collection of microservices orchestrating tasks. As the company grew, the challenges with this architecture also grew until they decided to build a new workflow-based platform. In a blog post, James Novino at Jet describes the challenges with their old system and an overview of the new platform.

  • O’Reilly Publishes “The State of Microservices Maturity” Report

    Microservices are evolving from fad to trend, according to “The State of Microservices Maturity” survey, published by O’Reilly. The report showed an overall positive attitude towards microservices among practitioners surveyed. One significant finding is that DevOps and microservices feed off each other, so that the success of one contributes heavily to the success of the other.

  • Adopting Envoy as a Service-to-Service Proxy at Reddit

    Reddit introduced Envoy into their backend framework as service-to-service proxy to support their ongoing architectural improvements. By adopting Envoy as a service-to-service Layer 4/Layer 7 proxy, they discovered significant improvements in observability, ease of adoption, and performance.

  • An Incremental Architecture Approach to Building Systems

    Of most of the applications we have globally, maybe 90% of them are perfectly served by a monolithic approach. To avoid overengineering, we should start with a simple architecture and evolve it as needs arise, Randy Shoup recently declared in a presentation where he described his experience with companies that started small and then grew into large global internet companies.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.