WSO2 is now Choreo LabsLearn more

Trusted AI Governance
Build

Create agents and AI apps with the tools and languages your teams already use.

Connect

Link agents securely to your APIs, data, models and business systems.

Run

Deploy, observe and operate agents and AI apps reliably at any scale.

Govern

Control identity, access, cost and policy for every agent in production.

Agent Management

Developer Platform

  • API Management Cloud

    Design, secure and publish APIs with governance and analytics built in.

    Sign Up Now
  • Integration Cloud

    Connect apps, data and AI agents with low-code and pro-code integration.

    Sign Up Now
  • Identity & Access Management Cloud

    Secure sign-in and access for customers, partners, workforce and agents.

    Sign Up Now
  • Agent Management Cloud

    Build, run and govern AI agents with full visibility and control.

    Sign Up Now
  • Developer Platform Cloud

    Ship cloud-native apps faster on an internal developer platform.

    Sign Up Now

Self-Hosted

Full control over your stack. Deploy directly to your own servers, bare metal, cloud, or Kubernetes environment. Your data never leaves your perimeter.

Product Downloads
Choreo Labs
AI Governance
Platform
Solutions
Resources
Article

[Blog post] think beyond the ESB – think about the connected business

Many smart architects think of WSO2 as simply an open source ESB vendor, and look towards WSO2 when they need to solve a point integration challenge. As a veteran of the SOA adoption wars, I encourage teams to think beyond the ESB, and consider how to build a connected business.

Enterprise service bus (ESB)

AnEnterprise Service Bus is a key cornerstone of your integration and Services Oriented Architecture, and many teams pursue practical ESB adoption over comprehensive SOA thinking. The teams use the high-performance, lean footprint, and mature WSO2 ESB to fulfill common enterprise integration pattern use cases and pragmatically link service consumers to service providers.

However, many ESB Proof of Concept projects today focus on common use cases and miss the bigger picture; Will the team acquire middleware infrastructure that transforms business dynamics.

Connected business

Spurred on by a confluence of technology developments, including the cloud, mobile, APIs, Big Data, social, and open source, a Connected Business can grow revenue and outperform peers by increasing customer engagement, enhancing productivity, and seizing market opportunity. How does your ESB fit within the business story? and, is an ESB enough?

To be a Connected Business you need an environment that is

Integrated: accelerates interactions inside and outside the organization

–This is where the ESB fits in….

Accessible: reduces interaction friction and cost

–This is where APIs, mobile applications, and on-demand self service (e.g. Integration Platform as a Service iPaaS) fits.

Collaborative: increases engagement and enhances productivity

–This is where social, activity streams, and dashboards driving user engagement fits.

Adaptive: senses business activity and automatically adapts

–This is analyzing the message stream using complex event processing, business activity monitoring, and event driven architecture fits.

How do you build a connected business?

To build a Connected Business, consider utilizing WSO2 Connected components. Many organizations are adopting New IT delivery models based on:

API-centric, event-driven, and Service-Oriented Architecture

Mobile access and user engagement platforms

DevOps practices and Cloud-Native platforms

BigData analytics and business activity monitoring

How are you re-shaping your integration architecture and what are your thoughts about how APIs, mobile, DevOps, Cloud, and BigData influence your ESB evaluation criteria?

Refer to Chris's blog