The world of software development is constantly evolving, and one of the most exciting trends is the emergence of intelligent, agentic workflows. These workflows can automate complex tasks, make decisions, and interact with various systems. But how do you effectively build, package, and reuse these powerful capabilities within your own applications? This is where Services-as-Software comes in, and the .do platform is leading the charge.
Forget bulky applications or complex monolithic systems. Services-as-Software are self-contained, intelligent agentic workflows that are packaged and exposed as simple, reusable software services. Think of them as building blocks you can easily integrate into your projects, just like calling an API or using a library.
On the .do platform, these are known as .do Services. They encapsulate the entire logic of an agentic workflow, including its inputs, outputs, state management, and security. This allows you to focus on building the core intelligence of your service, while the platform handles the complexities of packaging, deployment, and discoverability.
The .do platform provides a comprehensive developer environment designed to make building Services-as-Software intuitive and efficient. You can define your agentic workflows using powerful tools provided by the platform, specifying the sequence of actions, decision points, and integrations. The platform helps you manage inputs and outputs, handle workflow state, and implement robust security measures to protect your service.
Once your workflow is defined, you can seamlessly publish it as a Service-as-Software. This process automatically generates a dedicated API endpoint for your service and makes it available through the .do SDK. This means your intelligent workflow instantly becomes a reusable component that other developers and systems can easily consume.
Consuming a .do Service is designed to be as straightforward as possible. You can integrate them into your existing applications using standard RESTful API calls, or leverage the official .do SDKs available for various programming languages.
Here's a simple example of how you might call a .do Service using the TypeScript SDK:
This code snippet demonstrates how easy it is to instantiate the .do client, provide your API key for authentication, and then call a specific service by its name, passing in the necessary data. The service executes on the .do platform, and the result is returned to your application.
Adopting a Services-as-Software approach offers numerous advantages for developers:
Services-as-Software, powered by the .do platform, are changing the way developers build and deploy intelligent applications. By packaging agentic workflows as reusable software services, you can modularize complex logic, accelerate development, and easily integrate powerful capabilities into your projects.
Ready to start building and consuming Services-as-Software? Explore the developer tools and APIs on the .do platform today and unlock the power of agentic workflows for your projects.
import { DoClient } from '@dotdo/sdk';
async function processData(data: any) {
const client = new DoClient({ apiKey: 'YOUR_API_KEY' });
try {
const serviceResult = await client.services.call('myAccount.processDataService', { inputData: data });
console.log('Service executed successfully:', serviceResult);
return serviceResult;
} catch (error) {
console.error('Error calling service:', error);
throw error;
}
}
// Example usage:
processData({ id: 1, value: 'sample' });