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


In this chapter, we learned about the OpenAPI Specification and how OpenAPI allows developers to describe their entire API, including the available endpoints and operations that can be performed on each endpoint, operation parameters such as input and output for each operation, authentication methods, contact information, licenses, terms of use, and so on.

We also learned about the concept of API-first design, which states that we should start with the design rather than writing the code first. We then learned about the creation resource-centric API, along with its appropriate HTTP requests. This allows you to expose only what you need, prevents you from including unnecessary resources and data, and makes you be conservative in regard to what you send and what you receive.

Finally, we learned about Swagger tooling with a real-life scenario, which will be implemented throughout...