Re: How stateless are service brokers?


Marco Nicosia
 

Matt,

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)pivotal.io> wrote:

Hi all,

Members of the Open Service Broker API
<https://www.openservicebrokerapi.org/> group are currently asking about *how
stateless service brokers really are*. There are features in the spec (
asynchronous
<https://github.com/openservicebrokerapi/servicebroker/blob/v2.13/spec.md#asynchronous-operations> instance
provisioning) and features that we want to get into the spec (allowing
platforms to GET
<https://github.com/openservicebrokerapi/servicebroker/pull/333> 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,
Matt
*CF Services API PM*


--
--
Marco Nicosia
Product Manager
Pivotal Software, Inc.
mnicosia(a)pivotal.io
c: 650-796-2948

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.