Re: How stateless are service brokers?


Chris Sterling
 

Hello Matt,

The Spring Cloud Services and Spring Cloud Data Flow for PCF service
brokers maintain state in a relational DB. Both of these projects support
asynchronous operations. One of them does it via RMQ queues while the other
is now using a reactive approach. The state maintained attempts to keep a
life cycles synchronized between our service broker and CF.

Chris Sterling
chris.sterling(a)gmail.com
twitter: @csterwa
linkedin: http://www.linkedin.com/in/chrissterling

On Thu, Oct 19, 2017 at 5:58 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*


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