Service Broker
Service Broker
Service Broker is an asynchronous messaging framework with which you can implement scalable, distributed, highly available, reliable and secure database applications.
Message Types — Well-formed XML
Contracts — A contract is therefore an agreement that states which message types a service can send and which message types a service can accept.
Queues — After you have defined your message types and your contracts, you have to create the queues for storing incoming messages in Service Broker.
Service Programs — The last object, a service program, is a stored procedure that gets executed when new messages arrive.
What is Open Service Broker API (OSBA)
Open Service Broker API defines a specification for listing, provisioning, accessing and deprovisioning cloud services. It have implementations for many cloud providers. Each implemenetation have a list of services that can be managed:
OSBA for Azure: Azure SQL Database, Azure Database for PostgresSQL / for MySQL, Azure CosmosDB, Azure Redis Cache, Azure Service Bus, Azure Storage, Azure Event Hubs, Azure Key Vault.
Service Broker for AWS: Amazon Relational Database Service (Amazon RDS), Amazon EMR, Amazon DynamoDB, Amazon Simple Storage Service (Amazon S3), and Amazon Simple Queue Service (Amazon SQS).
GCP Service Broker: BigQuery, Cloud Bigtable, Pub/Sub, Cloud Spanner, Cloud SQL, Cloud Storage.
The Open Service Broker API project allows independent software vendors, SaaS providers, and developers to easily provide backing services to workloads running on cloud-native platforms such as Cloud Foundry and Kubernetes.
A backing service is any service the app consumes over the network as part of its normal operation. Examples include datastores (such as MySQL or CouchDB), messaging/queueing systems (such as RabbitMQ or Beanstalkd), SMTP services for outbound email (such as Postfix), and caching systems (such as Memcached).
Cloud Foundry is an open-source project with an open contribution and open governance model that gives users maximum flexibility to avoid vendor lock-in. We help to oversee a trustworthy community of diverse minds who have come together to tackle all kinds of challenges. More perspectives and divergent thinking mean stronger code.
What are service brokers?
Service brokers manage the lifecycle of services, and platforms interact with service brokers to provision, get access to and manage the services they offer.
Each service broker built to the Open Service Broker API specification has the same intuitive set of lifecycle commands. These commands do useful things such as:
- Fetching the catalog of backing services that a service broker offers
- Provisioning new service instances
- Connecting and disconnecting applications and containers from those service instances
- Deprovisioning service instances
This model provides significant benefits for both development and operations teams:
- Developers can connect their applications and containers to the backing services they need. The operation is the same, regardless of the backing service.
- Operators no longer have to manually provision and delegate access to services. Instead, they simply configure a marketplace of services and service plans. From there, developers can self-serve, reducing the administrative overhead many enterprises face today.
