Serverless Extensibility

transcript

Serverless Extensibility from Within

Glenn Block, Auth0 Extend (@gblock)glenn.block@auth0.com

1990s – 2000s: Extensibility was easier when it was your servers

https://www.flickr.com/photos/darkseed/41932055

2006: Cloud and SaaS changed everything(and brought new challenges)

https://www.azernews.az/media/pictures/data_center_150614.jpg

2007: Webhooks revolutionized the web

"The idea here is to create new infrastructure. New opportunities. I've been thinking a lot about the possibilities of a web hook enabled web, and it makes me really excited."

Jeff Lindsey

The SaaS doesn't have to build the customizations The doesn't have to host them Code runs completely isolated and secure from the SaaS and from other

customers Customers can choose any language / stack to implement Relatively straightforward to implement*

SaaSWebhookEndpoint

Webhook invocation

Webhooks revolutionized Saas Extensibility

Continue Asynchronously

Webhooks also brought pain….to the customer

The customer has to build it. A Webhook is a service.

The customer has to host it The customer has to run and monitor it The customer has to pay for it

2015: Serverless

https://www.flickr.com/photos/jeepersmedia/13943819389

The customer still has to build it, but Webhooks are much easier to implement The Serverless provider is the host The customer has to monitor it The customer has to pay for it

SaaSServerlessProvider

Webhook invocation

Serverless functions are an evolution for Webhooks

Continue Asynchronously

But for SaaS extensibility,the costs still inhibit their usage

2017 - Serverless Extensibility, The next frontier

Serverless Extensibility, extensibility from within

Serverless Extensibility

A SaaS product directly invokes a Serverlessplatform to handle runtime execution of 3rd party extensions

SaaSServerlessProvider

Webhook invocation

Synch or Asynchronous

In productCode Editor

SaaS Product

Hook points within the product for extensibility An in-line code editor for creating extensions Templates for common extensions A Serverless runtime for securely executing 3rd

party code

Twilio

Stamplay

http://www.plexure.com/plexure-blog/2017/6/1/going-serverless-on-azure

Plexure

https://auth0.com/extend

Customer Benefits

Quicker ramp up. More approachable / does not need to be a traditional developerNo need to worry about hosting or signing up for a separate accountThe SaaS handles monitoringThey pay little to nothing

SaaS Benefits

All the benefits of WebhooksExperience can be more tailored to the needs of the customerHigher retention / stickier customersCan even enable sales engineers / help closing dealsGreater support visibility

Concerns

Not every customer wants to codeLack of visibility, code getting scattered (lost), "Dude, where's my

function?"VersioningDebuggingSecurityVendor lock-in

Serverless Extensibility: https://auth0.com/blog/why-is-serverless-extensibility-better-than-webhooks

Auth0 Extend:https://auth0.com/extend ZERO CRM:https://github.com/auth0/extend Twilio functions: https://www.twilio.com/functions Stamplay: https://codeblocks.stamplayapp.com Plexure: http://www.plexure.com

Where to learn more

Thanks!

Glenn Block, Auth0 Extend (@gblock)glenn.block@auth0.com

Serverless Extensibility

Technology