Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scalable Salesforce Integrations on a Shoestring Budget - Dreamforce '19 - Giuseppe Cardace

81 views

Published on

The Salesforce platform offers a multitude of integration options to suit a variety of different needs. And while there are many different factors to consider when choosing the right approach for your integrations, one of the most important ones is budget. In this session, you will learn about a real-world scenario with complex requirements, limited budget and no on-premise infrastructure. The demonstration will cover combining native Salesforce features like Outbound Messaging with external services on AWS and free open source tools to integrate, in near real-time, Salesforce data with more than 10 ERP systems. You will see an end-to-end walkthrough of the solution, which can mostly be configured by admins, requiring limited developer skills. You will also see a live demo and leave with ideas for how to build similar low-cost, scalable integration patterns and adapt them for your own use cases.

Published in: Technology
  • Be the first to comment

Scalable Salesforce Integrations on a Shoestring Budget - Dreamforce '19 - Giuseppe Cardace

  1. 1. Scalable Salesforce Integrations on a Shoestring Budget @gcardax giuseppe.cardace@acrotec.ch Giuseppe Cardace, Group IT Manager sebastien.virtel@acrotec.ch Sébastien Virtel, VP of Sales
  2. 2. Forward Looking Statement Statement under the Private Securities Litigation Reform Act of 1995: This presentation contains forward-looking statements about the company’s financial and operating results, which may include expected GAAP and non-GAAP financial and other operating and non- operating results, including revenue, net income, diluted earnings per share, operating cash flow growth, operating margin improvement, expected revenue growth, expected current remaining performance obligation growth, expected tax rates, the one-time accounting non-cash charge that was incurred in connection with the Salesforce.org combination; stock-based compensation expenses, amortization of purchased intangibles, shares outstanding, market growth and sustainability goals. The achievement or success of the matters covered by such forward-looking statements involves risks, uncertainties and assumptions. If any such risks or uncertainties materialize or if any of the assumptions prove incorrect, the company’s results could differ materially from the results expressed or implied by the forward-looking statements we make. The risks and uncertainties referred to above include -- but are not limited to -- risks associated with the effect of general economic and market conditions; the impact of geopolitical events; the impact of foreign currency exchange rate and interest rate fluctuations on our results; our business strategy and our plan to build our business, including our strategy to be the leading provider of enterprise cloud computing applications and platforms; the pace of change and innovation in enterprise cloud computing services; the seasonal nature of our sales cycles; the competitive nature of the market in which we participate; our international expansion strategy; the demands on our personnel and infrastructure resulting from significant growth in our customer base and operations, including as a result of acquisitions; our service performance and security, including the resources and costs required to avoid unanticipated downtime and prevent, detect and remediate potential security breaches; the expenses associated with new data centers and third-party infrastructure providers; additional data center capacity; real estate and office facilities space; our operating results and cash flows; new services and product features, including any efforts to expand our services beyond the CRM market; our strategy of acquiring or making investments in complementary businesses, joint ventures, services, technologies and intellectual property rights; the performance and fair value of our investments in complementary businesses through our strategic investment portfolio; our ability to realize the benefits from strategic partnerships, joint ventures and investments; the impact of future gains or losses from our strategic investment portfolio, including gains or losses from overall market conditions that may affect the publicly traded companies within the company's strategic investment portfolio; our ability to execute our business plans; our ability to successfully integrate acquired businesses and technologies, including delays related to the integration of Tableau due to regulatory review by the United Kingdom Competition and Markets Authority; our ability to continue to grow unearned revenue and remaining performance obligation; our ability to protect our intellectual property rights; our ability to develop our brands; our reliance on third-party hardware, software and platform providers; our dependency on the development and maintenance of the infrastructure of the Internet; the effect of evolving domestic and foreign government regulations, including those related to the provision of services on the Internet, those related to accessing the Internet, and those addressing data privacy, cross-border data transfers and import and export controls; the valuation of our deferred tax assets and the release of related valuation allowances; the potential availability of additional tax assets in the future; the impact of new accounting pronouncements and tax laws; uncertainties affecting our ability to estimate our tax rate; the impact of expensing stock options and other equity awards; the sufficiency of our capital resources; factors related to our outstanding debt, revolving credit facility, term loan and loan associated with 50 Fremont; compliance with our debt covenants and lease obligations; current and potential litigation involving us; and the impact of climate change. Further information on these and other factors that could affect the company’s financial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other filings it makes with the Securities and Exchange Commission from time to time. These documents are available on the SEC Filings section of the Investor Information section of the company’s website at www.salesforce.com/investor. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements, except as required by law.
  3. 3. Sébastien Virtel VP of Sales sebastien.virtel@acrotec.ch
  4. 4. • Context: Acrotec use-case scenario • Technical Solution • Live demo • Q&A Agenda
  5. 5. Context Acrotec use-case scenario
  6. 6. 1 Group | 3 Divisions | 20 Companies Watchmaking & Jewelry 48% of revenues Movement components Cases Machines and tooling Surface treatment Jewelry Medtech 22% of revenues Trauma Spine Dental Surgery Precision High Tech 30% of revenues Electronics Automotive Aeronautics & Defense
  7. 7. Acrotec Group History Creation of 20092001 2006 2014 2016 2017 2018 2019
  8. 8. Technical Side  Single Salesforce org for all subsidiaries (~ 70 Salesforce Users) • Need to cooperate but also to keep data segregated by company on most objects (=Private Org-Wide Defaults + Sharing Settings)  Very limited amount of IT employees • ~1 IT person per company (sometimes external providers only)  No on-premise infrastructure  Low IT budget  15+ Legacy & non-mainstream ERP systems Context
  9. 9. Our use-case Source: Management Acrotec Group 20 independent companies cooperating on Salesforce +15ERP Systems 33% of YoY growth
  10. 10. Giuseppe Cardace Group IT Manager giuseppe.cardace@acrotec.ch @gcardax
  11. 11. “We need to transfer data from Salesforce to our ERPs in real- time… we can’t wait 5 minutes! - Any End-User
  12. 12. • Why do you need it? • How many ERPs? • Data Volumes? • Data change frequency? Heroku Connect with ERPs reading PostgreSQL DB? Which skills and system capabilities do we have on both ends? Architect Point-to-Point, Hub & Spoke, Service Bus Scheduled ETL? Full-fledged ESB? Wait a minute! What’s the available budget?
  13. 13. Business Sponsor So… What’s the available budget? Technical Architect
  14. 14. Technical Solution A sustainable low-code & low-budget architecture
  15. 15. Integration from Salesforce to ERPs via shared DB High-level Architecture
  16. 16. Integration from Salesforce to ERPs via shared DB Detailed Architecture
  17. 17. Salesforce: Outbound Messaging Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19  Declarative: Admins can configure it  Contract-First: Uses WSDL, SOAP & XML  Sends asynchronous notifications from workflow rules or approval processes  Bulkified: up to 100 notifications /msg  Automatic retries for 24 hours  Monitoring tool  Independent retries: Message order not guaranteed  Because a message may be delivered more than once, your listener client should check the notification IDs delivered in the notification before processing.  Since it’s Workflow-based, it’s limited to Inserts and Updates Benefits Concerns / Tradeoffs
  18. 18. AWS: API Gateway  Declarative or Programmatic  Integrates with other services, e.g.: • run AWS Lambda • pass payload to SQS, SNS, etc. • start AWS Step Functions  Autoscale & Configurable Resiliency  Authentication  Optimized for REST services with JSON payloads  Workaround: wrap SOAP XML message as a String into a JSON object Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19 Benefits Concerns / Tradeoffs
  19. 19. AWS: SQS - “Standard”  At-Least-Once Delivery (Standard): A message is delivered at least once, but occasionally more than one copy of a message is delivered.  Best-effort ordering (Standard): Queue triggers are not supported by FIFO queues  Message size: max 256 KB/message (invoiced in 64 KB-chunks) → Save by message bulkification Standard Queue with Triggers Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19  Declarative or Programmatic  Configurable retention period: default 4 days [1 min to 14 days]  Unlimited Throughput (Standard)  No upfront costs → Pay per use  Server Side Encryption  Dead Letter Queues (DLQ) Benefits Concerns / Tradeoffs
  20. 20. AWS: Lambda  Requires some coding skills � Save implementation and maintenance time by using some graphical tool that generates robust code! Serverless compute Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19  Auto-scaled serverless functions  Built-in multi AZ fault tolerance: no maintenance windows or downtimes  No upfront costs → charged by 100ms  Reuse: pass Context in Env variables  Flexible resources: config memory & timeout period→ proportional CPU, network, disk I/O Benefits Concerns / Tradeoffs
  21. 21. «Write» your code faster  Free, open source, Apache license  Graphical design environment (Eclipse-based)  Hundreds of connectors: Salesforce, SAP, Marketo, Oracle, MS SQL server, PostgreSQL, MySQL, AWS, Azure, Dropbox, Box, SMTP, FTP/SFTP, etc.  File management: open, move, zip  Control and orchestrate data flows  Map, aggregate, sort, enrich, and merge data  The executable JAR produced by Talend cannot run as-is in AWS Lambda  Use Amazon SDK in a small wrapper Java application; add the JAR to the build path and execute the Talend job’s runJob method Talend Open Studio for Data Integration Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19 Benefits Concerns / Tradeoffs
  22. 22. Talend Open Studio for Data Integration What does it look like? (1/3) Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19
  23. 23. Talend Open Studio for Data Integration What does it look like? (2/3) Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19
  24. 24. Talend Open Studio for Data Integration What does it look like? (3/3)
  25. 25. AWS: RDS PostgreSQL  Requires some PostgreSQL-specific knowledge to create users, tables, views, triggers, and especially configure row-level security policies Serverless Database Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19  Fault-tolerant: Multi-AZ deployments with automatic switch in case of issues  Automatic software patching  Scalable: • Push-button compute scaling: up to 32 vCPUs and 244 GiB RAM • Easy storage scaling: no downtimes Benefits Concerns / Tradeoffs
  26. 26. AWS: CloudWatch (Logs & Monitoring) Unified Log Collection and Analysis Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19  Custom Log Retention Periods by service and lambda function  Built-In Metrics for the main services  Set Alert thresholds on key metrics  Create your own dashboards! Benefits
  27. 27. What about costs? Service Avg Monthly Cost Amazon API Gateway ~ 0.5 USD AWS SQS (1M requests/month are free) ~ 5 USD AWS Lambda (1M requests/month are free) ~ 1 USD AWS RDS PostgreSQL (64 GB SSD) ~ 75 USD AWS CloudWatch Logs *(incl. several metrics, alerts & logs from other solutions we have on AWS) ~ 25 USD* Total < 120 USD  Low amount of transactions → shift from very high fixed recurring costs to a “pay per transaction” model  Pay only for what you use (RDS runs 24/7)  Keep budget under control with configurable alerts  Free tiers available  Cost Simulation Tool: https://calculator.s3.amazonaws.com/index.html Scalable Salesforce Integrations on a Shoestring Budget – Giuseppe Cardace, Sébastien Virtel - Dreamforce ‘19 Benefits
  28. 28. Live Demo
  29. 29. Now it’s your turn! Adapt the presented architecture to your own needs, follow the step-by-step instructions on my blog to reproduce the demo and share your experience! https://bit.ly/sfdcarchitect
  30. 30. Q&A

×