Book Image

Hands-On RESTful Web Services with TypeScript 3

By : Biharck Muniz Araújo
5 (1)
Book Image

Hands-On RESTful Web Services with TypeScript 3

5 (1)
By: Biharck Muniz Araújo

Overview of this book

In the world of web development, leveraging data is the key to developing comprehensive applications, and RESTful APIs help you to achieve this systematically. This book will guide you in designing and developing web services with the power of TypeScript 3 and Node.js. You'll design REST APIs using best practices for request handling, validation, authentication, and authorization. You'll also understand how to enhance the capabilities of your APIs with ODMs, databases, models and views, as well as asynchronous callbacks. This book will guide you in securing your environment by testing your services and initiating test automation with different testing approaches. Furthermore, you'll get to grips with developing secure, testable, and more efficient code, and be able to scale and deploy TypeScript 3 and Node.js-powered RESTful APIs on cloud platforms such as the Google Cloud Platform. Finally, the book will help you explore microservices and give you an overview of what GraphQL can allow you to do. By the end of this book, you will be able to use RESTful web services to create your APIs for mobile and web apps and other platforms.
Table of Contents (20 chapters)
Free Chapter
Section 1: Unraveling API Design
Section 2: Developing RESTful Web Services
Section 3: Enhancing RESTful Web Services
Section 4: Extending the Capabilities of RESTful Web Services

Breaking down order-api

Having introduced microservices, we are going to split our application into two microservices so that they can be deployed, changed, and scaled independently.

Basically, our application was created with a lot of principles used by microservices, such as being partially organized around business capabilities, smart endpoints, infrastructure automation, designing for failure, and so on.

The idea now is to create two applications, each one with its own database, GitHub repository, and CI/CD, and the endpoints will be exposed by Google Cloud Endpoints:

Breaking down order-api into two microservices

Each microservice will be responsible only for its responsibility, such as the order microservices doesn't need to handle login either user microservice. Since we are going to use Google Cloud Endpoints, we can let endpoints handle that for us with an API key...