API service development history and technological evolution

With the development of the times, API has become the main way for modern enterprises to develop online businesses and standardize data operations. After repeated cooperation and exchanges, it gradually evolved into API economic activities. API services are the product of mutual cooperation between developers and demanders. API services mainly refer to developers using a certain platform or resources to provide API interfaces to demanders. This can be a specific development platform, or it can be resources such as data information, or a standardized database, resource library, etc. The API service provides a good data interaction service between different institutions to achieve high-quality and quantifiable transactions.

To date, there are more than 20 million API developers around the world who have created more than 10 billion APIs. Where there is the Internet, there are APIs. It can be said that API has become the key to unlocking the future. It is the gateway for all data interaction and an important way for developers to output data and services.

1. API 1.0 era, focusing on enterprise internal system integration

Dating back to 1989, Tim Berners-Lee defined the emergence of Web 1.0. Web 1.0 only provided simple static pages, which allowed users to view web pages. The emergence of Mosaic, the first browser, created a precedent for the Internet. At that time, API services had not yet been formed. Until 2000, when enterprise internal management system technology reached a mature stage, enterprises began to introduce RESTful APIs to automate enterprise communications, and designed and created public APIs, private APIs, and internal APIs. Among them, the public API is a consumer-oriented application based on client development; the private API is an efficient communication for enterprise management of internal work, which can be reorganized and modernized; the internal API is to optimize the accuracy of analysis results, The key to intelligence is to encrypt and protect various data generated during the operation of private APIs.

Technology is changing with each passing day. As people's requirements for the Internet increase, the emergence of Web 2.0 ushered in a new media era. With the popularity of maps and their designable appearance, people can operate freely using Web tools. With the emergence of social platforms from 2003 to 2006 , the self-media industry began to rise, and API services once again set off a technological revolution. People began to use API services for various content such as web links and photos. From 2006 to 2008, API 1.0 showed a rapid development trend.

In this process, the characteristics of API 1.0 services can be summarized. Because early API services mainly existed in the form of a monolithic architecture through short-lived links between servers and browsers, they had an obvious hierarchical structure. From information collection, storage to protection, there were clear business logic pipelines, showing A clear picture of IT architecture. The advantage is that the structure is clear and clear, and there is a preliminary awareness of data protection to ensure the safe circulation of corporate data. The disadvantage is that it cannot meet the needs of data communication between enterprises in the industry. When calling information, it is often necessary to copy the overall architecture, which is prone to repeated calls, slow speed, cumbersome and complex information, etc., affecting social and economic benefits and service processes.

2. API 2.0 era, realizing cross-platform system docking

Beginning in 2008, following the trend of the web 2.0 era, enterprise system resources finally transcended the internal scope, and the emergence of UDDI technology created a new API port. UDDI can be collectively referred to as a directory service. It mainly describes, discovers and integrates data information. It is a platform-independent search framework. Users can use the Internet to describe services and retrieve relevant information. UDDI can be called a service architecture, because it faces not only internal enterprises, but also more enterprise users. The relevant UDDI API ports can directly search data based on the SOAP access protocol. SOAP is used for information exchange in retrieval computing environments, allowing developers to access objects, servers, etc. in a platform-independent manner.

Based on the characteristics of API services in the API 2.0 era, it can be referred to as SOA architecture design . The advantage of SOA is that it gets rid of the shortcomings of a single-layer architecture and adopts a layered architecture, which can avoid the duplication of information to a certain extent. At the same time, it further proposes the concepts of message bus (MQ) and service reuse. In this model, the IT architecture is divided into three major layers according to its functional characteristics, namely component layer, Web service layer and business process layer. Among them, the component layer mainly includes various types of application systems. In the important IT design process, the component layer forms independent information components with its distributed technical characteristics, which also brings certain benefits to the integrated development of applications. The difficulty of the challenge; the Web service layer exists to solve integration problems. The Web service layer uses descriptive language to define discrete business functions and supports the transformation of distributed component technologies into corresponding document information - WSDL . Developers only need to follow the relevant descriptions of WSDL to perform business operations; the business process layer is the actual operation and implementation of the final business, and the business is built on the basis of the Web service layer.

But the shortcomings are also obvious. This architecture is not separated from the systematic overall deployment. When developers want to update and maintain parts, they often involve overall architectural adjustments, which makes operation, maintenance and upgrades difficult and does not conform to actual operating conditions. People are beginning to demand more flexible and agile architecture models.

3. API 3.0 era, cloud platform distributed application architecture

In 2014, the concept of "cloud computing" spread all over the world. The ecological changes in the Internet industry changed the concepts of many manufacturers, and the traditional independent application architecture was gradually abandoned. The industry is showing a vertical development trend. Its business form has shifted from simple computer PC networks to WAP terminals, mobile terminals, dedicated terminals, etc. API services have also seen new changes - the concept of cloud platform distributed applications has emerged.

Cloud platform distributed applications mainly use the Rest architecture to solve the problem of how to split an application when multiple processes run simultaneously and errors occur, with both speed and efficiency. The basic logic of Rest operation is to identify the problem location and compare various solutions based on the Web architecture. Rest architecture is widely used in cloud computing. It can quickly identify running problems and provide solutions.

For modern enterprises, the scale of traditional centralized storage has reached a bottleneck after digital transformation. The distributed cloud infrastructure can separate the main system into various working nodes, and provide efficient and fast computing through the mutual cooperation and operation between nodes. and storage capacity. Storage capabilities can be divided into integrated deployment and separated deployment. Integrated deployment is often used in cloud platform management area services, which can provide business functions to multiple users at the same time and intelligently generate deployment plans. This means that developers can perform independent network deployments on the front and back ends at the same time. The advantage of this architecture is that it can be debugged and called flexibly without worrying about the impact of local changes on the whole. The disadvantage is that the security of the data is reduced because it is exposed on the public network.

The pirated resources of "Qing Yu Nian 2" were uploaded to npm, causing npmmirror to have to suspend the unpkg service. Zhou Hongyi: There is not much time left for Google. I suggest that all products be open source. Please tell me, time.sleep(6) here plays a role. What does it do? Linus is the most active in "eating dog food"! The new iPad Pro uses 12GB of memory chips, but claims to have 8GB of memory. People’s Daily Online reviews office software’s matryoshka-style charging: Only by actively solving the “set” can we have a future. Flutter 3.22 and Dart 3.4 release a new development paradigm for Vue3, without the need for `ref/reactive `, no need for `ref.value` MySQL 8.4 LTS Chinese manual released: Help you master the new realm of database management Tongyi Qianwen GPT-4 level main model price reduced by 97%, 1 yuan and 2 million tokens
{{o.name}}
{{m.name}}

Guess you like

Origin my.oschina.net/u/5925727/blog/11112167