Integration
697 items from stn1slv/awesome-integration ★566
-
Reference Data Holder microservice-api-patterns.org
How should data that is referenced in many places, lives long, and is immutable for clients be treated in API endpoints? How can such reference data be used in requests to and responses from Processing Resources or Information Holder Resources?
-
Operational Data Holder microservice-api-patterns.org
How can an API support clients that want to create, read, update, and/or delete instances of domain entities that represent operational data: data that is rather short-lived, changes often during daily business operations, and has many outgoing relations?
-
Master Data Holder microservice-api-patterns.org
How can I design an API that provides access to master data that lives for a long time, does not change frequently, and will be referenced from many clients?
-
Link Lookup Resource microservice-api-patterns.org
How can message representations refer to other, possibly many and frequently changing, API endpoints and operations without binding the message recipient to the actual addresses of these endpoints?
-
Data Transfer Resource microservice-api-patterns.org
How can two or more communication participants exchange data without knowing each other, without being available at the same time, and even if the data has already been sent before its recipients became known?
-
Processing Resource microservice-api-patterns.org
How can an API provider allow its clients to trigger an action in it?
-
Information Holder Resource microservice-api-patterns.org
How can domain data be exposed in an API, but its implementation still be hidden? How can an API expose data entities so that API clients can access and/or modify these entities concurrently without compromising data integrity and quality?
-
Linked Information Holder microservice-api-patterns.org
How can messages be kept small even when an API deals with multiple information elements that reference each other?
-
Embedded Entity microservice-api-patterns.org
How can one avoid sending multiple messages when their receivers require insights about multiple related information elements?
-
Service Level Agreement microservice-api-patterns.org
How can an API client learn about the specific quality-of-service characteristics of an API and its endpoint operations? How can these characteristics, and the consequences of not meeting them, be defined and communicated in a measurable way?
-
Rate Limit microservice-api-patterns.org
How can the API provider prevent API clients from excessive API usage?
-
Pricing Plan microservice-api-patterns.org
How can the API provider meter API service consumption and charge for it?
-
Wish Template microservice-api-patterns.org
How can an API client inform the API provider about nested data that it is interested in? How can such preferences be expressed flexibly and dynamically?
-
Wish List microservice-api-patterns.org
How can an API client inform the API provider at runtime about the data it is interested in?
-
Request Bundle microservice-api-patterns.org
How can the number of requests and responses be reduced to increase communication efficiency?
-
Pagination microservice-api-patterns.org
How can an API provider deliver large sequences of structured data without overwhelming clients?
-
Conditional Request microservice-api-patterns.org
How can unnecessary server-side processing and bandwidth usage be avoided when frequently invoking API operations that return rarely changing data?
-
Solution-Internal API microservice-api-patterns.org
How can access to and usage of an API be limited to an application, for instance, components in the same or another logical layer and/or physical tier?
-
Public API microservice-api-patterns.org
How can an API be made available to an unlimited and/or unknown number of API clients outside the organization that are globally, nationally, and/or regionally distributed?
-
Frontend Integration microservice-api-patterns.org
How can client-side end-user interfaces that are physically separated from server-side business logic and data storage be populated and updated with computing results, result sets from searches in data sources, and detailed information about data entities? How can application…
-
Community API microservice-api-patterns.org
How can the visibility of and the access to an API be restricted to a closed user group that does not work for a single organizational unit but for multiple legal entities (such as companies, nonprofit/nongovernment organizations, and governments)?
-
Backend Integration microservice-api-patterns.org
How can distributed applications and their parts, which have been built independently and are deployed separately, exchange data and trigger mutual activity while preserving system-internal conceptual integrity without introducing undesired coupling?
-
API Description microservice-api-patterns.org
Which knowledge should be shared between an API provider and its clients? How should this knowledge be documented?
-
Version Identifier microservice-api-patterns.org
How can an API provider indicate its current capabilities as well as the existence of possibly incompatible changes to clients in order to prevent malfunctioning of clients due to undiscovered interpretation errors?
-
Two In Production microservice-api-patterns.org
How can a provider gradually update an API without breaking existing clients but also without having to maintain a large number of API versions in production?
-
Semantic Versioning microservice-api-patterns.org
How can stakeholders compare API versions to detect immediately whether they are compatible?
-
Limited Lifetime Guarantee microservice-api-patterns.org
How can a provider let clients know for how long they can rely on the published version of an API?
-
Experimental Preview microservice-api-patterns.org
How can providers make the introduction of a new API, or new API version, less risky for their clients and obtain early adopter feedback without having to freeze the API design prematurely?
-
Eternal Lifetime Guarantee microservice-api-patterns.org
How can a provider support clients that are unable or unwilling to migrate to newer API versions at all?
-
Aggressive Obsolescence microservice-api-patterns.org
How can API providers reduce the effort for maintaining an entire API or its parts (such as endpoints, operations, or message representations) with guaranteed service quality levels?
-
API Design Patterns manning.com
JJ Geewax's catalog of design patterns for resource-oriented APIs, covering naming, pagination, versioning, and more.
-
Make (Integromat) make.com
Low-code automation tool with a visual interface, advanced data transformation, and modular workflow execution.
-
SAP Certified Associate - Integration Developer learning.sap.com
Validates that the candidate possesses the fundamental and core knowledge required of the SAP Integration Suite profile.
-
SnapLogic Integrator Certification learn.snaplogic.com
Focuses on topics such as beginner training, ultra tasks, pipeline migration, and user assistance videos covering various integration endpoints.
-
SnapLogic Developer Certification learn.snaplogic.com
Testing your expertise in using the SnapLogic SDK, implementing different parts of Snap functionality, and building custom Snaps.
-
SnapLogic Architect Certification learn.snaplogic.com
Evaluates your knowledge of integration reference architectures and key strategies for the SnapLogic platform, covering topics like SnapLogic Architecture, Snaplex Requirements, Pipeline Lifecycle Management, Advanced Data Transformations, API Management, Resumable Pipelines…
-
SnapLogic Administrator Certification learn.snaplogic.com
Assesses your ability to handle administrative tasks for SnapLogic instances.
-
SnapLogic Integrator Accreditation learn.snaplogic.com
It's designed for those who want to enhance their expertise on all core SnapLogic concepts for various integration needs across industries and lines of business.
-
Azure Schema Registry learn.microsoft.com
Schema registry hosted in Azure Event Hubs that centralizes schema management and governance for event-driven applications.
-
KubeMQ kubemq.io
Kubernetes-native message broker and queue system designed for scalability, high availability, and seamless cloud integration.
-
Kong Enterprise konghq.com
A cloud-native, enterprise-grade solution that enhances API connectivity, microservices orchestration, and security via a rich plugin architecture.
-
Kong AI Gateway konghq.com
Multi-LLM AI gateway built on Kong Gateway, offering semantic caching, prompt security, and AI observability through dedicated plugins.
-
Kong Gateway Certified Associate konghq.com
Validate your entry-level knowledge and skills on Kong Gateway for developers, DevOps, and architects.
-
Offset Explorer kafkatool.com
A comprehensive GUI for managing Apache Kafka clusters (formerly named Kafka Tool) with user-friendly monitoring and administration tools.
-
Kafka Streams kafka.apache.org
Client library for building streaming applications and microservices directly on top of Apache Kafka.
-
Kafka Connect kafka.apache.org
A tool for scalably and reliably streaming data between Apache Kafka and other systems.
-
JSON Lines jsonlines.org
A text format for storing structured data one record per line.
-
JSCAPE MFT Server jscape.com
Secure, protocol-agnostic platform with automation and compliance.
-
Jitterbit Harmony jitterbit.com
Comprehensive integration solution offering prebuilt workflows and automation templates to accelerate business processes.
-
JMS javaee.github.io
A messaging API that enables Java applications to send and receive messages. JMS supports reliable messaging and is widely used in enterprise-level applications.
- next page of items loading…
