awesome-awesomeness/terminal/integration2

                                                                                   Awesome Integration !Awesome (https://awesome.re/badge.svg) (https://awesome.re)

▐ A curated list of awesome system integration software, patterns and resources.

System integration is the process of linking together different IT systems (components) to functionally cooperate as a whole.

Contents
- Projects (#projects)
  - API Management (#api-management)
  - API Design (#api-design)
  - API Documentation (#api-documentation)
  - API Gateway (#api-gateway)
  - API Testing (#api-testing)
  - BRE (#bre)
  - BPM (#bpm)
  - Data Mapping Solution (#data-mapping-solution)
  - CDC (#cdc)
  - ESB (#esb)
  - ETL (#etl)
  - Integration Frameworks (#integration-frameworks)
  - iPaaS (#ipaas)
  - MaaS (#maas)
  - MFT (#mft)
  - MDM (#mdm)
  - Messaging (#messaging)
  - RPA (#rpa)
  - Self-Service Integration (#self-service-integration)
  - Workflow engine (#workflow-engine)
- Integration Patterns (#integration-patterns)
  - Enterprise Integration Patterns (#enterprise-integration-patterns)
  - Integration Architecture Patterns (#integration-architecture-patterns)
  - Microservice API Patterns (#microservice-api-patterns)
  - SOA Patterns (#soa-patterns)
- Resources (#resources)
  - API Specification (#api-specification)
  - Articles (#articles)
  - Certifications (#certifications)
  - Connectors (#connectors)
  - Data Formats (#data-formats)
  - Integration Styles (#integration-styles)
  - Market Analysis (#market-analysis)
  - Protocols (#protocols)
  - Standard APIs (#standard-apis)
  - Structure and Validation (#structure-and-validation)

――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
Projects
API Management
API Management solutions offer a comprehensive approach to handling the entire API lifecycle. They enable developers to create, publish, secure, and monitor APIs, ensuring efficient and reliable communication between systems. With features such 
as authentication, rate limiting, and analytics, these tools provide centralized control and enhanced security, making it easier to manage and scale APIs across different platforms and environments.
- Akana API Management Platform (https://www.akana.com/products/api-platform) - Provides comprehensive lifecycle management, enabling rapid digital transformation and robust compliance across multi-cloud environments.
- Amazon API Management (https://aws.amazon.com/api-gateway/api-management/) - Leverages AWS scalability and security to efficiently create, monitor, and manage APIs.
- Anypoint Platform (https://www.mulesoft.com/platform/api/manager) - Combines API design, integration, and management into one unified platform, streamlining connectivity and development.
- Amplify API Management Platform (https://www.axway.com/en/products/amplify-api-management-platform) - Offers an open, agile approach to API management with robust integration and flexible deployment options.
- Apigee (https://cloud.google.com/apigee) - Delivers powerful analytics, security, and scalability for enterprise-grade API management from Google.
- Azure API Management (https://azure.microsoft.com/en-us/services/api-management/) - A hybrid, multicloud solution that simplifies API lifecycle management with comprehensive security and analytics.
- Boomi Cloud API Management (https://developer.mashery.com/) - A cloud-native platform enabling seamless API deployment and centralized management with strong integration capabilities.
- DigitMarket API Manager (https://www.torryharris.com/products/digitmarket-api-manager-for-api-management) - Transforms APIs into strategic business tools through end-to-end lifecycle management and enhanced operational insights.
- Gravitee.io API Management (⭐273) (https://github.com/gravitee-io/gravitee-api-management) - A lightweight, open-source platform offering flexible API governance, robust security, and straightforward configuration.
- IBM API Connect (https://www.ibm.com/cloud/api-connect) - Provides a scalable, secure, and intuitive environment for creating, managing, and monetizing APIs across clouds.
- IBM webMethods API Management (https://www.ibm.com/products/webmethods-api-management) - Offers a comprehensive suite for API lifecycle management that seamlessly integrates on-premises and cloud systems.
- Kong Enterprise (https://konghq.com/products/kong-enterprise) - A cloud-native, enterprise-grade solution that enhances API connectivity, microservices orchestration, and security via a rich plugin architecture.
- Layer7 API Management (https://www.broadcom.com/products/software/api-management) - Ensures secure and efficient API development with continuous lifecycle management and advanced integration features.
- Red Hat 3scale API Management (https://www.redhat.com/en/technologies/jboss-middleware/3scale) - Simplifies API monetization and governance with a cloud-native approach and powerful scaling capabilities.
- Sensedia API Management (https://www.sensedia.com/api-management-platform) - Provides a full-lifecycle API solution with advanced security, performance monitoring, and streamlined integration.
- Traefik API Management (https://traefik.io/traefik-hub) - Provides an API Management as Code platform to DevOps and Platform Engineering Teams who favor less ClickOps and more GitOps-driven API lifecycle workflows.
- Tyk API Management (https://tyk.io/api-lifecycle-management/) - Delivers high-performance, open-source API management focused on flexibility, robust security, and scalability.
- WSO2 API Manager (⭐906) (https://github.com/wso2/product-apim) - A fully open-source API platform offering robust governance, flexible deployment, and community-driven innovation.
- Zuplo API Management (https://zuplo.com) - A developer-centric, lightweight platform featuring GitOps integration, rapid edge deployment, extensive OpenAPI support, and seamless monetization.

⬆ back to top (#contents)

API Design
API design, documentation, and life-cycle automation tools streamline the process of creating, maintaining, and evolving APIs. These tools offer efficient means to design consistent and scalable APIs, generate comprehensive documentation, and 
automate various stages of the API life-cycle, enhancing developer experience and promoting API adoption.
- Apicurio Studio (⭐1k) (https://github.com/apicurio/apicurio-studio) - A web-based, open-source API design tool that leverages the OpenAPI specification.
- Dredd (⭐4.2k) (https://github.com/apiaryio/dredd) - Validate API description docs against backend implementation using this language-agnostic CLI tool.
- OpenAPI-GUI (⭐1.4k) (https://github.com/Mermade/openapi-gui) - Create and validate OpenAPI specs with ease using this intuitive graphical user interface.
- OpenAPI Diff (⭐951) (https://github.com/OpenAPITools/openapi-diff) - Compare OpenAPI specs with version control and visualize the differences in HTML or Markdown format.
- OpenAPI Generator (⭐24k) (https://github.com/OpenAPITools/openapi-generator) - Automate the creation of API client libraries, server stubs, documentation and config files with this powerful OpenAPI Spec tool.
- OpenAPI Style Validator (⭐218) (https://github.com/OpenAPITools/openapi-style-validator) - Ensure that your OpenAPI specs meet your organization's standards with this flexible and customizable style validator.
- Spectral (⭐2.7k) (https://github.com/stoplightio/spectral) - Detect and fix errors in your JSON/YAML files using this linter tool that supports OpenAPI 3.0 & 2.0 and AsyncAPI.
- Swagger Editor (⭐9.2k) (https://github.com/swagger-api/swagger-editor) - Create, describe, and document your API with ease using this open source editor built specifically for OpenAPI-based APIs.
- Zally (⭐926) (https://github.com/zalando/zally) - Ensure the quality of your OpenAPI specs with this linter tool that provides extensive analysis and feedback.


⬆ back to top (#contents)

API Documentation
Explore a collection of tools and platforms designed to create, maintain, and present clear, concise, and user-friendly documentation for APIs. These resources facilitate seamless collaboration between developers and enable effective 
communication of API functionalities and specifications.
- DapperDox (⭐420) (https://github.com/DapperDox/dapperdox) - Generates elegant, interactive API documentation from OpenAPI/Swagger specs with easy customization and automated updates.
- OpenAPI Explorer (⭐334) (https://github.com/Rhosys/openapi-explorer) - Creates intuitive, interactive user interfaces from OpenAPI specs, simplifying API exploration and testing.
- RapiDoc (⭐1.8k) (https://github.com/rapi-doc/RapiDoc) - Produces highly customizable, interactive API documentation with responsive design and rich configuration options.
- Redoc (⭐24k) (https://github.com/Redocly/redoc) - Delivers clean, modern documentation with advanced theming, multi-language support, and seamless integration.
- Slate (⭐36k) (https://github.com/slatedocs/slate) - Converts markdown into stylish, static API documentation with intuitive navigation and clear code examples.
- Stoplight Elements (⭐2k) (https://github.com/stoplightio/elements) - Provides modular, attractive UI components for building comprehensive API reference and tutorial documentation.
- SwaggerHub (https://swagger.io/tools/swaggerhub/) - An integrated API design and documentation hub that enhances team collaboration, version control, and automated testing.
- Swagger UI (⭐27k) (https://github.com/swagger-api/swagger-ui) - Offers an interactive, in-browser tool for visualizing and testing APIs directly from OpenAPI specifications.
- SpectaQL (⭐1.1k) (https://github.com/anvilco/spectaql) - Generates static, customizable documentation for GraphQL schemas, making complex API structures easy to understand.
- Zudoku (⭐256) (https://github.com/zuplo/zudoku) - A customizable framework built on OpenAPI, focused on delivering exceptional developer experiences through quality documentation.


⬆ back to top (#contents)

API Gateway
API Gateways act as intermediaries between client applications and backend services, enabling key features such as request routing, authentication, rate limiting, and caching. They simplify the process of managing, securing, and monitoring APIs 
by providing a unified entry point for various services.
- Apinto (⭐1.5k) (https://github.com/eolinker/apinto) - A Golang-based gateway that offers dynamic routing, multi-tenancy, and robust API access control for modern architectures.
- Ambassador Edge Stack (https://www.getambassador.io/products/edge-stack/api-gateway/) - A Kubernetes-native API gateway designed for high-scale environments with flexible routing and advanced security features.
- Apache APISIX (⭐15k) (https://github.com/apache/apisix) - A high-performance, dynamic gateway featuring real-time traffic management and powerful plugin integrations.
- Apache ShenYu (⭐8.6k) (https://github.com/apache/shenyu) - A Java-native gateway excelling in protocol conversion, service proxying, and comprehensive API governance.
- Envoy Gateway (⭐1.9k) (https://github.com/envoyproxy/gateway) - CNCF Envoy-based gateway with Gateway API, mTLS, JWT, and other built-ins.
- Gloo Edge (⭐106) (https://github.com/solo-io/gloo) - An Envoy Proxy–based gateway offering advanced traffic control, enhanced security, and observability for microservices ecosystems.
- Kong API Gateway (⭐41k) (https://github.com/Kong/kong) - A scalable, cloud-native gateway that simplifies API management through extensive plugin support and seamless microservices integration.
- KrakenD API Gateway (⭐2.2k) (https://github.com/devopsfaith/krakend-ce) - An ultra-high performance gateway with efficient middleware configuration, robust security, and seamless scaling.
- Ocelot (⭐8.5k) (https://github.com/ThreeMammals/Ocelot) - A .NET-based gateway offering intuitive routing and easy integration for lightweight API management.
- Spring Cloud Gateway (⭐4.6k) (https://github.com/spring-cloud/spring-cloud-gateway) - Leverages the Spring ecosystem to deliver robust routing, filtering, and security for microservices.
- Traefik API Gateway (⭐55k) (https://github.com/traefik/traefik) - Combines Traefik Proxy, a fully declarative application proxy with enterprise-grade access control, distributed security, and premium integrations.
- Tyk API Gateway (⭐10k) (https://github.com/TykTechnologies/tyk) - An enterprise-grade, open-source gateway supporting REST, GraphQL, TCP, and gRPC with advanced rate limiting and analytics.


⬆ back to top (#contents)

API Testing
The API testing tools section provides a list of software tools and frameworks that developers can use to test REST APIs and message brokers. This section includes GUI clients for testing REST APIs and message brokers, mocking tools for 
simulating API responses, as well as various testing tools and frameworks to automate testing processes.
- API clients
   - Advanced REST Client (⭐1.4k) (https://github.com/advanced-rest-client/arc-electron) - A robust open-source API client for testing and debugging RESTful services with an intuitive interface.
   - Bruno (⭐35k) (https://github.com/usebruno/bruno) - A fast, offline API client designed for git-friendly workflows and seamless testing.
   - curl (⭐38k) (https://github.com/curl/curl) - A versatile command-line tool for data transfer across multiple protocols, essential for quick API testing.
   - curlie (⭐3.3k) (https://github.com/rs/curlie) - A modern, user-friendly frontend to curl that combines simplicity with powerful performance.
   - HTTPie (⭐36k) (https://github.com/httpie/httpie) - An intuitive CLI HTTP client that simplifies crafting API requests and inspecting responses.
   - HttpMaster (https://www.httpmaster.net/) - Free and lightweight desktop tool for HTTP testing and debugging.
   - Hoppscotch (⭐72k) (https://github.com/hoppscotch/hoppscotch) - A lightweight, web-based API development tool offering real-time testing with an intuitive interface.
   - Insomnia (⭐36k) (https://github.com/Kong/insomnia) - A cross-platform client that streamlines API debugging and testing for both REST and GraphQL services.
   - posting (⭐9.4k) (https://github.com/darrenburns/posting) - A modern, terminal-based API client designed for efficient and seamless API interactions.
   - Postman (https://www.postman.com/product/api-client/) - The industry-standard tool for API development and testing, featuring automation, mock servers, and collaborative documentation.
   - resty (⭐2.6k) (https://github.com/micha/resty) - A Lua-based HTTP client framework providing an interactive shell for streamlined REST service testing.
   - SoapUI (⭐1.6k) (https://github.com/SmartBear/soapui) - A comprehensive open-source solution for testing both SOAP and REST web services with extensive automation features.
- MQ clients
   - JMSToolBox (⭐216) (https://github.com/jmstoolbox/jmstoolbox) - A universal JMS client offering broad compatibility and streamlined messaging testing across various brokers.
   - kcat (⭐5.5k) (https://github.com/edenhill/kcat) - A lightweight command-line tool for Apache Kafka, providing efficient message production and consumption.
   - MQTT Explorer (⭐3.4k) (https://github.com/thomasnordquist/MQTT-Explorer) - A detailed MQTT client delivering structured topic visualization and intuitive debugging.
   - Offset Explorer (https://www.kafkatool.com) - A comprehensive GUI for managing Apache Kafka clusters with user-friendly monitoring and administration tools.
   - Service Bus Explorer (⭐2.1k) (https://github.com/paolosalvatori/ServiceBusExplorer) - An advanced GUI for Azure Service Bus that enables in-depth testing and seamless management of topics, queues, and subscriptions.
- Mocking tools
   - Hoverfly (⭐2.4k) (https://github.com/SpectoLabs/hoverfly) - A lightweight API simulation tool that enables rapid HTTP(S) service virtualization for efficient testing.
   - Imposter (⭐391) (https://github.com/outofcoffee/imposter) - A flexible mock server supporting REST, OpenAPI, SOAP, and more to simulate diverse API behaviors.
   - Microcks (⭐1.6k) (https://github.com/microcks/microcks) - A Kubernetes-native tool for API mocking and testing that supports AsyncAPI, OpenAPI, and Postman Collections.
   - Mockable (https://www.mockable.io/) - An easy-to-configure service for creating custom HTTP responses, ideal for rapid prototyping and testing.
   - Mockbin (⭐113) (https://github.com/zuplo/mockbin) - A simple endpoint generator for testing HTTP requests with real-time logging and feedback.
   - Mockoon (⭐7.4k) (https://github.com/mockoon/mockoon) - A user-friendly tool for designing and running mock REST APIs with real-time simulation and easy setup.
   - MockServer (⭐4.7k) (https://github.com/mock-server/mockserver) - A powerful solution for mocking any HTTP/HTTPS-based service, streamlining integration testing.
   - Mocky (⭐2k) (https://github.com/MockyAbstract/Mocky) - A free online service that generates custom HTTP responses for testing API endpoints.
   - Prism (⭐4.6k) (https://github.com/stoplightio/prism) - An open-source HTTP mock server that replicates API behavior for early testing and validation.
   - WireMock (⭐6.8k) (https://github.com/tomakehurst/wiremock) - A robust and flexible API mocking tool delivering reliable, real-time simulation for comprehensive testing.
- Testing tools and frameworks
   - Apache JMeter (⭐8.8k) (https://github.com/apache/jmeter) - A feature-rich tool for load testing and performance analysis across diverse web applications and services.
   - Gatling (⭐6.7k) (https://github.com/gatling/gatling) - A powerful load testing framework with a developer-friendly DSL that delivers detailed performance metrics.
   - Grafana k6 (⭐28k) (https://github.com/grafana/k6) - Open-source, JS-scriptable load-testing tool for CI/CD.
   - Karate (⭐8.5k) (https://github.com/karatelabs/karate) - A unified testing framework that merges API automation, mocking, and performance testing with simple, expressive syntax.
   - Pyresttest (⭐1.1k) (https://github.com/svanoort/pyresttest) - A Python-based testing tool offering easy YAML/JSON-driven REST API testing and microbenchmarking.
   - REST Assured (⭐6.9k) (https://github.com/rest-assured/rest-assured) - A Java DSL that simplifies REST API testing with intuitive syntax and seamless integration into CI pipelines.
   - Schemathesis (⭐2.5k) (https://github.com/schemathesis/schemathesis) - A Python library for property-based testing of API schemas, ensuring reliability through robust edge-case detection.
   - Taurus (⭐2k) (https://github.com/Blazemeter/taurus) - An open-source automation framework that simplifies continuous testing with intuitive configuration and integration support.


⬆ back to top (#contents)

BRE
Business Rules Engines and Business Rules Management Systems (BRMS) are software systems that allow organizations to define, manage, and execute business rules. These rules are used to automate decision-making processes, enforce business 
policies, and ensure regulatory compliance. A BRMS provides a way for organizations to centrally manage their business rules and make changes to them quickly and easily, without requiring changes to the underlying code. It is a valuable tool for 
businesses that need to be agile and respond quickly to changing market conditions.
- Drools (⭐6k) (https://github.com/apache/incubator-kie-drools) - Open-source engine that supports advanced Decision Model and Notation (DMN) with Eclipse IDE integration for efficient rule development.
- Easy Rules (⭐5k) (https://github.com/j-easy/easy-rules) - Lightweight Java-based rules engine designed for straightforward rule processing and rapid decision automation.
- FICO Blaze Advisor (https://www.fico.com/en/products/fico-blaze-advisor) - Enterprise-grade decision engine that empowers both business and technical users with an intuitive interface for fast rule creation and management.
- IBM ODM (https://www.ibm.com/products/operational-decision-manager) - Scalable decision management system that streamlines rule authoring, testing, and updates while ensuring compliance and agility.
- NxBRE (⭐132) (https://github.com/ddossot/NxBRE) - Specialized .NET open-source rule engine offering efficient rule processing tailored for Microsoft environments.
- OpenL Tablets (⭐172) (https://github.com/openl-tablets/openl-tablets) - Flexible open-source decision management system that simplifies defining and executing business rules and decision tables.
- Progress Corticon (https://www.progress.com/corticon) - Model-driven BRMS enabling rapid, no-code rule creation that delivers high-performance automated decisions with guaranteed integrity.
- Red Hat Decision Manager (https://access.redhat.com/products/red-hat-decision-manager) - Enterprise-class decision platform built on Drools, offering advanced DMN support, intuitive UIs, and high availability for large-scale automation.
- ZEN Engine (⭐1.1k) (https://github.com/gorules/zen) - A cross-platform, open-source Business Rules Engine written in Rust that executes JSON Decision Models through interconnected graphs of decision tables, functions, and expressions.


⬆ back to top (#contents)

BPM
BPM solutions are software tools that help businesses streamline and automate their operational processes to improve efficiency and productivity. These solutions typically provide features such as process modeling, workflow management, task 
automation, and reporting. They can be used to automate a wide range of processes, from simple tasks like data entry to complex workflows involving multiple departments and stakeholders.
- Appian BPM Suite (https://appian.com/platform/complete-automation/business-process-management-bpm.html) - Low-code BPM platform that empowers both IT and citizen developers to quickly build process- and case-centric applications.
- Genpack Cora SeQuence (https://www.genpact.com/cora/sequence) - Agile process orchestration tool that enhances business efficiency by seamlessly integrating and managing workflows.
- IBM Business Automation Workflow (https://www.ibm.com/products/business-automation-workflow) - Integrated platform combining workflow automation and BPM to optimize operational processes and decision-making.
- Oracle BPM Suite (https://www.oracle.com/middleware/technologies/bpm.html) - Comprehensive solution offering robust process modeling, workflow automation, and real-time analytics to drive operational excellence.
- Pega Platform (https://www.pega.com/products/platform) - Advanced BPM and RPA platform featuring intelligent process automation and workforce analytics to streamline operations.
- Red Hat Process Automation Manager (https://www.redhat.com/en/technologies/jboss-middleware/process-automation-manager) - Cloud-native platform that enables cross-functional teams to design, deploy, and manage automated business workflows with 
agility.
- SAP Process Orchestration (https://www.sap.com/products/process-orchestration.html) - Robust BPM offering that combines process orchestration with application integration for end-to-end operational efficiency.
- TIBCO BPM Enterprise (https://www.tibco.com/products/business-process-management) - Enterprise BPM solution delivering process automation, documentation, and predictive analytics to enhance performance and decision-making.


⬆ back to top (#contents)

Data Mapping Solution
Data Mapping tools are used to define and transform data between different systems, applications, and formats. These tools allow for the mapping of data from source to target, allowing for data transformation and integration. This section covers 
different data mapping solutions that can be used to facilitate data mapping and transformation processes for different use cases.
- Altova MapForce (https://www.altova.com/mapforce) - Graphical data mapping solution that enables any-to-any conversion, reducing complexity and accelerating integration projects.
- AtlasMap (⭐203) (https://github.com/atlasmap/atlasmap) - Interactive web-based tool that simplifies mapping across Java, XML, CSV, and JSON data sources with an intuitive interface.
- JOLT (⭐1.6k) (https://github.com/bazaarvoice/jolt) - Java-based JSON transformation library that uses a specification-driven approach for effortless JSON-to-JSON conversions.
- JSLT (⭐670) (https://github.com/schibsted/jslt) - Powerful JSON query and transformation language inspired by jq and XPath, designed for rapid and flexible data manipulation.


⬆ back to top (#contents)

CDC
Change Data Capture (CDC) solutions enable real-time identification and capture of changes made to data in databases, data warehouses, and other data sources. These tools continuously monitor data changes and propagate them to downstream systems,
enabling real-time data synchronization, event-driven architectures, and maintaining data consistency across distributed systems. CDC is essential for modern data architectures, microservices, and real-time analytics.
- Debezium (⭐11k) (https://github.com/debezium/debezium) - Open-source distributed platform for change data capture that turns your existing databases into event streams for real-time data integration.
- IBM InfoSphere CDC (https://www.ibm.com/products/infosphere-change-data-capture) - Enterprise CDC solution that captures and delivers data changes with minimal impact on source systems and low latency.
- Maxwell's daemon (⭐4.1k) (https://github.com/zendesk/maxwell) - An open-source CDC tool for MySQL that reads database binlogs and streams row-level changes as JSON to systems like Kafka, Kinesis, or other destinations.
- Oracle GoldenGate (https://www.oracle.com/integration/goldengate/) - Enterprise-grade real-time data integration and replication solution that provides comprehensive CDC capabilities for heterogeneous databases and cloud platforms.
- Qlik Replicate (https://www.qlik.com/us/products/qlik-replicate) - Universal data replication software that provides real-time CDC capabilities for modern data architecture and analytics.


⬆ back to top (#contents)

ESB
Enterprise Service Bus (ESB) solutions facilitate the integration of disparate systems and applications by providing a communication layer that allows them to exchange information. ESBs offer a range of capabilities such as message routing, 
transformation, protocol conversion, and data mediation. They typically support various messaging patterns and communication protocols and provide a centralized platform for managing and monitoring message traffic.
- Anypoint Platform (https://www.mulesoft.com/platform/enterprise-integration) - Comprehensive integration solution that leverages robust ESB capabilities to connect and orchestrate disparate systems.
- Apache ServiceMix (https://servicemix.apache.org/) - Versatile open-source integration container combining messaging, routing, and service mediation for flexible enterprise connectivity.
- ArcESB (https://www.arcesb.com/integration/) - Flexible integration platform that synchronizes data across applications, streamlines partner connectivity, and enhances data accessibility.
- IBM App Connect (https://www.ibm.com/cloud/app-connect) - Robust integration solution that connects diverse applications and protocols, ensuring seamless data flow across the enterprise.
- IBM webMethods Integration (https://www.ibm.com/products/webmethods-integration) - Comprehensive platform that accelerates application integration and simplifies connectivity across heterogeneous systems.
- NServiceBus (⭐2.1k) (https://github.com/Particular/NServiceBus) - Developer-friendly, .NET-based service bus that simplifies messaging and orchestrates service integration efficiently.
- Oracle Service Bus (https://www.oracle.com/middleware/technologies/service-bus.html) - Powerful ESB solution that virtualizes and manages service interactions to reduce integration complexity.
- Oracle SOA Suite (https://www.oracle.com/middleware/technologies/soasuite.html) - Comprehensive SOA platform that orchestrates services into composite applications, driving efficient business process integration.
- Red Hat Fuse (https://developers.redhat.com/products/fuse/overview) - Cloud-native integration platform that delivers distributed integration capabilities for agile, scalable connectivity.
- TIBCO BusinessWorks (https://www.tibco.com/products/tibco-businessworks) - Enterprise-grade integration platform implementing proven hybrid integration patterns for reliable data exchange.
- UltraESB (https://www.adroitlogic.com/products/ultraesb/) - High-performance ESB engineered for extreme throughput with zero-copy proxying and non-blocking IO techniques.
- WSO2 Enterprise Integrator (⭐384) (https://github.com/wso2/product-ei) - API-centric, cloud-native integration platform offering robust, distributed capabilities for modern software architectures.


⬆ back to top (#contents)

ETL
ETL (Extract, Transform, Load) and ELT (Extract, Load, Transform) are processes used to integrate and consolidate data from multiple sources. This section covers a range of open source and commercial tools for performing these tasks, including 
data ingestion, transformation, and loading into data warehouses or other data storage systems.
- Apache InLong (⭐1.4k) (https://github.com/apache/inlong) - One-stop, full-scenario integration framework for massive data that supports data ingestion, synchronization, and subscription with real-time ETL capabilities.
- Apache NiFi (⭐5.4k) (https://github.com/apache/nifi) - Automated data integration tool with a visual interface that seamlessly extracts, transforms, and delivers data across systems.
- Airbyte (⭐18k) (https://github.com/airbytehq/airbyte) - Flexible, open-source data integration platform that builds ELT pipelines to move data from diverse sources to modern destinations.
- CloverDX (https://www.cloverdx.com/) - Enterprise ETL suite offering robust data transformation and workflow orchestration for scalable integration.
- Estuary Flow (⭐768) (https://github.com/estuary/flow) - Versatile, scalable platform that provides both real-time and batch data integration for ETL and ELT pipelines.
- Fivetran (https://www.fivetran.com/) - Managed ELT that syncs 700 + sources to data warehouses.
- Hevo (https://hevodata.com/) - No-code, fully automated data pipeline platform that supports extensive integrations, simplifying complex data workflows.
- IBM DataStage (https://www.ibm.com/products/datastage) - Robust platform that cleanses, transforms, and delivers reliable data, empowering businesses with trusted insights.
- Informatica PowerCenter (https://www.informatica.com/products/data-integration/powercenter.html) - Enterprise-class solution that streamlines big data and cloud analytics through comprehensive data integration management.
- Microsoft SSIS (https://docs.microsoft.com/en-us/sql/integration-services/sql-server-integration-services) - Proven data integration solution for building scalable ETL processes within enterprise environments using SQL Server.
- Oracle Data Integrator (https://www.oracle.com/middleware/technologies/data-integrator.html) - Comprehensive platform that addresses batch loads, real-time processes, and SOA-enabled services for end-to-end data management.
- Pentaho Data Integration (⭐8k) (https://github.com/pentaho/pentaho-kettle) - Intuitive, visual ETL tool that simplifies data ingestion, blending, and cleansing across multiple sources without heavy coding.
- SAS Data Management (https://www.sas.com/en_us/software/data-management.html) - Robust solution that transforms, integrates, and secures data to enhance quality and reliability across the enterprise.
- Stitch (https://www.stitchdata.com/) - Developer-friendly SaaS ETL service that effortlessly extracts data from numerous sources into data warehouses for streamlined analytics.
- Talend Data Integration (https://www.talend.com/products/integrate-data/) - Versatile platform that unifies disparate data sources into actionable insights to empower informed business decisions.


⬆ back to top (#contents)

Integration Frameworks
The Integration frameworks section includes software tools and libraries that help developers implement and manage integration patterns in their applications. These frameworks are based on well-established Enterprise Integration Patterns (EIPs), 
which provide a standard vocabulary and architecture for designing and implementing integration solutions. The frameworks in this section can help simplify the process of integrating different systems, applications, and data sources by providing 
pre-built connectors, message routing, and transformation capabilities.
- Apache Camel (⭐5.8k) (https://github.com/apache/camel) - Robust integration framework leveraging Enterprise Integration Patterns to seamlessly connect diverse systems and APIs.
- Ballerina (⭐3.7k) (https://github.com/ballerina-platform/ballerina-lang) - Innovative programming language designed for effortless creation and integration of network services and APIs.
- Frank!Framework (⭐141) (https://github.com/frankframework/frankframework) - Low-code Java messaging framework that simplifies system connectivity and data integration through configurable XML setups.
- Spring Integration (⭐1.5k) (https://github.com/spring-projects/spring-integration) - Extension of the Spring ecosystem that provides out-of-the-box integration capabilities using proven Enterprise Integration Patterns.


⬆ back to top (#contents)

iPaaS
Integration Platform as a Service (iPaaS) is a cloud-based platform that enables businesses to integrate different systems, applications, and data sources with ease. It provides a unified platform for managing data flows between various systems, 
simplifying the process of integrating different systems and automating workflows. iPaaS tools typically provide a visual interface for designing, deploying, and managing integrations, as well as pre-built connectors and APIs for integrating with
popular systems and services.
- Anypoint Platform (https://www.mulesoft.com/platform/saas/cloudhub-ipaas-cloud-based-integration) - Combines API management and integration into one platform, enabling seamless connectivity across diverse applications.
- Boomi AtomSphere (https://boomi.com/platform) - Cloud-native, intelligent platform that connects systems effortlessly while automating integration processes.
- Celigo Integration Platform (https://www.celigo.com/platform/) - User-friendly iPaaS with prebuilt templates for rapid SaaS-to-SaaS integrations and intuitive drag-and-drop design.
- Jitterbit Harmony (https://www.jitterbit.com/platform/ipaas) - Comprehensive integration solution offering prebuilt workflows and automation templates to accelerate business processes.
- IBM Cloud Integration (https://www.ibm.com/cloud/integration) - Next-generation platform leveraging AI to streamline integration, increase scalability, and speed up deployment.
- IBM webMethods (https://www.ibm.com/products/webmethods) - All-in-one integration platform that unifies applications, simplifies processes, and boosts overall efficiency.
- Informatica Intelligent Cloud Services (https://www.informatica.com/products/cloud-integration.html) - Suite of cloud data management tools that accelerates productivity and simplifies application and data integration.
- OpenText Alloy (https://businessnetwork.opentext.com/enterprise-data-management/) - Enterprise data management solution that transforms basic integration into actionable insights and smarter decision-making.
- Oracle Integration Cloud Service (https://www.oracle.com/integration/application-integration/) - Robust platform with prebuilt connectivity for both SaaS and on-premises apps, streamlining integration processes.
- SAP Integration Suite (https://www.sap.com/products/technology-platform/integration-suite.html) - Cloud-native solution offering prebuilt adapters, API management, and event brokering for end-to-end connectivity.
- SnapLogic Intelligent Integration Platform (https://www.snaplogic.com/products/intelligent-integration-platform) - AI-driven platform that connects applications and data rapidly, ensuring efficient and scalable integrations.
- TIBCO Cloud Integration (https://docs.tibco.com/products/tibco-cloud-integration-ipaas) - Flexible, API-led and event-driven platform that empowers you to integrate virtually any system quickly.
- Tray.io (https://tray.ai/) - Low-code automation platform with a drag-and-drop interface, making it simple to build scalable integrations and workflows.
- Workato (https://www.workato.com/) - Unified integration and workflow automation solution that simplifies complex processes and enhances operational efficiency.


⬆ back to top (#contents)

MaaS
Cloud Messaging as a Service (MaaS) refers to cloud-based messaging platforms that enable reliable, secure, and scalable communication between distributed applications and services. These platforms provide various messaging patterns such as 
publish-subscribe, request-reply, and streaming. They also offer features such as message routing, filtering, transformation, and persistence, and support various protocols and APIs for integration with different systems.
- Amazon MQ (https://aws.amazon.com/amazon-mq) - Fully managed message broker supporting Apache ActiveMQ and RabbitMQ, ensuring reliable and secure messaging.
- Amazon MSK (https://aws.amazon.com/msk) - Managed Apache Kafka service that simplifies cluster setup, scaling, and real-time data streaming.
- Amazon SQS (https://aws.amazon.com/sqs) - Reliable, fully managed queuing service to decouple microservices and scale distributed applications seamlessly.
- Amazon SNS (https://aws.amazon.com/sns) - Managed pub/sub messaging service that flexibly notifies subscribers and supports various delivery protocols.
- Alibaba Cloud Message Queue for Apache Kafka (https://www.alibabacloud.com/product/kafka) - High-throughput Kafka service with seamless Alibaba Cloud integration for real-time data processing.
- Alibaba Cloud Message Queue for RabbitMQ (https://www.alibabacloud.com/product/rabbitmq) - Scalable RabbitMQ solution offering low latency and high throughput for distributed messaging.
- Alibaba Cloud Message Service (https://www.alibabacloud.com/product/message-service) - Distributed messaging service that ensures reliable data transfer between decoupled systems.
- AlibabaMQ for Apache RocketMQ (https://www.alibabacloud.com/product/mq) - Robust message queue service supporting asynchronous communication with high availability and durability.
- Anypoint MQ (https://www.mulesoft.com/platform/anypoint-mq-message-queue) - Enterprise-class messaging service integrated with Anypoint Platform for flexible and reliable message orchestration.
- Azure Event Hubs (https://azure.microsoft.com/en-us/products/event-hubs/) - A high-throughput, fully managed event-ingestion (publish-subscribe) service, supports the Kafka protocol natively.
- Azure Service Bus (https://azure.microsoft.com/en-us/services/service-bus/) - Cloud messaging solution that supports multiple patterns and protocols for robust enterprise integration.
- CloudAMQP (https://www.cloudamqp.com/) - Managed RabbitMQ service featuring an intuitive web console, advanced analytics, and seamless scalability.
- Confluent Cloud (https://www.confluent.io/confluent-cloud/) - Fully managed Kafka service offering enterprise features like schema registry, connectors, and governance.
- Google Cloud Managed Service for Apache Kafka (https://cloud.google.com/products/managed-service-for-apache-kafka) - Simplifies Kafka deployment and management on Google Cloud for real-time streaming applications.
- Google Cloud Pub/Sub (https://cloud.google.com/pubsub) - High-throughput messaging service that supports event-driven architectures with flexible delivery models.
- Huawei Cloud Distributed Message Service (https://www.huaweicloud.com/intl/en-us/product/dms.html) - Fully managed messaging service that ensures secure, scalable, and reliable communication between applications.
- Huawei Cloud Distributed Message Service for Kafka (https://www.huaweicloud.com/intl/en-us/product/dmskafka.html) - Managed Kafka solution that simplifies scaling and management while delivering high performance and security.
- IBM MQ on Cloud (https://www.ibm.com/cloud/mq) - Enterprise messaging service that offers secure, reliable data transfer across applications in a cloud environment.
- IronMQ (https://www.iron.io/mq) - Elastic, cloud-native message queue designed for scalable and reliable processing of high-volume messages.
- Oracle Cloud Streaming (https://www.oracle.com/cloud/cloud-native/streaming/) - Serverless, real-time event streaming platform with Apache Kafka compatibility for efficient data processing.
- Solace PubSub+ Cloud (https://solace.com/products/platform/cloud/) - Integrated event streaming platform providing full visibility and control over your data pipelines.
- Yandex Message Queue (https://cloud.yandex.com/en/services/message-queue) - Cloud messaging service compatible with Amazon SQS API for easy integration with existing systems.
- Yandex Managed Service for Apache Kafka (https://cloud.yandex.com/en/services/managed-kafka) - Fully managed Kafka service with automated scaling, monitoring, and maintenance for hassle-free streaming.


⬆ back to top (#contents)

MFT
Managed File Transfer (MFT) solutions provide secure and reliable file transfer capabilities that help organizations meet regulatory compliance requirements, improve operational efficiency, and reduce the risk of data breaches. MFT software 
typically includes features such as encryption, digital signatures, user access controls, and detailed audit logs to ensure that data is transmitted securely and can be tracked throughout the transfer process.
- ArcESB Managed File Transfer (https://www.arcesb.com/mft/) - Enterprise-grade MFT solution with an intuitive interface and powerful automation for streamlined file exchanges.
- Axway Managed File Transfer (https://www.axway.com/en/products/managed-file-transfer) - Robust platform offering advanced security and efficient, reliable data transfer across enterprise systems.
- GoAnywhere MFT (https://www.goanywhere.com/products/goanywhere-mft) - Comprehensive solution delivering centralized, secure file transfers with automation and complete audit logging.
- GlobalSCAPE EFT (https://www.globalscape.com/eft) - Hardened file transfer server that ensures end-to-end encryption, automation, and compliance for mission-critical data.
- IBM Sterling Secure File Transfer (https://www.ibm.com/products/secure-file-transfer) - Scalable and high-performance MFT platform designed for secure, fast, and reliable file exchange.
- IBM webMethods MFT (https://www.ibm.com/products/webmethods-mft) - Integrated managed file transfer solution that supports flexible deployment across hybrid environments.
- JSCAPE MFT Server (https://www.jscape.com/products/file-transfer-servers/jscape-mft-server) - Secure, protocol-agnostic platform with automation and compliance.
- Oracle Managed File Transfer (https://www.oracle.com/middleware/technologies/mft/managed-file-transfer.html) - Comprehensive platform that simplifies secure file exchange and management for enterprise operations.
- Progress MOVEit (https://www.progress.com/moveit) - Secure, automated file transfer solution with guaranteed delivery, encryption, and compliance tools for regulated industries.
- TIBCO Managed File Transfer (https://www.tibco.com/products/tibco-managed-file-transfer) - Centralized MFT platform with robust automation and security features designed to support diverse file transfer scenarios.
- Titan MFT Server (https://southrivertech.com/titan-mft-server/) - Enterprise-level MFT server offering high availability, failover capabilities, and efficient large-scale file automation.


⬆ back to top (#contents)

MDM
Master Data Management (MDM) solutions help organizations create a single, authoritative source of accurate and consistent data across different systems, applications, and departments. These tools provide capabilities for data profiling, 
cleansing, enrichment, and governance, enabling organizations to improve data quality, reduce errors, and increase operational efficiency.
- IBM InfoSphere Master Data Management (https://www.ibm.com/products/ibm-infosphere-master-data-management) - Comprehensive platform that centralizes data governance, ensuring consistency and accuracy across your enterprise.
- Informatica Multidomain MDM (https://www.informatica.com/products/master-data-management/multidomain-mdm.html) - Integrated solution for managing and governing master data across all domains, enhancing overall data quality.
- Oracle Enterprise Data Management (https://www.oracle.com/performance-management/enterprise-data-management/) - Robust tool that centralizes master data to support faster, more effective decision-making and operational agility.
- Reltio (https://www.reltio.com/products/multidomain-mdm) - Cloud-native, multi-domain MDM platform combining data quality, governance, and real-time analytics for a 360° view.
- SAP Master Data Governance (https://www.sap.com/products/master-data-governance.html) - Centralized solution that consolidates and governs master data to ensure consistency and high quality.
- SAS MDM (https://support.sas.com/en/software/mdm-support.html) - Unified platform that integrates data from diverse sources into accurate master records for improved efficiency.
- Stibo MDM (https://www.stibosystems.com/platform) - Proven multi-domain MDM solution focusing on data transparency and governance to provide a single source of truth.
- Teradata MDM (https://www.teradata.co.uk/Products/Applications/Master-Data-Management) - Establishes a consistent analytical foundation by maintaining accurate reference data for enhanced ROI.
- TIBCO EBX (https://www.tibco.com/products/ebx) - Comprehensive platform for governing and managing shared data assets, ensuring consistency and enabling smarter decisions.


⬆ back to top (#contents)

Messaging
Message brokers are a type of middleware that allows communication between different applications or systems by facilitating the exchange of messages. They can handle different messaging patterns, such as point-to-point, publish-subscribe, and 
request-reply, and provide features such as message transformation, routing, and filtering.
- Apache ActiveMQ (⭐2.3k) (https://github.com/apache/activemq) - Open-source broker that implements JMS, enabling seamless conversion between synchronous and asynchronous messaging.
- Apache ActiveMQ Artemis (⭐973) (https://github.com/apache/activemq-artemis) - Next-generation message broker from Apache ActiveMQ with high performance, clustering support, and multi-protocol capabilities.
- Apache Kafka (⭐30k) (https://github.com/apache/kafka) - Distributed, high-throughput system designed for real-time data streaming and fault-tolerant processing.
- Apache Pulsar (⭐14k) (https://github.com/apache/pulsar) - Versatile pub/sub and streaming platform offering scalable, low-latency messaging for modern applications.
- Apache RocketMQ (⭐21k) (https://github.com/apache/rocketmq) - High-performance distributed messaging platform engineered for low latency and high throughput.
- Apache Qpid (⭐59) (https://github.com/apache/qpid-broker-j) - AMQP-compliant messaging tool with multi-language support for enterprise-grade message delivery.
- BlazingMQ (⭐2.6k) (https://github.com/bloomberg/blazingmq) - Distributed message queuing system focused on efficiency and reliability for modern workflow needs.
- Centrifugo (⭐9k) (https://github.com/centrifugal/centrifugo) - Scalable real-time messaging server that minimizes delay in delivering events to online users.
- Eclipse Mosquitto (⭐9.8k) (https://github.com/eclipse/mosquitto) - Lightweight MQTT broker optimized for low-power devices with robust encryption and authentication.
- EMQX (⭐15k) (https://github.com/emqx/emqx) - High-performance MQTT broker built for IoT and industrial applications, ensuring scalable message delivery.
- IBM MQ (https://www.ibm.com/products/mq) - Enterprise-grade messaging solution providing robust features, high availability, and multi-protocol support.
- KubeMQ (https://kubemq.io/) - Kubernetes-native message broker and queue system designed for scalability, high availability, and seamless cloud integration.
- LavinMQ (⭐749) (https://github.com/cloudamqp/lavinmq) - High-performance message queue server implementing AMQP 0-9-1 and MQTT protocols, built with Crystal for exceptional throughput and minimal resource usage.
- NATS (⭐17k) (https://github.com/nats-io/gnatsd) - Lightweight, high-performance messaging system ideal for microservices and cloud-native architectures.
- NSQ (⭐25k) (https://github.com/nsqio/nsq) - Realtime distributed messaging platform designed to operate at scale, handling billions of messages per day with decentralized topology.
- Oracle AQ (https://www.oracle.com/database/technologies/advanced-queuing.html) - Integrated messaging solution within Oracle databases, offering reliable and efficient message delivery.
- RabbitMQ (⭐12k) (https://github.com/rabbitmq/rabbitmq-server) - Popular open-source broker implementing AMQP, known for reliability, clustering, and ease-of-use.
- Redpanda (⭐10k) (https://github.com/vectorizedio/redpanda) - Kafka-compatible streaming platform that eliminates Zookeeper, delivering high performance and low latency.
- Red Hat AMQ (https://www.redhat.com/en/technologies/jboss-middleware/amq) - Enterprise messaging platform based on open-source technologies, offering scalable and reliable message delivery.
- TIBCO Enterprise Message Service (https://www.tibco.com/products/tibco-enterprise-message-service) - Standards-based JMS implementation that enables efficient and robust exchange of messages between applications.
- VerneMQ (⭐3.3k) (https://github.com/vernemq/vernemq) - High-performance distributed MQTT broker designed for scalable and efficient message delivery in modern environments.


⬆ back to top (#contents)

RPA
Robotic Process Automation (RPA) solutions are software tools that automate repetitive, rule-based tasks within business processes. RPA bots can perform tasks such as data entry, data extraction, and data processing with accuracy and speed, 
freeing up human workers to focus on more complex tasks.
- Automation Anywhere (https://www.automationanywhere.com/) - Intelligent automation ecosystem that streamlines business processes and reduces errors through advanced RPA capabilities.
- Blue Prism (https://www.blueprism.com/products/intelligent-rpa-automation/) - No-code platform delivering robust, scalable automation to minimize manual tasks and boost productivity.
- OpenRPA (⭐2.6k) (https://github.com/open-rpa/openrpa) - Enterprise-grade, open-source robotic process automation suite. 
- Robot Framework (⭐10k) (https://github.com/robotframework/robotframework) - An open-source automation framework with human-friendly keyword syntax that enables both technical and non-technical users to create test scripts and automate business
processes cost-effectively, supporting web, API, mobile, and database automation through extensive libraries and integrations.
- TagUI (⭐6k) (https://github.com/aisingapore/TagUI) - An open-source RPA tool that democratizes automation through natural language scripting in 20+ human languages, enabling non-programmers to automate web, desktop, and data tasks while 
integrating AI/ML capabilities via Python and R for intelligent process automation.
- Tungsten RPA (https://www.tungstenautomation.com/products/rpa) - AI-powered, no-code automation solution that enhances accuracy, efficiency, and compliance across workflows.
- UiPath (https://www.uipath.com/product) - Comprehensive RPA platform that automates routine tasks, enabling scalable digital transformation across enterprises.
- WorkFusion (https://www.workfusion.com/platform/) - Enterprise automation solution that combines RPA with intelligent automation to streamline complex workflows.


⬆ back to top (#contents)

Self-Service Integration
Self-service and citizen integrator tools are designed to enable non-technical users to build integrations without the need for extensive programming knowledge. These tools typically feature drag-and-drop interfaces and pre-built connectors for 
popular applications and services.

- IFTTT (https://ifttt.com/) - Easy-to-use platform that connects web services with simple conditional statements, empowering custom workflow creation.
- Make (Integromat) (https://www.make.com) - Low-code automation tool with a visual interface, advanced data transformation, and modular workflow execution.
- Microsoft Power Automate (https://powerautomate.microsoft.com) - Cloud-based service with an intuitive interface for creating automated workflows that seamlessly integrate diverse apps.
- n8n (⭐116k) (https://github.com/n8n-io/n8n) - Open-source workflow automation tool with 400+ connectors, giving you full control over your data and integrations.
- Oracle Self-Service Integration (https://docs.oracle.com/en/cloud/paas/self-service-integration-cloud/index.html) - Streamlined tool that automates tasks between cloud applications, making integration accessible for non-developers.
- Zapier (https://zapier.com/) - Intuitive platform that connects hundreds of web services to create efficient, code-free automations.


⬆ back to top (#contents)

Workflow engine
Software tools that enable the design, execution, and monitoring of complex workflows or business processes. Workflow engines provide a way to automate and streamline business processes, while orchestration engines help to manage the interactions
between different systems or services.
- Activiti (⭐10k) (https://github.com/Activiti/Activiti) - Lightweight, Java-centric BPMN engine that efficiently executes business workflows with a focus on simplicity.
- Apache Airflow (⭐40k) (https://github.com/apache/airflow) - Platform for programmatically creating, scheduling, and monitoring workflows, ideal for managing complex data pipelines.
- Argo Workflows (⭐15k) (https://github.com/argoproj/argo-workflows) - Container-native workflow engine designed for orchestrating parallel jobs in Kubernetes-based, cloud-native environments.
- Azkaban (⭐4.5k) (https://github.com/azkaban/azkaban) - Distributed scheduler that simplifies managing job dependencies in large-scale data processing environments.
- Bonita (⭐167) (https://github.com/bonitasoft/bonita-engine) - Open-source BPMN engine with a designer interface to build and automate complex business processes.
- Cadence (⭐8.7k) (https://github.com/uber/cadence) - Fault-tolerant, stateful platform that reliably orchestrates long-running workflows and complex applications.
- Camunda (⭐4.2k) (https://github.com/camunda/camunda-bpm-platform) - Flexible workflow and decision automation platform designed for scalable business process management.
- Conductor (⭐12k) (https://github.com/Netflix/conductor) - Cloud-based orchestration engine that manages microservices workflows, streamlining complex process automation.
- Elsa Core (⭐7.1k) (https://github.com/elsa-workflows/elsa-core) - .NET Core library that integrates seamlessly into any application to execute and manage workflows.
- Flowable (⭐8.5k) (https://github.com/flowable/flowable-engine) - Compact, efficient set of open-source engines for automating and scaling enterprise workflows.
- jBPM (⭐1.6k) (https://github.com/kiegroup/jbpm) - Comprehensive toolkit for automating business processes and decisions with robust workflow management capabilities.
- Prefect (⭐19k) (https://github.com/PrefectHQ/prefect) - Modern, developer-friendly orchestration tool optimized for data pipelines and complex workflows.
- StackStorm (⭐6.2k) (https://github.com/StackStorm/st2) - Robust automation engine that combines sensors, triggers, and workflows to orchestrate complex IT processes.
- Temporal (⭐14k) (https://github.com/temporalio/temporal) - Open-source workflow-as-code platform designed for building reliable, scalable, and fault-tolerant applications. 


⬆ back to top (#contents)

Integration Patterns
Integration patterns provide standardized solutions for common integration problems within an enterprise. Enterprise Integration Patterns (EIP) provide a common language for describing integration problems and solutions, while Integration 
Architecture Patterns address high-level concerns of enterprise architects. Service-Oriented Architecture (SOA) patterns provide guidance for designing and implementing service-oriented architectures, ensuring that services are scalable, 
reusable, and loosely coupled.
Enterprise Integration Patterns
Patterns from a book by Gregor Hohpe and Bobby Woolf.
- Aggregator (https://www.enterpriseintegrationpatterns.com/patterns/messaging/Aggregator.html) - How do we combine the results of individual, but related messages so that they can be processed as a whole?  
- Canonical Data Model (https://www.enterpriseintegrationpatterns.com/patterns/messaging/CanonicalDataModel.html) - How can you minimize dependencies when integrating applications that use different data formats?
- Channel Adapter (https://www.enterpriseintegrationpatterns.com/patterns/messaging/ChannelAdapter.html) - How can you connect an application to the messaging system so that it can send and receive messages?
- Channel Purger (https://www.enterpriseintegrationpatterns.com/patterns/messaging/ChannelPurger.html) - How can you keep 'left-over' messages on a channel from disturbing tests or running systems?
- Claim Check (https://www.enterpriseintegrationpatterns.com/patterns/messaging/StoreInLibrary.html) - How can we reduce the data volume of message sent across the system without sacrificing information content?  
- Command Message (https://www.enterpriseintegrationpatterns.com/patterns/messaging/CommandMessage.html) - How can messaging be used to invoke a procedure in another application?  
- Competing Consumers (https://www.enterpriseintegrationpatterns.com/patterns/messaging/CompetingConsumers.html) - How can a messaging client process multiple messages concurrently?
- Composed Message Processor (https://www.enterpriseintegrationpatterns.com/patterns/messaging/DistributionAggregate.html) - How can you maintain the overall message flow when processing a message consisting of multiple elements, each of which 
may require different processing?  
- Content Enricher (https://www.enterpriseintegrationpatterns.com/patterns/messaging/DataEnricher.html) - How do we communicate with another system if the message originator does not have all the required data items available?  
- Content Filter (https://www.enterpriseintegrationpatterns.com/patterns/messaging/ContentFilter.html) - How do you simplify dealing with a large message, when you are interested only in a few data items?  
- Content-Based Router (https://www.enterpriseintegrationpatterns.com/patterns/messaging/ContentBasedRouter.html) - How do we handle a situation where the implementation of a single logical function (e.g., inventory check) is spread across 
multiple physical systems?  
- Control Bus (https://www.enterpriseintegrationpatterns.com/patterns/messaging/ControlBus.html) - How can we effectively administer a messaging system that is distributed across multiple platforms and a wide geographic area?  
- Correlation Identifier (https://www.enterpriseintegrationpatterns.com/patterns/messaging/CorrelationIdentifier.html) - How does a requestor that has received a reply know which request this is the reply for?
- Datatype Channel (https://www.enterpriseintegrationpatterns.com/patterns/messaging/DatatypeChannel.html) - How can the application send a data item such that the receiver will know how to process it?
- Dead Letter Channel (https://www.enterpriseintegrationpatterns.com/patterns/messaging/DeadLetterChannel.html) - What will the messaging system do with a message it cannot deliver?  
- Detour (https://www.enterpriseintegrationpatterns.com/patterns/messaging/Detour.html) - How can you route a message through intermediate steps to perform validation, testing or debugging functions?
- Document Message (https://www.enterpriseintegrationpatterns.com/patterns/messaging/DocumentMessage.html) - How can messaging be used to transfer data between applications?
- Durable Subscriber (https://www.enterpriseintegrationpatterns.com/patterns/messaging/DurableSubscription.html) - How can a subscriber avoid missing messages while it is not listening for them?
- Dynamic Router (https://www.enterpriseintegrationpatterns.com/patterns/messaging/DynamicRouter.html) - How can you avoid the dependency of the router on all possible destinations while maintaining its efficiency?
- Envelope Wrapper (https://www.enterpriseintegrationpatterns.com/patterns/messaging/EnvelopeWrapper.html) - How can existing systems participate in a messaging exchange that places specific requirements on the message format, such as message 
header fields or encryption?  
- Event Message (https://www.enterpriseintegrationpatterns.com/patterns/messaging/EventMessage.html) - How can messaging be used to transmit events from one application to another?
- Event-Driven Consumer (https://www.enterpriseintegrationpatterns.com/patterns/messaging/EventDrivenConsumer.html) - How can an application automatically consume messages as they become available?
- Format Indicator (https://www.enterpriseintegrationpatterns.com/patterns/messaging/FormatIndicator.html) - How can a messages data format be designed to allow for possible future changes?
- Guaranteed Delivery (https://www.enterpriseintegrationpatterns.com/patterns/messaging/GuaranteedMessaging.html) - How can the sender make sure that a message will be delivered, even if the messaging system fails?
- Idempotent Receiver (https://www.enterpriseintegrationpatterns.com/patterns/messaging/IdempotentReceiver.html) - How can a message receiver deal with duplicate messages?
- Invalid Message Channel (https://www.enterpriseintegrationpatterns.com/patterns/messaging/InvalidMessageChannel.html) - How can a messaging receiver gracefully handle receiving a message that makes no sense?
- Message (https://www.enterpriseintegrationpatterns.com/patterns/messaging/Message.html) - How can two applications connected by a message channel exchange a piece of information?
- Message Dispatcher (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageDispatcher.html) - How can multiple consumers on a single channel coordinate their message processing?
- Message Expiration (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageExpiration.html) - How can a sender indicate when a message should be considered stale and thus shouldnt be processed?
- Message Translator (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageTranslator.html) - How can systems using different data formats communicate with each other using messaging?  
- Message Broker (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageBroker.html) - How can you decouple the destination of a message from the sender and maintain central control over the flow of messages?
- Message Bus (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageBus.html) - What is an architecture that enables separate applications to work together, but in a decoupled fashion such that applications can be easily added 
or removed without affecting the others?  
- Message Channel (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageChannel.html) - How does one application communicate with another using messaging?
- Message Endpoint (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageEndpoint.html) - How does an application connect to a messaging channel to send and receive messages?
- Message Filter (https://www.enterpriseintegrationpatterns.com/patterns/messaging/Filter.html) - How can a component avoid receiving uninteresting messages?
- Message History (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageHistory.html) - How can we effectively analyze and debug the flow of messages in a loosely coupled system?  
- Message Router (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageRouter.html) - How can you decouple individual processing steps so that messages can be passed to different filters depending on a set of conditions?
- Message Sequence (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageSequence.html) - How can messaging transmit an arbitrarily large amount of data?
- Message Store (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageStore.html) - How can we report against message information without disturbing the loosely coupled and transient nature of a messaging system?  
- Messaging Bridge (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessagingBridge.html) - How can multiple messaging systems be connected so that messages available on one are also available on the others?
- Messaging Gateway (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessagingGateway.html) - How do you encapsulate access to the messaging system from the rest of the application?
- Messaging Mapper (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessagingMapper.html) - How do you move data between domain objects and the messaging infrastructure while keeping the two independent of each other?
- Normalizer (https://www.enterpriseintegrationpatterns.com/patterns/messaging/Normalizer.html) - How do you process messages that are semantically equivalent, but arrive in a different format?
- Pipes and Filters (https://www.enterpriseintegrationpatterns.com/patterns/messaging/PipesAndFilters.html) - How can we perform complex processing on a message while maintaining independence and flexibility?  
- Point-to-Point Channel (https://www.enterpriseintegrationpatterns.com/patterns/messaging/PointToPointChannel.html) - How can the caller be sure that exactly one receiver will receive the document or perform the call?
- Polling Consumer (https://www.enterpriseintegrationpatterns.com/patterns/messaging/PollingConsumer.html) - How can an application consume a message when the application is ready?  
- Process Manager (https://www.enterpriseintegrationpatterns.com/patterns/messaging/ProcessManager.html) - How do we route a message through multiple processing steps when the required steps may not be known at design-time and may not be 
sequential?
- Publish-Subscribe Channel (https://www.enterpriseintegrationpatterns.com/patterns/messaging/PublishSubscribeChannel.html) - How can the sender broadcast an event to all interested receivers?
- Recipient List (https://www.enterpriseintegrationpatterns.com/patterns/messaging/RecipientList.html) - How do we route a message to a list of dynamically specified recipients?
- Request-Reply (https://www.enterpriseintegrationpatterns.com/patterns/messaging/RequestReply.html) - When an application sends a message, how can it get a response from the receiver?
- Resequencer (https://www.enterpriseintegrationpatterns.com/patterns/messaging/Resequencer.html) - How can we get a stream of related but out-of-sequence messages back into the correct order?
- Return Address (https://www.enterpriseintegrationpatterns.com/patterns/messaging/ReturnAddress.html) - How does a replier know where to send the reply?
- Routing Slip (https://www.enterpriseintegrationpatterns.com/patterns/messaging/RoutingTable.html) - How do we route a message consecutively through a series of processing steps when the sequence of steps is not known at design-time and may vary
for each message?  
- Scatter-Gather (https://www.enterpriseintegrationpatterns.com/patterns/messaging/BroadcastAggregate.html) - How do you maintain the overall message flow when a message needs to be sent to multiple recipients, each of which may send a reply?  
- Selective Consumer (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageSelector.html) - How can a message consumer select which messages it wishes to receive?  
- Service Activator (https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessagingAdapter.html) - How can an application design a service to be invoked both via various messaging technologies and via non-messaging techniques?
- Smart Proxy (https://www.enterpriseintegrationpatterns.com/patterns/messaging/SmartProxy.html) - How can you track messages on a service that publishes reply messages to the Return Address specified by the requestor?
- Splitter (https://www.enterpriseintegrationpatterns.com/patterns/messaging/Sequencer.html) - How can we process a message if it contains multiple elements, each of which may have to be processed in a different way?  
- Test Message (https://www.enterpriseintegrationpatterns.com/patterns/messaging/TestMessage.html) - What happens, though, if a component is actively processing messages, but garbles outgoing messages due to an internal fault?  
- Transactional Client (https://www.enterpriseintegrationpatterns.com/patterns/messaging/TransactionalClient.html) - How can a client control its transactions with the messaging system?  
- Wire Tap (https://www.enterpriseintegrationpatterns.com/patterns/messaging/WireTap.html) - How do you inspect messages that travel on a point-to-point channel?  


⬆ back to top (#contents)

Integration Architecture Patterns
Design patterns used to connect systems and applications in an efficient and seamless manner.
- API-led Connectivity pattern (https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/API-led-Connectivity-Pattern.md) - Use APIs to connect different systems and applications.
- Anti Corruption Layer Pattern (https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Anti-Corruption-Layer-Pattern.md) - Add a layer to isolate and transform data between systems.
- Change Data Capture Pattern (https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Introduction-to-Change-Data-Capture.md) - Capture and propagate changes made to a database or data source in real-time.
- Hybrid API Management pattern (https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Hybrid-API-Management-Pattern.md) - Manage APIs that span both cloud and on-premises environments using a central control 
plane.
- Hybrid Integration pattern (https://github.com/chanakaudaya/solution-architecture-patterns/blob/master/vendor-neutral/Hybrid-Integration-Pattern.md) - Integrate systems and applications that are deployed both on-premises and in the cloud using 
a combination of integration technologies.


⬆ back to top (#contents)

Microservice API Patterns
MAP (Microservice API Patterns) is a set of proven solutions to common problems encountered when designing, implementing, and maintaining message-based APIs. It focuses on the message representations or payloads exchanged during API calls and 
their impact on the design and runtime qualities of an API. Proper governance of API specifications and implementations is essential for their long-term maintenance.
- Foundation
- **Frontend Integration** (https://microservice-api-patterns.org/patterns/foundation/FrontendIntegration) - How can client-side end-user interfaces that are physically separated from server-side business logic and data storage be populated and u                                                                                                                                                                                                          
pdated with computing results, result sets from searches in data sources, and detailed information about data entities? How can application frontends invoke activities in a backend or upload data to it?                                                                                                                                                                                                                                                      
- **Backend Integration** (https://microservice-api-patterns.org/patterns/foundation/BackendIntegration) - How can distributed applications and their parts, which have been built independently and are deployed separately, exchange data and trigge                                                                                                                                                                                                          
r mutual activity while preserving system-internal conceptual integrity without introducing undesired coupling?                                                                                                                                                                                                                                                                                                                                                 
- **Public API** (https://microservice-api-patterns.org/patterns/foundation/PublicAPI) - 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 regional                                                                                                                                                                                                          
ly distributed?                                                                                                                                                                                                                                                                                                                                                                                                                                                 
- **Community API** (https://microservice-api-patterns.org/patterns/foundation/CommunityAPI) - 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 mul                                                                                                                                                                                                          
tiple legal entities (such as companies, nonprofit/nongovernment organizations, and governments)?                                                                                                                                                                                                                                                                                                                                                               
- **Solution-Internal API** (https://microservice-api-patterns.org/patterns/foundation/SolutionInternalAPI) - 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?                                                                                                                                                                                                                                                                                                                                                                                                                                                 
- **API Description** (https://microservice-api-patterns.org/patterns/foundation/APIDescription) - Which knowledge should be shared between an API provider and its clients? How should this knowledge be documented?                                                                                                                                                                                                                                           

- Responsibility
- Endpoint Roles                                                                                                                                                                                                                                                                                                                                                                                                        
    - **Processing Resource** (https://microservice-api-patterns.org/patterns/responsibility/endpointRoles/ProcessingResource) - How can an API provider allow its clients to trigger an action in it?                                                                                                                                                                                                                  
    - **Information Holder Resource** (https://microservice-api-patterns.org/patterns/responsibility/endpointRoles/InformationHolderResource) - How can domain data be exposed in an API, but its implementation still be hidden? How can an API expos                                                                                                                                                                  
e data entities so that API clients can access and/or modify these entities concurrently without compromising data integrity and quality?                                                                                                                                                                                                                                                                               
- Operation Responsibilities                                                                                                                                                                                                                                                                                                                                                                                            
    - **State Creation Operation** (https://microservice-api-patterns.org/patterns/responsibility/operationResponsibilities/StateCreationOperation) - How can an API provider allow its clients to report that something has happened that the provide                                                                                                                                                                  
r needs to know about, for instance, to trigger instant or later processing?                                                                                                                                                                                                                                                                                                                                            
    - **Retrieval Operation** (https://microservice-api-patterns.org/patterns/responsibility/operationResponsibilities/RetrievalOperation) - How can information available from a remote party (the API provider, that is) be retrieved to satisfy an                                                                                                                                                                   
information need of an end user or to allow further client-side processing?                                                                                                                                                                                                                                                                                                                                             
    - **State Transition Operation** (https://microservice-api-patterns.org/patterns/responsibility/operationResponsibilities/StateTransitionOperation) - How can a client initiate a processing action that causes the provider-side application stat                                                                                                                                                                  
e to change? How can API clients and API providers share the responsibilities required to execute and control business processes and their activities?                                                                                                                                                                                                                                                                  
    - **Computation Function** (https://microservice-api-patterns.org/patterns/responsibility/operationResponsibilities/ComputationFunction) - How can a client invoke side-effect-free remote processing on the provider side to have a result calcul                                                                                                                                                                  
ated from its input?                                                                                                                                                                                                                                                                                                                                                                                                    
- Information Holder Types                                                                                                                                                                                                                                                                                                                                                                                              
    - **Operational Data Holder** (https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpointTypes/OperationalDataHolder) - 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** (https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpointTypes/MasterDataHolder) - 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?                                                                                                                                                                                                                                                                                                                                                                  
    - **Reference Data Holder** (https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpointTypes/ReferenceDataHolder) - How should data that is referenced in many places, lives long, and is immutable for clients be tr                                                                                                                                                                  
eated in API endpoints? How can such reference data be used in requests to and responses from Processing Resources or Information Holder Resources?                                                                                                                                                                                                                                                                     
    - **Link Lookup Resource** (https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpointTypes/LinkLookupResource) - How can message representations refer to other, possibly many and frequently changing, API endpoint                                                                                                                                                                  
s and operations without binding the message recipient to the actual addresses of these endpoints?                                                                                                                                                                                                                                                                                                                      
    - **Data Transfer Resource** (https://microservice-api-patterns.org/patterns/responsibility/informationHolderEndpointTypes/DataTransferResource) - How can two or more communication participants exchange data without knowing each other, withou                                                                                                                                                                  
t being available at the same time, and even if the data has already been sent before its recipients became known?                                                                                                                                                                                                                                                                                                      
- Structure
- Representation Elements                                                                                                                                                                                                                                                                                                                                                                             
    - **Atomic Parameter** (https://microservice-api-patterns.org/patterns/structure/representationElements/AtomicParameter) - How can simple, unstructured data (such as a number, a string, a Boolean value, or a block of binary data) be exchanged                                                                                                                                                
 between API client and API provider?                                                                                                                                                                                                                                                                                                                                                                 
    - **Atomic Parameter List** (https://microservice-api-patterns.org/patterns/structure/representationElements/AtomicParameterList) - How can multiple related Atomic Parameters be combined in a representation element so that each of them stays                                                                                                                                                 
simple, but their relatedness becomes explicit in the API Description and the runtime message exchanges?                                                                                                                                                                                                                                                                                              
    - **Parameter Tree** (https://microservice-api-patterns.org/patterns/structure/representationElements/ParameterTree) - How can containment relationships be expressed when defining complex representation elements and exchanging such related el                                                                                                                                                
ements at runtime?                                                                                                                                                                                                                                                                                                                                                                                    
    - **Parameter Forest** (https://microservice-api-patterns.org/patterns/structure/representationElements/ParameterForest) - How can multiple Parameter Trees be exposed as request or response payload of an API operation?                                                                                                                                                                        
- Element Stereotypes                                                                                                                                                                                                                                                                                                                                                                                 
    - **Data Element** (https://microservice-api-patterns.org/patterns/structure/elementStereotypes/DataElement) - How can domain/application-level information be exchanged between API clients and API providers without exposing provider-internal                                                                                                                                                 
data definitions in the API? How can API client and API provider be decoupled from a data management point of view?                                                                                                                                                                                                                                                                                   
    - **Metadata Element** (https://microservice-api-patterns.org/patterns/structure/elementStereotypes/MetadataElement) - How can messages be enriched with additional information so that receivers can interpret the message content correctly, wit                                                                                                                                                
hout having to hardcode assumptions about the data semantics?                                                                                                                                                                                                                                                                                                                                         
    - **Id Element** (https://microservice-api-patterns.org/patterns/structure/elementStereotypes/IdElement) - How can API elements be distinguished from each other at design time and at runtime? When applying domain-driven design, how can elemen                                                                                                                                                
ts of the Published Language be identified?                                                                                                                                                                                                                                                                                                                                                           
    - **Link Element** (https://microservice-api-patterns.org/patterns/structure/elementStereotypes/LinkElement) - How can API endpoints and operations be referenced in request and response message payloads so that they can be called remotely?                                                                                                                                                   
- Special Purpose Representations                                                                                                                                                                                                                                                                                                                                                                     
    - **API Key** (https://microservice-api-patterns.org/patterns/structure/specialPurposeRepresentations/APIKey) - How can an API provider identify and authenticate clients and their requests?                                                                                                                                                                                                     
    - **Error Report** (https://microservice-api-patterns.org/patterns/structure/specialPurposeRepresentations/ErrorReport) - How can an API provider inform its clients about communication and processing faults? How can this information be made i                                                                                                                                                
ndependent of the underlying communication technologies and platforms (for example, protocol-level headers representing status codes)?                                                                                                                                                                                                                                                                
    - **Context Representation** (https://microservice-api-patterns.org/patterns/structure/specialPurposeRepresentations/ContextRepresentation) - How can API consumers and providers exchange context information without relying on any particular r                                                                                                                                                
emoting protocols? How can identity information and quality properties in a request be made visible to related subsequent ones in conversations?                                                                                                                                                                                                                                                      
- Quality
- Reference Management                                                                                                                                                                                                                                                               
    - **Embedded Entity** (https://microservice-api-patterns.org/patterns/quality/referenceManagement/EmbeddedEntity) - How can one avoid sending multiple messages when their receivers require insights about multiple related information elements?                               
    - **Linked Information Holder** (https://microservice-api-patterns.org/patterns/quality/referenceManagement/LinkedInformationHolder) - How can messages be kept small even when an API deals with multiple information elements that reference eac                               
h other?                                                                                                                                                                                                                                                                             
- Data Transfer Parsimony                                                                                                                                                                                                                                                            
    - **Pagination** (https://microservice-api-patterns.org/patterns/quality/dataTransferParsimony/Pagination) - How can messages be kept small even when an API deals with multiple information elements that reference each other?                                                 
    - **Wish List** (https://microservice-api-patterns.org/patterns/quality/dataTransferParsimony/WishList) - How can an API client inform the API provider at runtime about the data it is interested in?                                                                           
    - **Wish Template** (https://microservice-api-patterns.org/patterns/quality/dataTransferParsimony/WishTemplate) - 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?                                                                                                                                                                                                                                                            
    - **Conditional Request** (https://microservice-api-patterns.org/patterns/quality/dataTransferParsimony/ConditionalRequest) - How can unnecessary server-side processing and bandwidth usage be avoided when frequently invoking API operations th                               
at return rarely changing data?                                                                                                                                                                                                                                                      
    - **Request Bundle** (https://microservice-api-patterns.org/patterns/quality/dataTransferParsimony/RequestBundle) - How can the number of requests and responses be reduced to increase communication efficiency?                                                                

- Quality Management and Governance                                                                                                                                                                                                                                                                                                                                                                 
    - **Pricing Plan** (https://microservice-api-patterns.org/patterns/quality/qualityManagementAndGovernance/PricingPlan) - How can the API provider meter API service consumption and charge for it?                                                                                                                                                                                              
    - **Rate Limit** (https://microservice-api-patterns.org/patterns/quality/qualityManagementAndGovernance/RateLimit) - How can the API provider prevent API clients from excessive API usage?                                                                                                                                                                                                     
    - **Service Level Agreement** (https://microservice-api-patterns.org/patterns/quality/qualityManagementAndGovernance/ServiceLevelAgreement) - 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?                                                                                                                                                                                                                                                      

- Evolution
- **Version Identifier** (https://microservice-api-patterns.org/patterns/evolution/VersionIdentifier) - How can an API provider indicate its current capabilities as well as the existence of possibly incompatible changes to clients in order to pre                                                                         
vent malfunctioning of clients due to undiscovered interpretation errors?                                                                                                                                                                                                                                                      
- **Semantic Versioning** (https://microservice-api-patterns.org/patterns/evolution/SemanticVersioning) - How can stakeholders compare API versions to detect immediately whether they are compatible?                                                                                                                         
- **Two In Production** (https://microservice-api-patterns.org/patterns/evolution/TwoInProduction) - How can a provider gradually update an API without breaking existing clients but also without having to maintain a large number of API versions i                                                                         
n production?                                                                                                                                                                                                                                                                                                                  
- **Aggressive Obsolescence** (https://microservice-api-patterns.org/patterns/evolution/AggressiveObsolescence) - How can API providers reduce the effort for maintaining an entire API or its parts (such as endpoints, operations, or message repres                                                                         
entations) with guaranteed service quality levels?                                                                                                                                                                                                                                                                             
- **Experimental Preview** (https://microservice-api-patterns.org/patterns/evolution/ExperimentalPreview) - How can providers make the introduction of a new API, or new API version, less risky for their clients and obtain early adopter feedback w                                                                         
ithout having to freeze the API design prematurely?                                                                                                                                                                                                                                                                            
- **Limited Lifetime Guarantee** (https://microservice-api-patterns.org/patterns/evolution/LimitedLifetimeGuarantee) - How can a provider let clients know for how long they can rely on the published version of an API?                                                                                                      
- **Eternal Lifetime Guarantee** (https://microservice-api-patterns.org/patterns/evolution/EternalLifetimeGuarantee) - How can a provider support clients that are unable or unwilling to migrate to newer API versions at all?                                                                                                


⬆ back to top (#contents)

SOA Patterns
SOA patterns are design solutions that provide guidelines and best practices for developing flexible and reusable service-oriented applications. These patterns address various aspects of service-oriented application design, including service 
identification, interaction, composition, and granularity.
- Foundational Inventory Patterns
   - Canonical Protocol (https://patterns.arcitura.com/soa-patterns/design_patterns/canonical_protocol) - Defines a common communication protocol between services to enable interoperability and decoupling.
   - Canonical Schema (https://patterns.arcitura.com/soa-patterns/design_patterns/canonical_schema) - Defines a standard data model and format for exchanging data between services.
   - Domain Inventory (https://patterns.arcitura.com/soa-patterns/design_patterns/domain_inventory) - Identifies and categorizes the types of services within a particular domain.
   - Enterprise Inventory (https://patterns.arcitura.com/soa-patterns/design_patterns/enterprise_inventory) - Identifies and categorizes the types of services within a particular domain.
   - Logic Centralization (https://patterns.arcitura.com/soa-patterns/design_patterns/logic_centralization) - Centralizes business logic within a service layer to reduce redundancy and promote consistency.
   - Service Layers (https://patterns.arcitura.com/soa-patterns/design_patterns/service_layers) - Centralizes business logic within a service layer to reduce redundancy and promote consistency.
   - Service Normalization (https://patterns.arcitura.com/soa-patterns/design_patterns/service_normalization) - Centralizes business logic within a service layer to reduce redundancy and promote consistency.

- Logical Inventory Layer Patterns
   - Entity Abstraction (https://patterns.arcitura.com/soa-patterns/design_patterns/entity_abstraction) - Abstracts data entities to simplify data access and reduce coupling.
   - Process Abstraction (https://patterns.arcitura.com/soa-patterns/design_patterns/process_abstraction) - Abstracts processes to improve reusability and maintainability.
   - Utility Abstraction (https://patterns.arcitura.com/soa-patterns/design_patterns/utility_abstraction) - Abstracts common utilities to reduce duplication and promote consistency.
   - Micro Task Abstraction (https://patterns.arcitura.com/soa-patterns/design_patterns/micro_task_abstraction) - Breaks down tasks into smaller, more granular tasks for easier management.

- Inventory Centralization Patterns
   - Policy Centralization (https://patterns.arcitura.com/soa-patterns/design_patterns/policy_centralization) - Centralizes policies to reduce duplication and improve consistency.
   - Process Centralization (https://patterns.arcitura.com/soa-patterns/design_patterns/process_centralization) - Centralizes processes to improve reusability and maintainability.
   - Rules Centralization (https://patterns.arcitura.com/soa-patterns/design_patterns/rules_centralization) - Centralizes business rules to reduce duplication and promote consistency.
   - Schema Centralization (https://patterns.arcitura.com/soa-patterns/design_patterns/schema_centralization) - Centralizes data schemas to reduce duplication and improve consistency.

- Inventory Implementation Patterns
   - Canonical Resources (https://patterns.arcitura.com/soa-patterns/design_patterns/canonical_resources) - Defines a standard set of resources for common functionality across services.
   - Cross-Domain Utility Layer (https://patterns.arcitura.com/soa-patterns/design_patterns/cross_domain_utility_layer) - Uses multiple protocols for improved performance and flexibility.
   - Dual Protocols (https://patterns.arcitura.com/soa-patterns/design_patterns/dual_protocols) - Defines a common utility layer across multiple domains.
   - Inventory Endpoint (https://patterns.arcitura.com/soa-patterns/design_patterns/inventory_endpoint) - Defines a standard endpoint for accessing inventory resources.
   - Service Grid (https://patterns.arcitura.com/soa-patterns/design_patterns/service_grid) - Provides a framework for managing and scaling services.
   - State Repository (https://patterns.arcitura.com/soa-patterns/design_patterns/state_repository) - Stores and manages service state information.
   - Stateful Services (https://patterns.arcitura.com/soa-patterns/design_patterns/stateful_services) - Maintains state information across service invocations.
   - Augmented Protocols (https://patterns.arcitura.com/soa-patterns/design_patterns/augmented_protocols) - Enhances protocols with additional features.

- Inventory Governance Patterns
   - Canonical Expression (https://patterns.arcitura.com/soa-patterns/design_patterns/canonical_expression) - Defines a standard expression language for inventory data.
   - Canonical Versioning (https://patterns.arcitura.com/soa-patterns/design_patterns/canonical_versioning) - Defines a standard versioning scheme for inventory resources.
   - Metadata Centralization (https://patterns.arcitura.com/soa-patterns/design_patterns/metadata_centralization) - Centralizes metadata to reduce duplication and improve consistency.

- Foundational Service Patterns
   - Agnostic Capability (https://patterns.arcitura.com/soa-patterns/design_patterns/agnostic_capability) - Abstracts service capabilities for improved flexibility.
   - Agnostic Context (https://patterns.arcitura.com/soa-patterns/design_patterns/agnostic_context) - Abstracts service context for improved flexibility.
   - Functional Decomposition (https://patterns.arcitura.com/soa-patterns/design_patterns/functional_decomposition) - Breaks down services into smaller, more manageable components.
   - Non-Agnostic Context (https://patterns.arcitura.com/soa-patterns/design_patterns/non_agnostic_context) - Breaks down services into smaller, more manageable components.
   - Service Encapsulation (https://patterns.arcitura.com/soa-patterns/design_patterns/service_encapsulation) - Encapsulates service functionality for improved maintainability.

- Service Implementation Patterns
   - Partial State Deferral (https://patterns.arcitura.com/soa-patterns/design_patterns/partial_state_deferral) - Encapsulates service functionality for improved maintainability.
   - Partial Validation (https://patterns.arcitura.com/soa-patterns/design_patterns/partial_validation) - Validates only relevant data for improved performance.
   - Redundant Implementation (https://patterns.arcitura.com/soa-patterns/design_patterns/redundant_implementation) - Implements multiple versions of a service for improved flexibility.
   - Service Data Replication (https://patterns.arcitura.com/soa-patterns/design_patterns/service_data_replication) - Replicates data across multiple services for improved performance.
   - Service Façade (https://patterns.arcitura.com/soa-patterns/design_patterns/service_facade) - Provides a simplified interface to a complex service for improved usability.
   - UI Mediator (https://patterns.arcitura.com/soa-patterns/design_patterns/ui_mediator) - Mediates between the user interface and underlying services for improved usability.
   - Reference Data Centralization (https://patterns.arcitura.com/soa-patterns/design_patterns/reference_data_centralization) - Centralizes reference data to reduce duplication and improve consistency.
   - Microservice Deployment (https://patterns.arcitura.com/soa-patterns/design_patterns/microservice_deployment) - Deploys services as independent, autonomous units for improved scalability and resilience.
   - Containerization (https://patterns.arcitura.com/soa-patterns/design_patterns/containerization) - How can an environment be provided with maximum support for services with high-performance recovery and scalability requirements?

- Service Security Patterns
   - Exception Shielding (https://patterns.arcitura.com/soa-patterns/design_patterns/exception_shielding) - Protects against security vulnerabilities through proper handling of exceptions.
   - Message Screening (https://patterns.arcitura.com/soa-patterns/design_patterns/message_screening) - Screens messages for malicious content.
   - Service Perimeter Guard (https://patterns.arcitura.com/soa-patterns/design_patterns/service_perimeter_guard) - Guards the service perimeter to prevent unauthorized access.
   - Trusted Subsystem (https://patterns.arcitura.com/soa-patterns/design_patterns/trusted_subsystem) - Establishes trust between subsystems for improved security.

- Service Contract Design Patterns
   - Concurrent Contracts (https://patterns.arcitura.com/soa-patterns/design_patterns/concurrent_contracts) - Allows multiple versions of a service contract to coexist simultaneously.
   - Contract Centralization (https://patterns.arcitura.com/soa-patterns/design_patterns/contract_centralization) - Centralizes service contracts to improve consistency and reduce duplication.
   - Contract Denormalization (https://patterns.arcitura.com/soa-patterns/design_patterns/contract_denormalization) - Centralizes service contracts to improve consistency and reduce duplication.
   - Decoupled Contract (https://patterns.arcitura.com/soa-patterns/design_patterns/decoupled_contract) - Decouples service contracts from their implementation for improved flexibility.
   - Validation Abstraction (https://patterns.arcitura.com/soa-patterns/design_patterns/validation_abstraction) - Abstracts validation logic to improve reusability and maintainability.

- Legacy Encapsulation Patterns
   - File Gateway (https://patterns.arcitura.com/soa-patterns/design_patterns/file_gateway) - Provides a gateway to access legacy file-based systems.
   - Legacy Wrapper (https://patterns.arcitura.com/soa-patterns/design_patterns/legacy_wrapper) - Wraps legacy systems to expose them as services.
   - Multi-Channel Endpoint (https://patterns.arcitura.com/soa-patterns/design_patterns/multi_channel_endpoint) - Provides multiple communication channels to access legacy systems.

- Service Governance Patterns
   - Compatible Change (https://patterns.arcitura.com/soa-patterns/design_patterns/compatible_change) - Enables changes to a service without breaking existing clients.
   - Decomposed Capability (https://patterns.arcitura.com/soa-patterns/design_patterns/decomposed_capability) - Breaks down a service capability into smaller, more manageable pieces.
   - Distributed Capability (https://patterns.arcitura.com/soa-patterns/design_patterns/distributed_capability) - Breaks down a service capability into smaller, more manageable pieces.
   - Proxy Capability (https://patterns.arcitura.com/soa-patterns/design_patterns/proxy_capability) - Provides a proxy to a remote service capability to improve performance and reduce network overhead.
   - Service Decomposition (https://patterns.arcitura.com/soa-patterns/design_patterns/service_decomposition) - Breaks down a monolithic service into smaller, more manageable pieces.
   - Service Refactoring (https://patterns.arcitura.com/soa-patterns/design_patterns/service_refactoring) - Refactors a service to improve its design and performance.
   - Termination Notification (https://patterns.arcitura.com/soa-patterns/design_patterns/termination_notification) - Notifies clients of a service's termination.
   - Version Identification (https://patterns.arcitura.com/soa-patterns/design_patterns/version_identification) - Identifies the version of a service. 

- Capability Composition Patterns
   - Capability Composition (https://patterns.arcitura.com/soa-patterns/design_patterns/capability_composition) - Combines multiple service capabilities to create a new capability.
   - Capability Recomposition (https://patterns.arcitura.com/soa-patterns/design_patterns/capability_recomposition) - Recombines existing service capabilities to create a new capability.

- Service Messaging Patterns
   - Asynchronous Queuing (https://patterns.arcitura.com/soa-patterns/design_patterns/asynchronous_queuing) - Uses a message queue to decouple services and improve scalability and reliability.
   - Event-Driven Messaging (https://patterns.arcitura.com/soa-patterns/design_patterns/event_driven_messaging) - Uses events to trigger service invocations and reduce coupling.
   - Intermediate Routing (https://patterns.arcitura.com/soa-patterns/design_patterns/intermediate_routing) - Uses intermediate routing nodes to improve performance and flexibility.
   - Messaging Metadata (https://patterns.arcitura.com/soa-patterns/design_patterns/messaging_metadata) - Uses metadata to describe and manage service messages.
   - Reliable Messaging (https://patterns.arcitura.com/soa-patterns/design_patterns/reliable_messaging) - Ensures message delivery and reliability in a distributed environment.
   - Service Agent (https://patterns.arcitura.com/soa-patterns/design_patterns/service_agent) - Acts as a proxy for a remote service to improve performance and reduce network overhead.
   - Service Callback (https://patterns.arcitura.com/soa-patterns/design_patterns/service_callback) - Uses callbacks to communicate between services.
   - Service Instance Routing (https://patterns.arcitura.com/soa-patterns/design_patterns/service_instance_routing) - Routes messages based on the service instance to improve performance and scalability.
   - Service Messaging (https://patterns.arcitura.com/soa-patterns/design_patterns/service_messaging) - Describes the communication between services.
   - State Messaging (https://patterns.arcitura.com/soa-patterns/design_patterns/state_messaging) - Uses messages to manage state information in a distributed environment.

- Composition Implementation Patterns
   - Agnostic Sub-Controller (https://patterns.arcitura.com/soa-patterns/design_patterns/agnostic_sub_controller) - Separates sub-controllers from the main controller to improve reusability and maintainability.
   - Atomic Service Transaction (https://patterns.arcitura.com/soa-patterns/design_patterns/atomic_service_transaction) - Uses transactions to ensure atomicity and consistency across multiple service invocations.
   - Compensating Service Transaction (https://patterns.arcitura.com/soa-patterns/design_patterns/compensating_service_transaction) - Reverses the effects of a failed transaction.
   - Composition Autonomy (https://patterns.arcitura.com/soa-patterns/design_patterns/composition_autonomy) - Enables services to act autonomously within a composition.

- Service Interaction Security Patterns
   - Brokered Authentication (https://patterns.arcitura.com/soa-patterns/design_patterns/brokered_authentication) - Authenticates clients through a broker.
   - Data Confidentiality (https://patterns.arcitura.com/soa-patterns/design_patterns/data_confidentiality) - Ensures data confidentiality in a distributed environment.
   - Data Origin Authentication (https://patterns.arcitura.com/soa-patterns/design_patterns/data_origin_authentication) - Authenticates the origin of a message.
   - Direct Authentication (https://patterns.arcitura.com/soa-patterns/design_patterns/direct_authentication) - Authenticates clients directly.

- Transformation Patterns
   - Data Format Transformation (https://patterns.arcitura.com/soa-patterns/design_patterns/data_format_transformation) - Transforms data formats to enable interoperability.
   - Data Model Transformation (https://patterns.arcitura.com/soa-patterns/design_patterns/data_model_transformation) - Transforms data models to enable interoperability.
   - Protocol Bridging (https://patterns.arcitura.com/soa-patterns/design_patterns/protocol_bridging) - Bridges between different protocols to enable interoperability.

- REST-inspired Patterns
   - Entity Linking (https://patterns.arcitura.com/soa-patterns/design_patterns/entity_linking) - Links related resources to enable navigation and discovery.
   - Lightweight Endpoint (https://patterns.arcitura.com/soa-patterns/design_patterns/lightweight_endpoint) - Provides a lightweight endpoint for resource access.
   - Reusable Contract (https://patterns.arcitura.com/soa-patterns/design_patterns/reusable_contract) - Reuses common contracts to improve consistency and reduce duplication.
   - Content Negotiation (https://patterns.arcitura.com/soa-patterns/design_patterns/content_negotiation) - Negotiates the content format between clients and servers.
   - Endpoint Redirection (https://patterns.arcitura.com/soa-patterns/design_patterns/endpoint_redirection) - Redirects clients to alternative endpoints.
   - Idempotent Capability (https://patterns.arcitura.com/soa-patterns/design_patterns/idempotent_capability) - Ensures that the same action can be performed multiple times without changing the system state.


⬆ back to top (#contents)

Resources
Some useful specifications, standards, articles and documentation.
API Specification
- API Blueprint (⭐8.6k) (https://github.com/apiaryio/api-blueprint) - A powerful high-level language for designing and documenting APIs that allows software engineers to easily collaborate and create efficient APIs.
- AsyncAPI (⭐4.6k) (https://github.com/asyncapi/spec) - An essential tool for developing Event-Driven Architectures (EDA) and enables engineers to build a better tooling ecosystem.
- CloudEvents (⭐5.4k) (https://github.com/cloudevents/spec) -  A specification for describing event data in common formats to provide interoperability across services, platforms and systems.
- GraphQL (⭐14k) (https://github.com/graphql/graphql-spec) - A sophisticated query language and runtime for building efficient APIs that empowers engineers to retrieve data from existing systems with ease.
- JSON:API (⭐7.5k) (https://github.com/json-api/json-api) - A standardized specification for building APIs that simplifies the representation of resources, relationships, and metadata, making it easier for software engineers to create efficient 
APIs.
- OpenAPI (ex.Swagger) (⭐29k) (https://github.com/OAI/OpenAPI-Specification) - A language-agnostic specification for creating RESTful APIs that enables both humans and machines to understand the capabilities of a service without the need for 
source code or documentation.
- RAML (⭐3.8k) (https://github.com/raml-org/raml-spec) - A RESTful API Modeling Language that allows software engineers to design and create efficient APIs by modeling resources, endpoints, and interactions.
- Standard Webhooks (⭐1.4k) (https://github.com/standard-webhooks/standard-webhooks) - Open source tools and guidelines for sending webhooks easily, securely, and reliably.
- WSDL (http://www.w3.org/TR/wsdl20) - A powerful XML-based interface description language for SOAP-based services that enables software engineers to describe the functionality of a web service and automate the creation of client code.


⬆ back to top (#contents)

Articles
- API-Security-Checklist (⭐22k) (https://github.com/shieldfy/API-Security-Checklist) - Best practices about REST API security.
- Architectural Styles and
the Design of Network-based Software Architectures (https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm) - Roy Fielding's dissertation defining REST.
- Enterprise Integration Using REST (http://martinfowler.com/articles/enterpriseREST.html) - Discusses the constraints and flexibility that you have with nonpublic APIs, and lessons learned from doing large scale RESTful integration across 
multiple teams.
- Richardson Maturity Model (http://martinfowler.com/articles/richardsonMaturityModel.html) - Explained by Martin Fowler, originally presented by Leonard Richardson.
- Web API Design: Crafting interfaces that developers love (https://pages.apigee.com/rs/apigee/images/api-design-ebook-2012-03.pdf) - Creating Web APIs that are consistent, intuitive, and user-friendly for developers.


⬆ back to top (#contents)

Certifications


  
- API Designer (https://apiacademy.learnupon.com/lpaths/4147453/courses/262369/details) - Validate your understanding of API design basics and best practices.
- API Product Manager (https://apiacademy.learnupon.com/lpaths/4147453/courses/262371/details) - Demonstrate your proficiency in managing APIs as products.
- API Security Architect (https://apiacademy.learnupon.com/lpaths/4147453/courses/262370/details) - Validate your expertise in securing APIs using modern architectures.
  



  
- API Documentation Best Practices (https://www.apisecuniversity.com/courses/api-documentation-best-practices) - The 2-hour course covers everything you need to know to create, automate, and publish API documentation your developers, partners and
users will love. You wll also learn why API documentation is the foundation for strong governance, effective API security, and achieving your API business goals.
- API Penetration Testing (https://www.apisecuniversity.com/courses/api-penetration-testing) - The API Penetration Testing course covers all the key topics to become an APIsec professional. This hands-on course includes over 12 hours of live 
instruction and provides detailed labs on API hacking techniques and how to uncover vulnerabilities.
- API Security for PCI Compliance (https://www.apisecuniversity.com/courses/api-security-for-pci-compliance) - This 60-minute course examines the new PCI DSS 4.0 requirements and details the API security obligations for compliance. DSS 4.0 
introduces API security concerns for the time ever - enroll to understand what the implications are for your organization.
- API Security Fundamentals (https://www.apisecuniversity.com/courses/api-security-fundamentals) - The 90-minute course covers the core threats to APIs and how to prevent breaches. Learn the OWASP API Security Top 10, examine real-world API 
attacks, and understand the 3 Pillars of API Security.
- Certified API Security Analyst (https://www.apisecuniversity.com/courses/certified-api-security-analyst-exam) - The CASA exam is designed to test your expertise in API security threats, risks, and best practices. Students are expected to have 
completed the OWASP API Security and Beyond! course before attempting to earn the CASA certification.
- OWASP API Security Top 10 (https://www.apisecuniversity.com/courses/owasp-api-security-top-10-and-beyond) - The 90-minute course provides a deep-dive into the 2023 edition of the OWASP API Security Top 10 - and covers key concepts that didn't 
make it into the Top 10.
- Securing API Servers (https://www.apisecuniversity.com/courses/securing-api-servers) - Learn key concepts for keeping API servers secure - from CORS to error handling to rate limiting and more.
  




- Apollo Graph Developer - Associate Certification (https://www.apollographql.com/tutorials/exams/apollo-graph-associate) - Developers who obtain this certification possess a solid foundational knowledge of GraphQL and the Apollo tool suite to 
design a schema, run an Apollo Server 4, and perform queries with Apollo Client 3 on the frontend.

- Apollo Graph Developer - Professional Certification (https://www.apollographql.com/tutorials/certifications/apollo-graph-professional) - Developers who obtain this certification demonstrate strong familiarity with Apollo Federation concepts. 
They can apply those concepts to build a federated supergraph or move an existing monolithic graph to federation.




  
- Associate Administrator Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OIKWA2&ltui__urlRedirect=learning-plan-detail-standard) - Validates an individual's foundational knowledge and 
skills in managing and administering the Boomi platform, focusing on platform monitoring, troubleshooting, and security.
- Associate Developer Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OIeWAM&ltui__urlRedirect=learning-plan-detail-standard) - Demonstrates a candidate's basic understanding of building 
and deploying integration processes using the Boomi platform, including design patterns, deployment, and error handling.
- Associate EDI for X12 Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OIFWA2&ltui__urlRedirect=learning-plan-detail-standard) - Validates an individual's proficiency in using Boomi to 
design, develop, and manage Electronic Data Interchange (EDI) integrations with the X12 standard, covering essential concepts like EDI document structure and trading partner management.
- Associate Flow Essentials Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OIZWA2&ltui__urlRedirect=learning-plan-detail-standard) - Showcases a candidate's knowledge of creating and 
managing business applications using Boomi Flow, with emphasis on workflow design, user interfaces, and data integration.
- Associate Master Data Hub Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OIPWA2&ltui__urlRedirect=learning-plan-detail-standard) - Highlights a candidate's understanding of using the 
Boomi Master Data Hub to ensure data quality and consistency across systems, focusing on data modeling, governance, and synchronization.
- Development and Application Architecture Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OJOWA2&ltui__urlRedirect=learning-plan-detail-standard) - Confirms an individual's expertise in 
designing and implementing complex integration solutions and application architectures on the Boomi platform, including best practices and performance optimization.
- Professional API Design Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OKzWAM&ltui__urlRedirect=learning-plan-detail-standard) - Demonstrates a candidate's ability to design, develop, 
and manage APIs using Boomi, including RESTful API principles, API security, and versioning.
- Professional API Management Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OIyWAM&ltui__urlRedirect=learning-plan-detail-standard) - Validates an individual's expertise in managing the 
full lifecycle of APIs using the Boomi platform, including API deployment, monitoring, and analytics.
- Professional Developer Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OJrWAM&ltui__urlRedirect=learning-plan-detail-standard) - Recognizes a candidate's in-depth knowledge and skills in 
developing, deploying, and managing integration processes using Boomi, with emphasis on advanced data transformation and error handling techniques.
- Professional Flow Developer Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OIUWA2&ltui__urlRedirect=learning-plan-detail-standard) - Showcases an individual's advanced capabilities in 
designing, developing, and managing business applications using Boomi Flow, including complex workflow design, custom UI components, and integration with external systems.
- Professional Linux Operational Administrator Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OI5WAM&ltui__urlRedirect=learning-plan-detail-standard) - Confirms a candidate's proficiency 
in managing and administering Boomi on Linux systems, covering topics such as system installation, configuration, security, and performance optimization.
- Professional Windows Operational Administrator Certification (https://community.boomi.com/s/learning-plan-detail-standard?ltui__urlRecordId=aOM6S0000008OIAWA2&ltui__urlRedirect=learning-plan-detail-standard) - Validates an individual's 
expertise in managing and administering Boomi on Windows systems, focusing on system installation, configuration, security, and performance optimization.
  



  
- IBM Certified Solution Developer – App Connect Enterprise V11 (https://www.ibm.com/training/certification/C0003107#exam) - Validate your intermediate-level knowledge and experience to develop, deploy, tune, and support platform-independent 
message flow applications using IBM App Connect V11.0.
- IBM Certified Solution Implementer – API Connect v10.0.3 (https://www.ibm.com/training/certification/C0002604#exam) - Demonstrate your intermediate-level knowledge and skills to develop, publish, configure, and manage APIs using IBM API Connect
v10.0.3.





- Event-native API Management Foundations (https://gravitee.getlearnworlds.com/course/gravitee-event-native-api-management-foundations) - Basics of Event-native API Management.
- Event-native API Management Professional (https://gravitee.getlearnworlds.com/course/gravitee-enap-certification) - Focuses on some more advanced API Management concepts, plus foundational knowledge around how to use Gravitee API Management.
  



  
- Kong Gateway Certified Associate (https://konghq.com/academy/exam-preparation) - Validate your entry-level knowledge and skills on Kong Gateway for developers, DevOps, and architects.




  
- MuleSoft Certified Developer - Level 1 (https://training.mulesoft.com/certification/developer-mule4-level1) - Validate your knowledge and skills to design, build, test and debug, deploy, and manage basic APIs and integrations using MuleSoft.
- MuleSoft Certified Developer - Level 2 (https://training.mulesoft.com/certification/developer-mule4-level2) - Validate your ability to work on production-ready Mule applications that address and balance critical non-functional requirements 
including monitoring, performance, maintainability, reliability, and security.
- MuleSoft Certified Integration Architect - Level 1 (https://training.mulesoft.com/certification/architect-integration-level1) - Validate your knowledge and skills to translate functional and non-functional requirements into integration 
interfaces and implementations.
- MuleSoft Certified Platform Architect - Level 1 (https://training.mulesoft.com/certification/architect-platform-level1) - Validate your knowledge and skills to direct the emergence of an effective application network out of individual 
integration solutions following API-led connectivity across an organization using Anypoint Platform.





- Oracle Business Process Management Suite 12c Certified Implementation Specialist (https://education.oracle.com/oracle-business-process-management-suite-12c-essentials/pexam_1Z0-435) - Validate your expertise in implementing Oracle BPM Suite 12c
solution.
- Oracle Cloud Platform Application Integration 2025 Certified Professional (https://education.oracle.com/oracle-cloud-infrastructure-2024-application-integration-professional/pexam_1Z0-1042-25) - Validate your understanding of Oracle Application
Integration to implement these Cloud services.
- Oracle Data Integrator 12c Certified Implementation Specialist (https://education.oracle.com/oracle-data-integrator-12c-certified-implementation-specialist/trackp_379) - Validate your expertise in selling or implementing Oracle Data Integration
12c solutions.
- Oracle SOA Suite 12c Certified Implementation Specialist (https://education.oracle.com/oracle-soa-suite-12c-essentials/pexam_1Z0-434) - Validate your expertise in implementing solutions based on Oracle SOA Suite 12c.




 
- Red Hat Certified Specialist in API Management (https://www.redhat.com/en/services/certification/red-hat-certified-specialist-api-management) - Validates the ability to create and maintain enterprise APIs using the Red Hat 3scale API Management
platform.
- Red Hat Certified Specialist in Business Rules (https://www.redhat.com/en/services/certification/rhcs-business-rules) - Checks the knowledge, skills, and abilities needed to perform tasks involving the implementation and management of business 
logic using the Red Hat JBoss BRMS.
- Red Hat Certified Specialist in Cloud-native Integration (https://www.redhat.com/en/services/certification/rhcs-cloud-native-integration) - Validates the ability to create and maintain enterprise integration services based on Red Hat Fuse, 
Camel, and APIs.
- Red Hat Certified Specialist in Event-Driven Development with Kafka (https://www.redhat.com/en/services/certification/red-hat-certified-specialist-event-driven-development-kafka) - Validates the ability to develop applications using Apache 
Kafka and Apache Kafka Streams.
  



  
- SAP Certified Associate - Integration Developer (https://learning.sap.com/certifications/sap-certified-associate-integration-developer) - Validates that the candidate possesses the fundamental and core knowledge required of the SAP Integration 
Suite profile.
  




- SnapLogic Administrator Certification (https://learn.snaplogic.com/snaplogic-administrator-certification) - Assesses your ability to handle administrative tasks for SnapLogic instances.
- SnapLogic Architect Certification (https://learn.snaplogic.com/snaplogic-architect-certification) - 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, and Best Practices.
- SnapLogic Developer Certification (https://learn.snaplogic.com/snaplogic-developer-certification) - Testing your expertise in using the SnapLogic SDK, implementing different parts of Snap functionality, and building custom Snaps.
- SnapLogic Integrator Accreditation (https://learn.snaplogic.com/snaplogic-accreditation) - 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.
- SnapLogic Integrator Certification (https://learn.snaplogic.com/snaplogic-integrator-certification-1) - Focuses on topics such as beginner training, ultra tasks, pipeline migration, and user assistance videos covering various integration 
endpoints.





- TIBCO BusinessWorks Associate (https://www.credly.com/org/citrix/badge/tca-tibco-businessworks) - Checks the understanding of Business Studio and TIBCO Cloud Integration, designing application components (modules, WSDL, REST API), developing 
integration applications, and testing, deploying, and managing applications.
- TIBCO BusinessWorks Certified Professional (https://www.credly.com/org/citrix/badge/tcp-tibco-businessworks) - Validates the ability to design, develop, deploy, monitor, and manage TIBCO BusinessWorks applications of average complexity with 
minimal supervision.
- TIBCO BusinessWorks Container Edition Certified Professional (https://www.credly.com/org/citrix/badge/tcp-tibco-businessworks-container-edition) - Validates the ability to develop, deploy, and manage TIBCO BusinessWorks Container Edition 
applications of average complexity with minimal supervision.
- TIBCO BPM Enterprise Associate (https://www.credly.com/org/citrix/badge/tca-tibco-bpm-enterprise) - Checks the understanding of TIBCO BPM's features and capabilities, developing and managing business processes, and deploying and testing process
applications.
- TIBCO BPM Enterprise Certified Professional (https://www.credly.com/org/citrix/badge/tcp-tibco-bpm-enterprise) - Validates the ability to design, develop, deploy, and manage business processes using TIBCO BPM Enterprise Suite.
- TIBCO Cloud Associate Certification (https://www.credly.com/org/citrix/badge/tca-tibco-cloud) - Validates the skills and knowledge required to work with TIBCO Cloud, including its key components and features.
- TIBCO Cloud API Management Associate (https://www.credly.com/org/citrix/badge/tca-tibco-cloud-api-management) - Covers topics such as API definition creation and testing, API key authentication, and using the Developer Portal and I/O docs.
- TIBCO Cloud API Management Certified Professional (https://www.credly.com/org/citrix/badge/tcp-tibco-cloud-api-management) - Validates the ability to implement TIBCO Cloud Mesh, OAuth-based security, and manage SOAP services.
- TIBCO Cloud Integration Associate (https://www.credly.com/org/citrix/badge/tca-tibco-cloud-integration) - Validates the skills and knowledge required to work with TIBCO Cloud Integration, including its Connect, Develop, and Integrate 
capabilities.
- TIBCO Cloud Integration - Connect Associate (https://www.credly.com/org/citrix/badge/tca-tibco-cloud-integration-connect) - Checks the usage of Connect capability of TIBCO Cloud Integration, installing On-Premise Agent, creating connections and
integration apps, and configuring flows.
- TIBCO Cloud Integration - Connect Certified Professional (https://www.credly.com/org/citrix/badge/tcp-tibco-cloud-integration-connect) - Checks the creation and management of connections, ensuring connection security, and troubleshooting issues
related to connections in TIBCO Cloud Integration.
- TIBCO Cloud Integration Certified Professional (https://www.credly.com/org/citrix/badge/tcp-tibco-cloud-integration) - Checks the knowledge about capabilities and benefits, integrating, developing, and connecting applications, creating APIs 
using the API Modeler and Mock functionality, and more.
- TIBCO Messaging Associate (https://www.credly.com/org/citrix/badge/tca-tibco-messaging) - Covers topics such as TIBCO Enterprise Message Service (EMS), TIBCO FTL, TIBCO eFTL, as well as other messaging technologies such as Apache Kafka, Apache 
Pulsar, and Eclipse Mosquitto.
- TIBCO Messaging Certified Professional (https://www.credly.com/org/citrix/badge/tcp-tibco-messaging) - Validates the skills and knowledge required to work with TIBCO Messaging and its components, including TIBCO Enterprise Message Service 
(EMS), TIBCO FTL, and TIBCO eFTL.
  




- Workato Automation Pro I (https://academy.workato.com/enterprise-automation-i-exam) - Fundamentals of business automation processes.
- Workato Automation Pro II (https://academy.workato.com/enterprise-automation-ii-exam) - Advanced and practical approaches to automation.
- Workato Automation Pro III (https://academy.workato.com/automation-pro-iii-exam) - In-depth series of badged modules for maximizing Workato's potential.





- WSO2 Certified API Manager Developer - V3 (https://wso2.com/training/certification/certified-api-manager-developer/) - Assesses your expertise in designing, developing, and publishing APIs using WSO2 API Manager V3, including API lifecycle 
management, access control, and API documentation.
- WSO2 Certified API Manager Developer - V4 - Micro Integrator Profile (https://wso2.com/training/certification/certified-api-manager-developer-v4-micro-integrator-profile/) - Validates your expertise in designing, developing, and publishing APIs
using the Micro Integrator profile of WSO2 API Manager V4. It covers API lifecycle management, access control, and API documentation within the Micro Integrator context.
- WSO2 Certified API Manager Expert - V3 (https://wso2.com/training/certification/certified-api-manager-expert/) - Confirms your advanced skills and knowledge in using WSO2 API Manager V3 for API management, including API creation, publishing, 
security, policy implementation, and analytics.
- WSO2 Certified API Manager Expert - V4 - API Management Profile (https://wso2.com/training/certification/api-manager-expert-v4-api-management-profile/) - Demonstrates your proficiency in using WSO2 API Manager V4 for API management tasks, such 
as creating, publishing, and securing APIs, as well as implementing policies and analytics.
- WSO2 Certified Enterprise Integrator Developer - V7 - Micro Integrator (https://wso2.com/training/certification/certified-enterprise-integrator-developer-micro-integrator/) - Validates your knowledge and skills in using the Micro Integrator 
profile of WSO2 Enterprise Integrator V7 to develop, deploy, and manage integration solutions.
- WSO2 Certified Enterprise Integrator Developer - V7 - Streaming Integrator (https://wso2.com/training/certification/certified-enterprise-integrator-developer-streaming-integrator/) - Demonstrates your expertise in using the Streaming Integrator
profile of WSO2 Enterprise Integrator V7 to develop, deploy, and manage real-time data integration and streaming analytics solutions.
- WSO2 Certified Enterprise Integrator Expert - V6 (https://wso2.com/training/certification/certified-enterprise-integrator6-expert/) - Tests your in-depth knowledge and skills in using WSO2 Enterprise Integrator V6 for complex integration 
scenarios, including best practices, troubleshooting, and performance tuning.
- WSO2 Certified Solutions Architect Associate (https://wso2.com/training/certification/certified-solutions-architect-associate/) - Assesses your understanding of the fundamental concepts and principles of WSO2 product architecture, as well as 
your ability to design and implement solutions using WSO2 technologies.




⬆ back to top (#contents)


Connectors
- JCA (https://projects.eclipse.org/projects/ee4j.jca) - Defines a standard architecture for Jakarta EE application components to connect to Enterprise Information Systems. Formerly Java EE Connector Architecture and J2EE Connector Architecture.
- Kafka Connect (https://kafka.apache.org/documentation/#connect) - A tool for scalably and reliably streaming data between Apache Kafka and other systems.


⬆ back to top (#contents)

Data Formats
- Apache Avro (⭐3.1k) (https://github.com/apache/avro) - Data serialization system that provides compact, fast, and efficient serialization of structured data. It supports schema evolution, allows for efficient data compression, and is designed 
to work well with big data processing frameworks.
- BSON (https://bsonspec.org/) - Binary-encoded serialization format for JSON-like documents that is designed to be lightweight and efficient. It supports rich data types and is widely used in NoSQL databases, such as MongoDB.
- CSV (https://datatracker.ietf.org/doc/html/rfc4180) - A simple and widely used data format that stores tabular data in plain text. It is easy to read and write, and can be processed by most programming languages.
- JSON (https://datatracker.ietf.org/doc/html/rfc8259) - A lightweight and easy-to-read data format that is widely used for data exchange. It supports a wide range of data types and is compatible with many programming languages.
- NDJSON (⭐751) (https://github.com/ndjson/ndjson-spec) - A standard for delimiting JSON objects in stream protocols. It allows for efficient processing of large JSON datasets and is widely used in big data processing.
- Protocol Buffers (⭐67k) (https://github.com/protocolbuffers/protobuf) - A language-neutral and platform-neutral serialization mechanism that is designed to be highly efficient and extensible. It supports rich data types and is widely used in 
distributed systems, such as gRPC and Apache Kafka.
- XML (https://www.w3.org/TR/xml11/) - A flexible and widely used markup language that is used for storing and exchanging structured data. It supports rich data types and is compatible with many programming languages.
- YAML (⭐399) (https://github.com/yaml/yaml-spec) - A human-friendly and easy-to-read data serialization format that is widely used for configuration files and data exchange. It supports rich data types and is compatible with most programming 
languages.


⬆ back to top (#contents)

Integration Styles
- File Transfer (https://www.enterpriseintegrationpatterns.com/patterns/messaging/FileTransferIntegration.html) - Data is exchanged through file exchange between applications.
- Messaging (https://www.enterpriseintegrationpatterns.com/patterns/messaging/Messaging.html) - Applications exchange messages using a messaging infrastructure.
- Remote Procedure Invocation (https://www.enterpriseintegrationpatterns.com/patterns/messaging/EncapsulatedSynchronousIntegration.html) - Applications call functions or procedures on a remote server over a network.
- Shared Database (https://www.enterpriseintegrationpatterns.com/patterns/messaging/SharedDataBaseIntegration.html) - Multiple applications access and manipulate the same data through a common database.


⬆ back to top (#contents)

Market Analysis
- API Management
  - Gartner Critical Capabilities for Full Life Cycle API Management (https://www.gartner.com/doc/code/468184)
  - Gartner Magic Quadrant for Full Life Cycle API Management (https://www.gartner.com/doc/code/464116)
  - The Forrester Wave: API Management Solutions (https://www.forrester.com/go?objectid=RES159081)
- BPM
  - Gartner Critical Capabilities for Intelligent Business Process Management Suites (https://www.gartner.com/doc/code/292486)
  - Gartner Magic Quadrant for Intelligent Business Process Management Suites (https://www.gartner.com/doc/code/345694)
- ETL
  - Gartner Critical Capabilities for Data Integration Tools (https://www.gartner.com/doc/code/464068)
  - Gartner Magic Quadrant for Data Integration Tools (https://www.gartner.com/doc/code/450251)
- iPaaS
  - Gartner Critical Capabilities for Enterprise Integration Platform as a Service (https://www.gartner.com/doc/code/434187)
  - Gartner Magic Quadrant for Enterprise Integration Platform as a Service (https://www.gartner.com/doc/code/397953)
  - The Forrester Wave: Enterprise iPaaS (https://www.forrester.com/report/the-forrester-wave-tm-enterprise-ipaas-q4-2021/RES176201)
- RPA
  - Gartner Critical Capabilities for Robotic Process Automation (https://www.gartner.com/doc/code/465756)
  - Gartner Magic Quadrant for Robotic Process Automation (https://www.gartner.com/doc/code/441474)
  - The Forrester Wave: Robotic Process Automation (https://www.forrester.com/go?objectid=RES161538)


⬆ back to top (#contents)

Protocols
- AMQP 0-9-1 (https://www.rabbitmq.com/resources/specs/amqp0-9-1.pdf) - A message queuing protocol that enables the exchange of messages between applications or systems. AMQP 0-9-1 provides reliability, security, and flexibility to handle complex
messaging scenarios.
- AMQP 1.0 (http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-overview-v1.0-os.html) - A widely accepted message queuing protocol that provides reliable, interoperable, and efficient messaging between systems. AMQP 1.0 supports a broad range
of messaging scenarios and is ideal for complex enterprise-level applications.
- CoAP (http://coap.technology/) - A specialized application protocol designed for constrained devices in the Internet of Things (IoT) ecosystem. CoAP offers a lightweight, low-overhead communication mechanism to support resource-constrained 
devices.
- HTTP (https://httpwg.org/specs/) - A widely used protocol that facilitates communication between web servers and clients. HTTP enables the transfer of data over the internet, making it possible for web applications to function seamlessly.
- JSON-RPC (https://www.jsonrpc.org/specification) - A simple and lightweight remote procedure call protocol that enables communication between systems using JSON data. JSON-RPC offers stateless communication and is suitable for 
resource-constrained devices.
- MQTT (https://mqtt.org/mqtt-specification/) - A lightweight and efficient publish-subscribe protocol that supports messaging between devices. MQTT enables low-overhead communication and is ideal for IoT and mobile applications.
- OpenMessaging (⭐290) (https://github.com/openmessaging/specification) - A cloud native, vendor-neutral open specification for distributed messaging.
- SOAP (https://www.w3.org/TR/soap/) - A messaging protocol that uses XML to enable communication between systems. SOAP supports a wide range of messaging scenarios, including distributed computing and enterprise applications.
- STOMP (https://stomp.github.io/) - A messaging protocol that offers simple, text-oriented communication between systems. STOMP is ideal for low-latency, high-performance messaging scenarios.


⬆ back to top (#contents)

Standard APIs
- JDBC (https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/) - A Java-based API that provides universal data access to relational databases. JDBC offers a consistent and efficient way to access and manipulate data, making it a popular 
choice among developers.
- JMS (https://javaee.github.io/jms-spec/) - A messaging API that enables Java applications to send and receive messages. JMS supports reliable messaging and is widely used in enterprise-level applications.
- ODBC (https://docs.microsoft.com/en-us/sql/odbc/reference/odbc-overview) - A widely accepted API that provides a standardized way to access data from various database management systems. ODBC offers a consistent interface to access data, making
it easy to develop database applications.
- OData (https://www.odata.org/) - An open protocol that enables the creation and consumption of queryable and interoperable REST APIs. OData simplifies the development of REST APIs and offers a standardized way to access data.


⬆ back to top (#contents)

Structure and Validation
- JSON Schema (⭐4.3k) (https://github.com/json-schema-org/json-schema-spec) - A powerful tool for validating the structure of JSON data. JSON Schema enables developers to ensure that JSON data conforms to a specific structure, making it easier 
to process and manipulate.
- Schematron (https://www.schematron.com) - A rule-based validation language that enables developers to define and validate business rules, data reporting, quality control, and other validation scenarios. Schematron offers a flexible way to 
validate XML documents.
- XML Schema (https://www.w3.org/TR/xmlschema11-1/) - A schema language that offers facilities for describing the structure and constraining the contents of XML documents. XML Schema enables developers to ensure that XML data conforms to a 
specific structure, making it easier to process and manipulate.


⬆ back to top (#contents)

Contributing
Your contributions are always welcome! Please take a look at the contribution guidelines (https://github.com/stn1slv/awesome-integration/blob/main/CONTRIBUTING.md) first.

integration Github: https://github.com/stn1slv/awesome-integration