Packaged Business Capability (PBC)

A Packaged Business Capability (PBC) is a self-contained, composable, and reusable software component that delivers a specific business capability. It follows the principles of modular architecture and composability, enabling enterprises to build flexible and adaptable business solutions.

At Syensqo, we adopt an integration strategy that is driving the creation of a first level of reusable integration components whose role will be to access the canonical resources of the applications part of the ecosystem.

Hence, we have defined this Key Characteristics of PBCs related to integration:
  • Composable: Can be assembled with other PBCs to create larger business solutions.
  • API-First: Offers well-defined APIs for interaction with other PBCs, applications, and services.
  • The event Channels used by the PBC to inform, or to be informed by,  its environment about business events (data changes).
  • Process(or Services) and Data Object provide the same vision by sharing the Data Model, access (API) and interactions with Events


Data Object Service PBC

Extend the design approach to Data

1.Concept Overview

  • Instead of only focusing on business applications, we define PBCs around data objects (e.g., Customer, Order, Product, Invoice).
  • Each Data Object Service PBC encapsulates:
    • Data Model (schema, metadata)
    • APIs (CRUD, search, aggregation)
    • Event Publishing (e.g., "Customer Updated", "Order Created")
    • Security & Access Control (RBAC, OAuth, Data Masking)
  • The ACP serves as a Data Composition Layer, allowing data aggregation, transformation, and data orchestration across multiple services.

2.Key Design Principles

  1. Domain-Oriented Data Objects:
    • Each PBC corresponds to a well-defined data domain (Customer, Order, Payment, Shipment).
  2. Data APIs & Virtualization:
    • Data should be exposed through GraphQL, REST, or gRPC APIs.
    • Virtualization layers (Denodo, Starburst) help unify access to multiple sources.
  3. Event-Driven Data Updates:
    • Data PBCs publish events on event buses (Kafka) to keep consumers in sync.
  4. Composability & Federation:
    • ACP provides a federated data layer that composes multiple Data Object Services dynamically.

3. Integration Model

  • Data Object Services interact with an ACP layer, which provides:
    • Unified Data APIs (API Gateway, GraphQL Federation)
    • Data Streaming & Replication (Change Data Capture - CDC)
    • Data Virtualization & Query Composition

Application Composition Platform (ACP)

An Application Composition Platform (ACP) is an integration and orchestration layer that enables enterprises to assemble, orchestrate, and manage PBCs and other applications into customised business solutions.

Key Characteristics of ACP
  • Composable Application Orchestration: Enables enterprises to combine multiple PBCs and traditional applications into a single workflow.
  • Low-Code / No-Code Tools: Provides visual interfaces and automation tools to compose business applications quickly.
  • Interoperability: Supports integration of both PBC-ready applications and non-PBC applications via APIs, event-driven messaging, and middleware.
  • Scalability & Security: Manages identity, access control, and data security across composed applications.
  • Observability & Monitoring: Provides insights into data flows, performance, and system health.

Integration of PBC-Ready and Non-PBC-Ready Applications

At Syensqo, we often need to integrate modern PBC-based applications with legacy or non-PBC applications. This integration can be achieved through different strategies:

1. API-Based Integration (Synchronous)

  • Expose APIs for non-PBC applications to interact with PBCs via an API Gateway.
  • Use GraphQL or API Aggregators for unifying data access.

2. Event-Driven Integration (Asynchronous)

  • Utilize event brokers (Kafka, Azure Event Grid) to enable decoupled interactions.
  • Non-PBC applications can publish or consume business events.

3. Middleware-Based Integration

  • Leverage Integration Platform Services for connecting non-PBC systems.
  • Implement data transformation and protocol mediation in the Integration Platform

4. Data Virtualization and Streaming

  • Use data platform capabilities: 
    • On virtualization tools to create a real-time data layer.
    • Use Change Data Capture (CDC) and streaming pipelines for data sync.


  • No labels