Skip to content

Developer Hub

The Developer Hub serves as the central nervous system for your integration ecosystem. It promotes reusability, governance, and collaboration by aggregating all interface definitions and data structures into a single, searchable repository.

By centralizing these assets, the platform eliminates silos, ensuring that teams across the enterprise are building against the same contracts and data models.

Event Catalog

AsyncAPI-based Message Registry

In an Event-Driven Architecture (EDA), visibility into what events exist and who consumes them is critical. The Event Catalog provides a unified view of all asynchronous interactions within your enterprise by utilizing a shared asyncapi.json definition.

  • Shared Source of Truth: All projects reference a centralized asyncapi.json file that defines standard Messages, Channels, Servers and Operations.
  • Centralized Discovery: Developers can browse the catalog to find existing events (e.g., OrderCreated, PaymentProcessed) without needing to inspect individual microservice repositories.
  • Contract Consistency: By sharing a single definition file, you ensure that all Producers and Consumers are strictly aligned on topic names and payload structures, preventing runtime errors caused by schema mismatches.
  • Protocol Agnostic: Whether you are using Kafka, RabbitMQ, or MQTT, the catalog documents the interaction model uniformly.

Schema Catalog

Shared Data Definitions

Data consistency is the backbone of reliable integration. The Schema Catalog acts as a centralized repository for JSON Schemas, allowing teams to define data structures once and reuse them across multiple microservices.

  • Write Once, Use Everywhere: Define a Customer or Invoice schema once and import it into any integration project.
  • Single Source of Truth: Prevents data drift by ensuring all services validate against the same master schema.
  • Code Generation: schemas stored here can be used to automatically generate Groovy code snippets for processing in your routes.

API Portal

Unified REST API Discovery

The API Portal transforms your disparate microservices into a discoverable ecosystem. It automatically aggregates documentation for all OpenAPI designed and exposed services running on the platform.

  • Auto-Discovery: As soon as a API is deigned, its definition is exposed to the portal.
  • Live Documentation: Provides an interactive Swagger-like interface for every API, allowing developers to read documentation and understand endpoints without needing access to the source repository.
  • Governance: Provides a high-level view of the API landscape, making it easier to identify duplicate functionality or non-compliant interface designs.

TryOut

Integrated Testing Workbench

Accelerate the feedback loop with TryOut, an integrated testing interface designed specifically for integration developers. It removes the need for context switching between the platform and external tools.

Beyond HTTP

Unlike standard API tools, TryOut interacts directly with the Camel Context, allowing you to trigger internal route logic, not just public endpoints.

  • Postman-like UI: A familiar, user-friendly interface to construct HTTP requests, set headers, and analyze JSON responses.
  • Test REST APIs: Send requests to your deployed OpenAPI endpoints directly from the browser to verify behavior.
  • Test Internal Routes: Trigger specific Apache Camel routes directly. This is essential for testing background processes, timer-based routes, or internal logic that isn't exposed via a public REST API.