Brings observability to the microservice architecture on Kubernetes

Microservices and containers have changed application design and deployment patterns. They’ve also brought with them some new challenges, such as service discovery, routing, failure handling, distributed tracing, circuit breaker, retry logic and visibility (monitoring) to microservices.

Kubernetes can handle multiple container-based workloads, including microservices, but when it comes to more sophisticated features like traffic management, failure handling, and resiliency, it leaves a lot to be desired. Most importantly, we want to do all this without changing the application code.

Service mesh architecture was created to handle these requirements. Istio is a service mesh created through a collaboration between IBM, Google and Lyft.

In this talk we will talk about the need of a service mesh, and what Istio brings to the table. We will also give a short demonstration of Istio in Kubernetes.

In this interactive session Shane discuss his experience working in a distributed, virtual organization which is founded on an Agile Mindset. The challenges of maintaining agility when remote, the ways the ICAgile team have consciously designed their team and organization culture and provide actionable advice based on real experience on how to maintain collaboration, teamwork and live the agile values in a remote only organization.

ICAgile is a global, virtual organisation working with partners across over 100 countries spanning almost every timezone. There is no single corporate office and the ICAgile team is spread across seven locations in three countries. We have managed to build a strong collaborative culture and a truly safe working environment focused on outcomes rather than activities, holding each other to account and being really effective and productive while having a joyful workplace.

Struggling to get software released on a daily basis? Stressed about how to apply the same techniques that make companies successful with continuous deployment? Learn from the experience of Atlassian’s Confluence development team on its journey from releasing once a week to every day. The talk begins with the team’s build and deployment process, providing insights into dealing with particularly large builds and tests and deployment complexities. Next, the speaker explores, in detail, the cultural and technical problems that prevented the team from making that transition quickly, including: slow builds, flaky tests, a lack of automation, the wrong mindset and dealing with release blockers, to name a few. The talk concludes with a discussion of the strategies the team has implemented to resolve these problems, including: reducing complexity, defining ownership, setting and monitoring time limits and establishing a “culture of green.” Learn how you, too, can make continuous delivery happen in a real, (and not so perfect!), engineering organization.

In past few years, it has become quite common for software development teams to be distributed across time-zones and comprise of multiple vendors with 50-100+ people.

Agile practices encourage in-person interactions to foster collaboration, whereas, distributed and large teams force communication into the opposite direction. Therefore, it is important to achieve agility albeit with different, or modified mechanics, that work well for distributed and large team.

In this talk I am going to share talk about ways of working effectively in distribute teams with examples from real projects and tools and techniques for achieving great results.

• How do we shift the mindset of team members from ‘my work’, ‘my job’ ‘my goals’ to ‘our work’, ‘our project’ & ‘our objectives’ ?
• Do your team members struggle to trust each other or keep blaming each other?
• Does your team always struggle to meet commitments & deadlines?
• Is the boss always the villain?
• Does adapting to frequent changing customer expectations makes your team uncomfortable?

We’ve all been part of such dysfunctional teams, or may be some of us are there even now.

Our combined experience of over 11 years at ThoughtWorks across domains, highly distributed setups & team sizes makes us believe it is possible to transform any agile team into an empowered team.

We speak about the factors that contribute to empowered teams through stories of projects that achieved the unachievable. We will help you with tweaks to your current recipe of agile team to ensure it transforms into and stays an empowered one.

This talk promises to contain real project experiences from us and people we interviewed across projects .