Book Image

TypeScript Microservices

Book Image

TypeScript Microservices

Overview of this book

In the last few years or so, microservices have achieved the rock star status and right now are one of the most tangible solutions in enterprises to make quick, effective, and scalable applications. The apparent rise of Typescript and long evolution from ES5 to ES6 has seen lots of big companies move to ES6 stack. If you want to learn how to leverage the power of microservices to build robust architecture using reactive programming and Typescript in Node.js, then this book is for you. Typescript Microservices is an end-to-end guide that shows you the implementation of microservices from scratch; right from starting the project to hardening and securing your services. We will begin with a brief introduction to microservices before learning to break your monolith applications into microservices. From here, you will learn reactive programming patterns and how to build APIs for microservices. The next set of topics will take you through the microservice architecture with TypeScript and communication between services. Further, you will learn to test and deploy your TypeScript microservices using the latest tools and implement continuous integration. Finally, you will learn to secure and harden your microservice. By the end of the book, you will be able to build production-ready, scalable, and maintainable microservices using Node.js and Typescript.
Table of Contents (17 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

What, why, and how of service registry and discovery


After looking briefly at service registry, we will understand the what, why, and how of service registry and discovery in this section. From understanding the need for service discovery, we will then understand the process and components involved in that process.

The why of service registry and discovery

Whatever container technology we go for, in production environments we will always have three four hosts and a number of containers inside each. In general, the way we distribute our services across all available hosts is totally dynamic and dependent on business capabilities, and can change at any point in time as hosts are just servers and they are not going to last forever. This is where service discovery and registry comes in. We need an external system that solves the limitations of a common web server, keeps an eye on all the services at all times, and maintains a combination of IP and port so that clients can seamlessly route to those...