ASP.NET Core 2：现代API设计构建跨平台后端系统全彩指南 - CSDN文库

需积分: 9 72 浏览量更新于2024-07-18 收藏 4.88MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

资源详情

资源推荐

1

© Fanie Reynders 2018

F. Reynders, Modern API Design with ASP.NET Core 2, https://doi.org/10.1007/978-1-4842-3519-5_1

CHAPTER 1

API Design Demystified

The times have changed—we commute with Uber, overnight with Airbnb, pay with

cryptocurrencies, and have breaking news at our fingertips via social media. We snap,

chat, and share our lives in real-time—and these kinds of apps make it happen.

What drives most of these apps, however, are Application Programming Interfaces

(APIs), which are the glue of the connected world we live in. APIs are everywhere, from

the doorbell in our smart homes to the traffic updates in our connected cars.

In web development, an API is a set of rules or contracts that dictate how consumers

should interact with services by explicitly defining expected inputs and outputs. This is

an architectural approach to abstract away the definition from the implementation.

Note Although other uses of APIs include libraries, frameworks, and operating

systems, the scope of this book will focus on the context of web-based APIs.

In this chapter, we will address the importance of APIs by understanding what they

are as well as by getting introduced to the different architectural styles of web API design.

We will then zoom into the REST architectural style and, by applying the six principles of

REST, learn what it means to have a RESTful service.

The Importance ofAPIs

In today’s modern, connected world, the API is one of the most critical elements of

cloud-based services. Having billions of services out there for consumption requires

good abstraction to promote compatibility, usability, and maintainability.

The API plays a crucial part in the integration of two systems, as it enforces a

standardized communication link between them. For example, an electrical drill

needs power from an electricity source for it to work. To be able to connect electrical

equipment to power sources, we need a wall socket and a plug.

2

In this analogy, the wall socket is the API for providing electricity, and the drill is

the consumer, as it uses a specific plug to be able to connect to power. One could, of

course, connect the drilling machine directly to the wiring circuit, but it would require

more manual work and be very unsafe. Imagine having to hardwire everything in your

home; the result would be a mess. The point here is that having a plug and wall-socket

mechanism drastically improves interoperability, allowing devices to be pluggable given

a standard interface.

Web APIs are no different, as they ensure that systems can communicate seamlessly

without the complexity of hardwiring. In fact, an API promotes accessibility by allowing

multiple systems to use one implementation of business logic, regardless of their

technology stack.

Imagine if the National Weather Service had to explicitly implement a system-

integration point for each of its consumer systems. Updates and maintenance would be

a nightmare, and that apparently wouldn’t scale very well. Instead, implement an API to

facilitate the flow of data in one standard way. Doing this also opens up the door to other

possibilities, like integration with third-party systems, which can lead to opportunities to

monetize on some of the internal components.

Other benefits of providing an API are control and analytics. It is vital that you secure

sensitive endpoints, and having a mechanism to control access is paramount. There is a

Dutch saying, “meten is weten,” which means measuring is knowing. Understanding how

services are used provides useful insights on feasibility and potential optimizations.

APIs can be implemented in many different architectural styles. The most common

styles that are used in the industry are RPC, WSDL, SOAP, and REST. When designing an

API, it is important to use the right style for the problem at hand, as each of the styles has

its advantages and disadvantages.

Note To keep things in perspective, we will mainly focus on the REST-based

architectural style. The others are only mentioned to broaden the understanding

within the context of REST.

CHAPTER 1 API DESIGN DEMYSTIFIED

剩余244页未读，继续阅读

weixin_38669689

粉丝: 27
资源: 300

最新资源

资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！点击此处反馈