Re: How stateless are service brokers?

Dr Nic Williams <drnicwilliams@...>

Dmitriy's On Demand Broker looks to be stateless

From: Gareth Smith <gsmith(a)>
Sent: Friday, October 20, 2017 5:11:40 PM
To: Discussions about Cloud Foundry projects and the system overall.
Subject: [cf-dev] Re: Re: How stateless are service brokers?

I think both the cf rabbitmq broker<> and the on demand broker<> are currently stateless.


On Fri, Oct 20, 2017 at 1:12 AM, Marco Nicosia <mnicosia(a)<mailto:mnicosia(a)>> wrote:

cf-mysql-broker is stateful.

We have a feature of the service plans which defines how much storage a plan may use; this isn't a core feature of MySQL. We leverage the fact that we have a DB at our disposal to remember how much space each service-instance is allowed, and monitor that.

On Thu, Oct 19, 2017 at 5:59 AM Matt McNeeney <mmcneeney(a)<mailto:mmcneeney(a)>> wrote:
Hi all,

Members of the Open Service Broker API<> group are currently asking about how stateless service brokers really are. There are features in the spec (asynchronous<> instance provisioning) and features that we want to get into the spec (allowing platforms to GET<> instances and bindings) that we believe require some degree of statefulness, and so we want to understand this space better before making these changes.

I'm keen to understand from Service Broker authors whether or not the service brokers you have created keep any state (either on their own or by relying on other platform components), and if not, whether or not you currently support or plan to support asynchronous operations (provisioning and binding)?

Many thanks,
CF Services API PM

Marco Nicosia
Product Manager
Pivotal Software, Inc.
c: 650-796-2948<tel:(650)%20796-2948>

Join { to automatically receive all group messages.