Microservice-based Architecture on the Salesforce1 Platform

 Paul Battisson, MVP, Technical Architect, Mavens Consulting  Sean Harrison, Technical Architect, Mavens Consulting

Paul Battisson Force.com MVP

Technical Architect, Mavens Consulting

@pbattisson

@forcedotcomcast

Sean Harrison Technical Architect, Mavens Consulting

@GizmoForce

Agenda

•  What are microservices anyway? •  Pattern 1 – The Gateway •  Pattern 2 – Synchronous Broker •  Pattern 3 – Asynchronous Broker •  Microservices on Salesforce1

•  Summary •  Q&A

What are microservices anyway?

Break the Monolith Business Capabilities – Products not Projects

Communication RESTful or Message Queues?

•  We will be showing our microservices communicating over a message queue

•  REST is most common pattern for synchronous communication

•  Message Queues for asynchronous

•  We are showing a message queue because:

•  Lots of people may not have seen one

•  Salesforce REST API would be better for REST based microservices architecture

Pattern 1 - The Gateway

Pattern 1 – The Gateway

Pattern 1 – The Gateway

1.  Microservice processes some information that requires interaction with Salesforce

2.  Microservice places message for Salesforce Gateway Microservice on message queue

3.  Gateway Microservice handles message from queue and calls appropriate function(s)

4.  Gateway Microservice functions call out to Salesforce REST API

5.  Salesforce REST API returns response

6.  Gateway Microservice handles and processes response as well as acknowledging processing of message

7.  Acknowledgement (possibly including processed REST API response) routed handled by originating microservice

8.  During processing, Gateway Microservice may place another message on queue to be handled by other microservices

Demo & Code! Please visit https://goo.gl/VsVRjk

The Microservice Part

index1.html

server.js

The Gateway and SFDC Part

server.js

SalesforceService.js

P1_Listener.cls

Pattern 2 – Salesforce Broker Synchronous

Pattern 2 – Salesforce Broker (Synchronous)

Pattern 2 – Salesforce Broker Synchronous

1.  Microservice processes some information that requires interaction with Salesforce

2.  Microservice places message for Salesforce Broker Microservice on message queue

3.  Broker Microservice handles message from queue

4.  Broker Microservice calls custom Broker Apex REST Endpoint

5.  Apex REST endpoint handles message and calls required apex code for message

6.  Broker endpoint responds with output from routed message

7.  Broker Microservice receives response and routes back to originating microservice via acknowledgement

8.  Acknowledgement (including Salesforce API response) handled by originating microservice

Demo & Code! Please visit https://goo.gl/xs3yFJ

Microservice Posts to a Queue

index1.html

server.js

Gateway Microservice Passes Information Through

SalesforceService.js

P2Listener.cls MessageHandlerContact.cls

Pattern 3 – Salesforce Broker Asynchronous

Pattern 3 – Salesforce Broker (Asynchronous)

Microservices on Salesforce1 Doing it on the platform

Microservices on Salesforce1

Demo & Code!

Microservices on Salesforce1

P4_Microservice.cls

Message_QueueTrigger.trigger

Microservices on Salesforce1

P4_Broker.cls

Microservices on Salesforce1

P4_Microservice.cls

Recap

Recap

•  Salesforce can be a first class player in a microservice architecture

•  Your situation will dictate the best pattern(s) to apply

•  Adoption takes time

•  Code samples and information available at: https://github.com/seanhharrison/DF15-microservices

•  We would love your feedback

•  On the session

•  On how you are (or could be!) using microservices

Share Your Feedback, and Win a GoPro!

3 Earn a GoPro prize entry for each completed survey

Tap the bell to take a survey 2Enroll in a session 1

Questions? @pbattisson

@GizmoForce

Thank you