@milan_milanovic: ๐ ๐ผ๐ฑ๐ฒ๐ฟ๐ป ๐๐ฃ๐ ๐๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐๐๐ฟ๐ฎ๐น ๐ฆ๐๐๐น๐ฒ...
@milan_milanovic
26 views
Dec 21, 2023
1
๐ ๐ผ๐ฑ๐ฒ๐ฟ๐ป ๐๐ฃ๐ ๐๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐๐๐ฟ๐ฎ๐น ๐ฆ๐๐๐น๐ฒ๐
Architectures for APIs have evolved along with how we use technology. The API market is now growing, necessitating the development of new API architectural styles that address scenarios other than client/server. Yet, we may steer our API style in a more unified direction by applying one of several used design architectures, cutting down on development time, boosting developer productivity, and streamlining the API life cycle.
There are ๐ณ๐ผ๐๐ฟ ๐บ๐ฎ๐ถ๐ป ๐ฎ๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐๐๐ฟ๐ฎ๐น ๐ฑ๐ฒ๐๐ถ๐ด๐ป ๐๐๐๐น๐ฒ๐ in the area of API design, each with its own user experience, history, and strategy for online apps and API connections. Although these designs are not incompatible, being aware of their differences can help you decide which design approach to use and whether it will lead you down a similar path of happiness and prosperity.
๐ญ. ๐จ๐ฅ๐ ๐ฆ๐๐๐น๐ฒ
The most well-known and utilized web architectural style in use right now is the URI style. It is far less complicated than others since URI-style APIs are simple to create and use. Create, read, delete, and update invocations are all connected to built-in HTTP protocol functions, making a simplified set of operations to act on the more exposed nature of an object/resource-oriented API style. Many of the most fundamental operations a developer could want are mapped to the HTTP methods and functionalities.
๐ฎ. ๐๐๐ฒ๐ป๐-๐๐ฟ๐ถ๐๐ฒ๐ป ๐ฆ๐๐๐น๐ฒ
This style is new and has become more well-known in recent years. The WebSocket protocol, which offers full-duplex data communication between a client and server, illustrates an event-driven architectural design. This, combined with implemented support for asynchronous messaging, results in a potent API that can handle complex invocations, large data transfers, and modern transport methodologies.
๐ฏ. ๐๐๐ฝ๐ฒ๐ฟ๐บ๐ฒ๐ฑ๐ถ๐ฎ ๐ฆ๐๐๐น๐ฒ
Like the URI approach, it uses hypermedia to generate more task-focused interactions than object-focused ones. These involve browser-based machine interaction. A Hypermedia API offers links to navigate a process and template input to request information, much like how you use links to navigate the Web and forms to enter data.
๐ฐ. ๐ง๐๐ป๐ป๐ฒ๐น๐ถ๐ป๐ด ๐ฆ๐๐๐น๐ฒ
The SOAP messaging standard is the most well-known example of the Tunneling API style. SOAP specifies an RPC-like interface for application integration and uses the WSDL standard to describe the interface. Based on a WSDL document, client applications can produce proxy code and make calls as if the remote component were local. This style is outdated today.
#api
Architectures for APIs have evolved along with how we use technology. The API market is now growing, necessitating the development of new API architectural styles that address scenarios other than client/server. Yet, we may steer our API style in a more unified direction by applying one of several used design architectures, cutting down on development time, boosting developer productivity, and streamlining the API life cycle.
There are ๐ณ๐ผ๐๐ฟ ๐บ๐ฎ๐ถ๐ป ๐ฎ๐ฟ๐ฐ๐ต๐ถ๐๐ฒ๐ฐ๐๐๐ฟ๐ฎ๐น ๐ฑ๐ฒ๐๐ถ๐ด๐ป ๐๐๐๐น๐ฒ๐ in the area of API design, each with its own user experience, history, and strategy for online apps and API connections. Although these designs are not incompatible, being aware of their differences can help you decide which design approach to use and whether it will lead you down a similar path of happiness and prosperity.
๐ญ. ๐จ๐ฅ๐ ๐ฆ๐๐๐น๐ฒ
The most well-known and utilized web architectural style in use right now is the URI style. It is far less complicated than others since URI-style APIs are simple to create and use. Create, read, delete, and update invocations are all connected to built-in HTTP protocol functions, making a simplified set of operations to act on the more exposed nature of an object/resource-oriented API style. Many of the most fundamental operations a developer could want are mapped to the HTTP methods and functionalities.
๐ฎ. ๐๐๐ฒ๐ป๐-๐๐ฟ๐ถ๐๐ฒ๐ป ๐ฆ๐๐๐น๐ฒ
This style is new and has become more well-known in recent years. The WebSocket protocol, which offers full-duplex data communication between a client and server, illustrates an event-driven architectural design. This, combined with implemented support for asynchronous messaging, results in a potent API that can handle complex invocations, large data transfers, and modern transport methodologies.
๐ฏ. ๐๐๐ฝ๐ฒ๐ฟ๐บ๐ฒ๐ฑ๐ถ๐ฎ ๐ฆ๐๐๐น๐ฒ
Like the URI approach, it uses hypermedia to generate more task-focused interactions than object-focused ones. These involve browser-based machine interaction. A Hypermedia API offers links to navigate a process and template input to request information, much like how you use links to navigate the Web and forms to enter data.
๐ฐ. ๐ง๐๐ป๐ป๐ฒ๐น๐ถ๐ป๐ด ๐ฆ๐๐๐น๐ฒ
The SOAP messaging standard is the most well-known example of the Tunneling API style. SOAP specifies an RPC-like interface for application integration and uses the WSDL standard to describe the interface. Based on a WSDL document, client applications can produce proxy code and make calls as if the remote component were local. This style is outdated today.
#api
2
To expand your knowledge and personal growth, subscribe to my free weekly newsletter with 20,000+ people: https://t.co/MMCXxQQR4F.