dogear

enter for all results · esc to close

Integration

697 items from stn1slv/awesome-integration ★566

  1. Rules Centralization patterns.arcitura.com

    Centralizes business rules to reduce duplication and promote consistency.

  2. Reusable Contract patterns.arcitura.com

    Reuses common contracts to improve consistency and reduce duplication.

    site link ↗
  3. Reliable Messaging patterns.arcitura.com

    Ensures message delivery and reliability in a distributed environment.

    site link ↗
  4. Reference Data Centralization patterns.arcitura.com

    Centralizes reference data to reduce duplication and improve consistency.

    site link ↗
  5. Redundant Implementation patterns.arcitura.com

    Implements multiple versions of a service for improved flexibility.

  6. Proxy Capability patterns.arcitura.com

    Provides a proxy to a remote service capability to improve performance and reduce network overhead.

    site link ↗
  7. Protocol Bridging patterns.arcitura.com

    Bridges between different protocols to enable interoperability.

    site link ↗
  8. Process Centralization patterns.arcitura.com

    Centralizes processes to improve reusability and maintainability.

    site link ↗
  9. Process Abstraction patterns.arcitura.com

    Abstracts processes to improve reusability and maintainability.

    site link ↗
  10. Policy Centralization patterns.arcitura.com

    Centralizes policies to reduce duplication and improve consistency.

    site link ↗
  11. Partial Validation patterns.arcitura.com

    Validates only relevant data for improved performance.

    site link ↗
  12. Partial State Deferral patterns.arcitura.com

    Temporarily defers a portion of service state data to optimize memory and resource consumption.

    site link ↗
  13. Non-Agnostic Context patterns.arcitura.com

    Encapsulates single-purpose, non-reusable logic in a dedicated service so it can still be governed within the inventory.

    site link ↗
  14. Multi-Channel Endpoint patterns.arcitura.com

    Provides multiple communication channels to access legacy systems.

    site link ↗
  15. Microservice Deployment patterns.arcitura.com

    Deploys services as independent, autonomous units for improved scalability and resilience.

  16. Micro Task Abstraction patterns.arcitura.com

    Breaks down tasks into smaller, more granular tasks for easier management.

  17. Metadata Centralization patterns.arcitura.com

    Centralizes metadata to reduce duplication and improve consistency.

    site link ↗
  18. Messaging Metadata patterns.arcitura.com

    Uses metadata to describe and manage service messages.

    site link ↗
  19. Message Screening patterns.arcitura.com

    Screens messages for malicious content.

    site link ↗
  20. Logic Centralization patterns.arcitura.com

    Centralizes business logic within a service layer to reduce redundancy and promote consistency.

  21. Lightweight Endpoint patterns.arcitura.com

    Provides a lightweight endpoint for resource access.

    site link ↗
  22. Legacy Wrapper patterns.arcitura.com

    Wraps legacy systems to expose them as services.

    site link ↗
  23. Inventory Endpoint patterns.arcitura.com

    Defines a standard endpoint for accessing inventory resources.

    site link ↗
  24. Intermediate Routing patterns.arcitura.com

    Uses intermediate routing nodes to improve performance and flexibility.

    site link ↗
  25. Idempotent Capability patterns.arcitura.com

    Ensures that the same action can be performed multiple times without changing the system state.

    site link ↗
  26. Functional Decomposition patterns.arcitura.com

    Breaks down services into smaller, more manageable components.

  27. File Gateway patterns.arcitura.com

    Provides a gateway to access legacy file-based systems.

    site link ↗
  28. Exception Shielding patterns.arcitura.com

    Protects against security vulnerabilities through proper handling of exceptions.

    site link ↗
  29. Event-Driven Messaging patterns.arcitura.com

    Uses events to trigger service invocations and reduce coupling.

    site link ↗
  30. Entity Linking patterns.arcitura.com

    Links related resources to enable navigation and discovery.

    site link ↗
  31. Entity Abstraction patterns.arcitura.com

    Abstracts data entities to simplify data access and reduce coupling.

    site link ↗
  32. Enterprise Inventory patterns.arcitura.com

    Establishes a single, enterprise-wide inventory of services to maximize reuse and recomposition.

    site link ↗
  33. Endpoint Redirection patterns.arcitura.com

    Redirects clients to alternative endpoints.

    site link ↗
  34. Dual Protocols patterns.arcitura.com

    Allows the service inventory to support two communication protocols to balance interoperability and performance.

    site link ↗
  35. Domain Inventory patterns.arcitura.com

    Identifies and categorizes the types of services within a particular domain.

    site link ↗
  36. Distributed Capability patterns.arcitura.com

    Breaks down a service capability into smaller, more manageable pieces.

    site link ↗
  37. Direct Authentication patterns.arcitura.com

    Authenticates clients directly.

    site link ↗
  38. Decoupled Contract patterns.arcitura.com

    Decouples service contracts from their implementation for improved flexibility.

    site link ↗
  39. Decomposed Capability patterns.arcitura.com

    Breaks down a service capability into smaller, more manageable pieces.

    site link ↗
  40. Data Origin Authentication patterns.arcitura.com

    Authenticates the origin of a message.

    site link ↗
  41. Data Model Transformation patterns.arcitura.com

    Transforms data models to enable interoperability.

    site link ↗
  42. Data Format Transformation patterns.arcitura.com

    Transforms data formats to enable interoperability.

    site link ↗
  43. Data Confidentiality patterns.arcitura.com

    Ensures data confidentiality in a distributed environment.

    site link ↗
  44. Cross-Domain Utility Layer patterns.arcitura.com

    Establishes a common utility services layer shared across multiple domain inventories.

    site link ↗
  45. Contract Denormalization patterns.arcitura.com

    Allows a service contract to include redundant capabilities to accommodate consumers with different data exchange requirements.

    site link ↗
  46. Contract Centralization patterns.arcitura.com

    Centralizes service contracts to improve consistency and reduce duplication.

    site link ↗
  47. Content Negotiation patterns.arcitura.com

    Negotiates the content format between clients and servers.

    site link ↗
  48. Containerization patterns.arcitura.com

    How can an environment be provided with maximum support for services with high-performance recovery and scalability requirements?

    site link ↗
  49. Concurrent Contracts patterns.arcitura.com

    Allows multiple versions of a service contract to coexist simultaneously.

    site link ↗
  50. Composition Autonomy patterns.arcitura.com

    Enables services to act autonomously within a composition.

    site link ↗
  51. next page of items loading…