The journey from a monolithic architecture to a microservices-based system is a well-trodden path for modern engineering teams. The promise is alluring: independent deployments, improved scalability, and technological flexibility. But as many developers discover, this new world introduces its own formidable challenge: orchestration.
How do you coordinate actions across a dozen distributed services to complete a single business process? How do you handle failures in one service without bringing the entire system to a halt? Suddenly, a simple user signup flow can transform into a complex, brittle web of direct API calls, message queues, and custom retry logic.
This is where the orchestration layer becomes critical. Instead of letting services talk directly to each other in a chaotic mesh, a dedicated orchestrator can conduct them like a symphony. And with the .do agentic workflow platform and our powerful SDKs, you can build that conductor with elegance and ease.
Before we dive into the solution, let's acknowledge the common pain points of microservice orchestration. Does any of this sound familiar?
The .do platform tackles these challenges head-on by allowing you to define your business logic as a centralized, stateful, and resilient agentic workflow.
Think of a workflow as a blueprint for a business process. Instead of your user-service knowing the intricate details of every other service, it simply makes one call: "Hey .do, please run the customer-onboarding-workflow for this new user."
From there, .do takes over, acting as the central orchestrator:
Your individual microservices remain simple and focused on their core responsibilities. All the complex orchestration logic lives in .do, where it's visible, manageable, and version-controlled.
"This sounds great," you might be thinking, "but how do I connect my application to the .do platform?"
The answer is our suite of Software Development Kits (SDKs).
We designed our SDKs to provide a simple, elegant interface for interacting with the .do API from your native programming language. Instead of manually crafting HTTP requests, you get a clean, idiomatic library that makes triggering and managing workflows feel like a native part of your codebase.
Here’s how easy it is to trigger our customer-onboarding-workflow from a Node.js or TypeScript application:
import { Do } from '@do-platform/sdk';
// Initialize the client once in your application
const doClient = new Do({
apiKey: process.env.DO_API_KEY, // Your secret API key
});
async function runCustomerOnboarding(customerData: any) {
try {
console.log('Starting customer onboarding workflow...');
// Trigger the workflow by its name and provide the necessary input
const result = await doClient.workflows.run({
name: 'customer-onboarding-workflow',
input: { customer: customerData },
});
console.log('Workflow successfully started! Run ID:', result.runId);
return result;
} catch (error) {
console.error('Failed to trigger workflow:', error);
// Handle the failure to start the workflow (e.g., log, alert)
}
}
With just a few lines of code, your service has successfully delegated a complex, multi-step, and potentially long-running process to a platform built to handle it. Your service is now decoupled, more resilient, and simpler to maintain.
Migrating from a monolith shouldn't mean trading one kind of complexity for another. By adopting a dedicated orchestration layer, you can reap the benefits of microservices without the headaches of managing their interactions.
The .do platform, combined with our developer-friendly SDKs for TypeScript, Python, and more, provides the perfect solution. You can build, run, and manage your business logic as code, bringing order and visibility to your distributed systems.
Ready to stop building brittle, point-to-point integrations and start orchestrating your services with confidence?
Q: What is the .do SDK?
A: The .do Software Development Kit (SDK) is a set of tools, libraries, and documentation that allows developers to easily integrate the .do agentic workflow platform directly into their own applications.
Q: Which programming languages are supported?
A: We provide official SDKs for popular languages like TypeScript/JavaScript, Python, and Go. Check our developer documentation for the most up-to-date list and community-supported libraries.
Q: How do I get an API key?
A: You can generate an API key from your .do account dashboard. Navigate to the 'API Settings' section to create and manage your keys securely.
Q: Is the SDK free to use?
A: Yes, our SDKs are free to download and use. Usage of the underlying .do platform is subject to our standard pricing plans, which are based on workflow executions and agent usage.