Basic Knowledge

Essential knowledge articles on Connect SDK

Agent and Skills Guide

How to route tasks to the correct agents: learn which agents own specific front end/back end tasks
How to apply skills across the SDLC (Software Development Lifecycle)
How to troubleshoot and operate the system
When to use natural language vs slash commands: Use natural language when focusing on outcomes vs specific slash commands when precise control is needed

Handler Prioritization: Customize execution order by assigning priorities during startup.
Message Handling Protocols: Follow specific rules for retries, dead letter queue forwarding, and managing multiple items within a message.
Implementation Guidelines: Adhere to guidelines, use annotations like @HandlerInfo and @Component, and configure routes. Extensibility is seen in job handlers, configuration handlers, and product availability enrichments.
Receiving External Messages: Support diverse methods, including HTTP requests with authentication filters and external listeners like SQS and Kafka. Custom controllers enhance authentication through the SDK's security module.

Connect SDK helps partners and customers quickly start building ad hoc connectors with consistency, better security, and short implementation time.
A deployed Connect SDK-based integration simplifies middleware setup and support
It offers incredible flexibility in building synchronous and asynchronous endpoints with a common credential, logging, and configuration interface
In regards to hosting responsibility, any connector built using Connect SDK is cloud-agnostic, and the integration layer is still owned and maintained by the solution integrator, becoming part of the project codebase.

The Connect SDK architecture consists of core, cloud, and additional libraries, enabling the building and extension of connectors.
Key features include configurations, a secret manager for sensitive information, a scheduler for periodic operations, listeners/subscribers, web services/webhooks, an event log, product availability options, and SDK handlers for custom business logic.
The message lifecycle follows a specific flow, and there are two integration approaches: Pull and Push. The SDK offers patterns for scheduled operations and receiving external requests, and it includes dead letter queues, metrics, and logs for monitoring and observability.
Build and deployment use SpringBoot, generating a deployable JAR with an embedded Tomcat.