service mesh

Showing 7 out of 7 results


Expert Talk: gRPC, Kubernetes & .NET

Join Mark Rendle, MS Dev Tech MVP, and Matt Turner, DevOps leader, architect, and engineer at Marshall Wace, in a passionate discussion about gRPC’s past and future and how it fits in with technologies such as .NET and service meshes. They get deep in the weeds on technology cycles while debating the future of infrastructure as a code and Kubernetes. And Mark has a brilliant idea on how to build an alternative to Facebook.

May 17, 2022

Software Technologies that Stand the Test of Time

What software technologies have stood the test of time or have had a massive influence over existing systems? Which do you love or hate? We asked these questions to the GOTO Book Club authors and interviewers that made up the lineup for the second season. Find out what Nicki Watt, CTO/CEO at OpenCredo, Eberhard Wolff, fellow at innoQ, Venkat Subramaniam, founder of Agile Developer, Inc., Liz Rice, chief open source officer at Isovalent, Rebecca Nugent, professor in statistics & data science, Phil Winder, CEO of Winder Research, Hanna Prinz, DevOps & software engineer and Eoin Woods, CTO at Endava, had to say. The conversation was moderated by Rebecca Parsons, CTO at ThoughtWorks.

May 6, 2021

Getting Started with Service Mesh

Hanna Prinz, a consultant at InnoQ, and Eberhard Wolff, fellow at InnoQ, the authors of Service Mesh Primer explain what a service mesh is and more importantly when and if you should use it. They also delve into the main features and reasons for deciding to use one.

November 20, 2020

The Best of GOTO Book Club Part Two

Did you know that your job is probably one of the best out there? You have the opportunity to make change happen in the world. Keep on learning and be considerate of your impact on society as a whole by: Handling security issues wit OAuth 2 Know the 97 Things Every [Java] Programmer Should Know Discover the power of Graph Databases Understand the power of Service Meshes Discover why developers “Love Kotlin” See what you can use “reinforcement learning” for.

December 16, 2021

The Future is Istio

Istio is a powerful service mesh, but what does that mean. We will take a deep dive into the Istio feature set and explore what it means to the future of not only Kubernetes but the cloud itself, and how it will be redefining how our systems interact.


Making Microservices Micro with Istio and Kubernetes

Microservices are here to stay. When applied properly, microservices techniques and culture ultimately help us continuously improve business at a faster pace than traditional architecture. However, microservices architecture itself can be complex to configure. All of a sudden, we are faced with the need for a service discovery server, how do we store service metadata, make decisions on whether to use client side load balancing or server side load balancing, deal with network resiliency, think how do we enforce service policies and audit, trace nested services calls…. The list goes on. Sure, it’s easy to have a single stack that makes everything work provided there are good microservices support - but what if you have a polyglot environment? How would you make sure all of the stack can address the same concerns in a consistent way? This is where a service mesh comes in. In this talk, Ray will introduce Istio, an open source service mesh framework created by Google, IBM, and Lyft. We’ll see how the service mesh work, the technology behind it, and how it addresses aforementioned concerns.


The World after Microservice Migration with Service Mesh and Contract Testing

Refactoring complex legacy monoliths into microservices is on the agenda of many tech companies of today. Once the migration is over, however, one quickly learns that the complexity simply spills over from the "dev" to the "ops" side. Many new infrastructural questions arise. For example, how do we maintain stability in a dynamic ecosystem of microservices? How do we recover from communication failures or identify performance bottlenecks in call graphs? During the refactoring, it's important for legacy clients that the APIs behave in exactly the same way as before, even exhibiting the same quirks and "features". Later, and especially with continuous deployment practices in place, developers have to be confident that changes in a microservice do not break its consumers. In the first part of the talk we will discuss the concept of a service mesh, a dedicated infrastructure layer for tackling the inter-service communication. We will analyze existing solutions, such as linkerd and Istio, and cover practical aspects of installing a service mesh on both AWS ECS (with the help of Consul) and Kubernetes. In the second part we will discuss consumer-driven contract testing. We will go through the process of creating contracts for existing systems but also see how to build new services by starting from a contract definition. And since defining the contracts isn't enough, we will show a way of integrating them in build pipelines. **Prerequisite attendee experience level:** beginner