Master this deck with 20 terms through effective study methods.
Generated from uploaded pdf
APIs can be distinguished by several characteristics including provisioning (public, private, partner), technical design style (REST, GraphQL, RPC, SOAP), protocol used (HTTP(S), MQTT, AMQP), and data format (XML, JSON, YAML, CSV).
The three types of API provisioning are public APIs, which are available to any developer; private APIs, which are used internally within an organization; and partner APIs, which are shared with specific business partners.
REST is an architectural style that uses standard HTTP methods and is stateless, while SOAP is a protocol that relies on XML messaging and has strict standards for security and transactions.
Common protocols used in API communication include HTTP(S), MQTT, AMQP, CoAP, and SOAP, each serving different use cases and requirements.
APIs typically support various data formats including XML, JSON, YAML, CSV, TXT, ODATA, and HTML, allowing for flexible data interchange.
Most API types are designed for transactional connections, focusing on quick, efficient exchanges of small data packets rather than bulk data transfers.
Loose coupling allows clients and servers to interact through data without depending on each other's internal workings, enhancing flexibility and scalability.
Statelessness means that each API call is independent, with no stored context from previous requests, ensuring that each request is treated as a new transaction.
Caching allows responses to be stored temporarily, reducing the need for redundant requests for the same resource, which improves response times and reduces server load.
A uniform interface means that each resource in a REST API has a unique identifier (URI), allowing for consistent access and interaction with the API.
Web-scale refers to the ability to manage system growth that is not linear, addressing explosive changes in demand and load while decoupling user experience from underlying services.
Microservice architecture consists of small, independent services that communicate over a network, allowing for greater flexibility, scalability, and easier maintenance compared to monolithic architectures.
Horizontal integration involves connecting different systems or services at the same level of the supply chain, while vertical integration connects systems across different levels, from production to sales.
APIs enable seamless communication and data exchange between different organizational units and systems within the supply chain, enhancing efficiency and coordination.
Business logic defines the rules and processes that govern how data is created, stored, and manipulated within an application, serving as the backbone of application functionality.
The concept of web-scale SOA emerged in the 2010s, focusing on managing rapid growth and demand in software systems while decoupling user experience from backend services.
Using different data formats in APIs can affect interoperability, ease of use, and performance, as some formats may be more suitable for specific applications or environments.
Having a unique identifier for each resource allows for consistent access and interaction, making it easier for developers to work with the API and ensuring clarity in resource management.
Organizations may face challenges such as ensuring security, managing versioning, maintaining documentation, and ensuring compatibility with existing systems when implementing APIs.
APIs support loose coupling by allowing different components of a system to communicate through well-defined interfaces, reducing dependencies and enabling easier updates and changes.