Rahul Sharma - Getting Started with Istio Service Mesh: Manage Microservices in Kubernetes

Any source code or other supplementary material referenced by the author in this book is available to readers on GitHub via the books product page, located at www.apress.com/978-1-4842-5457-8 . For more detailed information, please visit www.apress.com/source-code .

This book would not have been possible without the support of my family. I want to thank my parents, my loving and supportive wife Swati, and my son, Rudra. They are a constant source of encouragement and inspiration. Thanks for providing the time and for listening to my gibberish when things were not going according to plan. I would also like to thank my co-author, Avinash Singh, for his knowledge and support. Your experience and willingness has made this a successful project.

I am grateful to Nikhil Karkal for believing in me and providing this wonderful opportunity. I would also like to thank Divya Modi and her editorial team for the constant push throughout the process. It would have been difficult to finish the project without her support. I would like to thank Harish Oraon and Matthew Moodie for sharing valuable feedback. Your advice has helped me to deliver my ideas in a better manner.

Rahul Sharma

About the Authors

Rahul Sharma

is a seasoned Java developer with more than 14 years of industry experience. During his career, he has worked with companies of various sizes, from enterprises to startups, and has developed and managed microservices on the cloud (AWS/GCE/DigitalOcean) using open source software. He is an open source enthusiast and shares his experience at local meetups. He is also the co-author ofJava Unit Testing with JUnit 5(Apress, 2017).

Avinash Singh

is an IIT-Kanpur alumnus with more than ten years of experience in architecture, design, and developing scalable and distributed cloud applications. He has hands-on experience in technologies such as AWS Cloud, J2EE, ROR, MySQL, MongoDB, Spring, and Hibernate. Avinash has a strong understanding of SOA and microservices architecture, with a good handle on resource capacity planning.

About the Technical Reviewer

Harish Oraon

is an experienced professional from Bangalore, India, with almost a decade of experience developing scalable and distributed systems. He has worked with multiple technologies and stacks. Currently, he is leading the technology arm at a startup. Previously he was associated with Edureka, an ed-tech company, and played a key role in shaping the technology and infrastructure. He has also been associated with these giants: Roofandfloor by the Hindu Media, Koovs Fashion, and Sportskeeda.

Harish holds a UG degree from BIT Mesra, a premier institute in India. When he is not working, he loves to contribute to the open source community. He writes articles on Medium.com and answers questions on Stack Overflow and Google Groups. In his spare time, he loves spending time with his family.

Kubernetes originated from the Greek word , meaning governor, helmsman, or pilot. Thats what the founders Joe Beda, Brendan Burns, and Craig McLuckie had in mind. They wanted to drive a container ship leading to the creation of a container orchestration platform , which these days is becoming the de facto standard for running microservices in the cloud.

In late 2013, the declarative configuration of IaaS started to gain strength over bash scripts for cloud infrastructure . Though companies like Netflix were popularizing immutable infrastructures, that came with the cost of heavyweight virtual machine images. Docker became a savior by offering a lightweight container. It allowed a simple way to package, distribute, and deploy applications on a machine as compared to heavyweight VM images. But running Docker containers on a single machine was not a solution for scaling applications, which required deploying Docker containers across multiple machines. This created a need for an orchestrator.

Kubernetes development started by focusing on the key features of an orchestrator, such as replication of an application with load balancing and service discovery, followed by basic health checks and repair features to ensure availability. Kubernetes was also released as an open source version of Borg, a large-scale cluster manager at Google running hundreds of thousands of jobs for different applications across clusters, with each cluster having tens of thousands of machines. In the middle of 2015, Kubernetes was committed to GitHub and opened for developers to start contributing. In no time, big players like Microsoft, Red Hat, IBM, Docker, Mesosphere, CoreOS, and SaltStack joined the community and started contributing. In time, multiple modules were developed in and on Kubernetes, ensuring the basic orchestrator was intact and optimized over time.