InfoQ Homepage Microservices Content on InfoQ

  • Netflix Play API: Building an Evolutionary Architecture

    At QCon SF, Suudhan Rangarajan presented “Netflix Play API: Why We Built an Evolutionary Architecture”. Key takeaways included: services that have a single identity/responsibility are easier to upgrade; spend time identifying core decisions that need to be made when building a service; and designing an “evolutionary architecture” using tools like fitness functions provides many benefits.

  • HashiCorp Improves Consul Service Mesh Integration with Kubernetes

    Hashicorp has released new features to better integrate Consul with Kubernetes. These features include support for installing Consul on Kubernetes using an official Helm Chart, autosycing of Kubernetes services with Consul, auto-join for external Consul agents to join a Kubernetes cluster, support for Envoy, and injectors so Pods can be secured with Connect.

  • The Human Side of Microservices

    A microservices architecture is a game changer for team communication, not a purely technical solution. If different teams don’t have stable, direct communication channels, the software they produce will suffer. The five key properties crucial for a successful microservices implementation are zero-configuration, auto-discovery, high redundancy, self-healing, and fault tolerance.

  • Building Production-Ready Applications: Michael Kehoe Shares Lessons Learned from LinkedIn

    At QCon San Francisco, Michael Kehoe presented “Building Production-Ready Applications”. Drawing on his experience with site reliability engineering (SRE), he introduced the tenets of “production-readiness” that all engineers across the organisation should focus on as: stability and reliability; scalability and performance; fault tolerance and disaster recovery; monitoring; and documentation.

  • Axon Conference Panel: Why Should We Use Microservices?

    In the panel discussion at the recent Event-Driven Microservices Conference in Amsterdam, Frans van Buul from AxonIQ, the conference organizer, started by noting that microservices are quite mainstream today. He wanted to look back at what we have learned, but also think about where we will be heading in the next couple of years.

  • NGINX Interview: Enterprise Adoption of Software Load Balancing, API Gateways, and Service Meshes

    InfoQ recently sat down with Rob Whiteley, Sidney Rabsatt, Liam Crilly from NGINX, and discussed their views on the future of networking and data center communication. NGINX aims to be a “trusted advisor” and provide an “easy on-ramp” for enterprises looking to leverage software load balancers, ingress gateways, and service meshes, as is appropriate to their current technology landscape and goals.

  • Q&A with IBM's Lin Sun on Istio 1.0 and Microservices

    InfoQ caught up with Lin Sun, a senior technical member at IBM and also a participant in the open source Istio project release team, regarding Istio in general and the 1.0 release in particular.

  • Strategies for Microservices Communication

    When moving from a monolith to a microservices architecture, complexity implicitly hidden within the monolith becomes explicitly visible and the challenges for communication will grow exponentially, Michael Plöd explained in a presentation at GeeCON 2018, describing different strategies for communicating between microservices.

  • Experiences Using Micro Frontends at IKEA

    Today, we commonly split up an enterprise architecture in smaller services, microservices. But we have the same problems with the frontend monolith as we had with the backend, Gustaf Nilsson Kotte explained in a recent interview hosted by Stefan Tilkov. Using a micro frontend architecture, he breaks the frontend into smaller parts, to allow for teams to deploy continuously and autonomously.

  • Istio v1.0 Service Mesh Released with Feature “Ready for Production Use”

    At the Google Cloud Next 2018 event, the release of Istio 1.0 service was announced. Key new features include cross-cluster mesh support, fine-grained traffic flow control, and the ability to incrementally roll out mutual TLS across a mesh.

  • QLoo Creates GraphQL Interface for Existing Services recently released QLoo , an API translation layer to provide GraphQL endpoints for existing services and serverless functions. QLoo is intended to simplify the process of adding GraphQL on top of existing software.

  • Buoyant's Conduit Service Mesh Officially Becomes Linkerd 2

    Conduit officially merged into the Linkerd project and released as Linkerd 2 (Beta). In addition to regular Linkerd 1 releases, Linkerd 2 (beta) artifacts are now being generated. Linkerd 2 code is fully open sourced and available on their GitHub repository. Conduit 0.5.0 is its last official release of the Conduit project.

  • Instana Releases Sample Microservice Application

    Instana, provider of AI powered monitoring solutions for dynamic containerised microservice applications, announced at QCon New York the release of Stan’s Robot Shop, a sample microservice application that can be used as a sandbox to test and learn about microservice architecture, containerised application orchestration and automatic monitoring techniques.

  • HashiCorp Releases Consul 1.2 with "Consul Connect" Service Mesh Solution

    HashiCorp has released Consul 1.2.1, the latest version of their highly available and distributed service discovery and key-value store, which also includes a public beta launch of the Consul Connect. Consul Connect provides service-to-service connection authorization and encryption using mutual TLS, and “automatically turns any existing Consul cluster into a service mesh solution.”

  • Microsoft Releases Azure Service Fabric Mesh as a Public Preview

    Service Fabric now has a relative in the cloud – Azure Service Fabric Mesh, a fully managed service in Azure that will enable developers to deploy and operate containerised applications. This service is now publicly in preview after its initial private preview debut during Build 2018 last May.


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:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.