Salesforce1 lightning dev week UYSDUG 2015 - Lightning Connect

Salesforce1 lightning dev week UYSDUG 2015 - Lightning Connect

• 1.
  Lightning Connect Connect andaccess data from external sources March 12th 2015
• 2.
  Aldo Fernandez Technical Consultant @aldoforce
• 3.
  Safe Harbor Safe harborstatement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, risks associated with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal quarter ended July 31, 2011. This document and others are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
• 4.
  Follow UYSDUG forthe latest news @uysdug #uysdug /Uruguay-Salesforce-Developer-User-Group/ www.uysdug.com
• 5.
  Agenda ▪ Data Integration:the golden niche ▪ Traditional approach problem ▪ Real-time data integration ▪ OData protocol: the web SQL ▪ External Objects works as custom objects ▪ Demo ▪ Pros, Cons and Limitations ▪ Lightning Connect Roadmap
• 6.
  Data Integration: thegolden niche ▪ 28% data integration ▪ Inbound / Outbound ▪ One-way / Bidirectional ▪ Target: ▪ Cloud to Cloud ▪ Cloud to Ground ▪ Ground to Cloud ▪ Mashups, Callouts, DataLoader, SOAP, REST, … (too many items to mention) Facts from Consulting world
• 7.
  Traditional approach problem Salesforceorg External data source RDBMSApex class API Callout (read/write) SObjects ▪ Custom implementation (code) ▪ Data duplication ▪ Space consuming ▪ Synchronization ▪ Re-inventing the wheel
• 8.
  Real-time data integration Salesforceorg External data source RDBMS ODataService LightningConnect OData protocol SObjects External Objects ▪ Declarative implementation (no code) ▪ Real-time access ▪ Data stored outside Salesforce ▪ Always up to date data ▪ Transform external data into NATIVE objects*
• 9.
  OData protocol: theSQL for web ▪ Defines the best practices for building and consuming RESTful APIs ▪ Allows to forget about defining: ▪ Request/Response headers ▪ Status codes ▪ HTTP methods ▪ URL conventions ▪ Media types / payload format ▪ OData metadata: powerful generic service ▪ Check www.odata.org for more information
• 10.
  OData protocol: theSQL for web
• 11.
  What External DataSources are Supported? Any Data Sources that can publish data in Open Data (OData) 2.0 protocol ▪ Commercial Packages – SAP Netweaver Gateway – Microsoft SQL Server, Dynamics CRM/NAV, 
 Azure Table Services – IBM Websphere exTreme Scale – Heroku Connect External Objects – Oracle Open XDX ▪ DIY Data Producer – .Net WCF Data Services, Java (Apache Olingo, odata4j), NodeJS ▪ Many more via partners
• 12.
  External objects worksas custom objects
• 13.
  DEMO: Lightning Connect
• 14.
  Pros, Cons andLimitations ✗ Formula and Roll-up Summary Fields ✗ Triggers, Workflow, Approvals, Process ✗ Validation Rules ✗ Field History Tracking ✗ Notes, Attachments ✗ Read-only (GA Spring’15) ✗ Field accessibility/Sharing ✗ Lookups only ✗ Reports ✗ 10k queries p/hr (EE, XE, UE) ✓ Tabs ✓ List Views ✓ Detail Pages ✓ Chatter Feeds ✓ Visualforce pages with standard or custom controllers ✓ Apex SObject types ✓ REST/SOAP API access ✓ SOQL and SOSL queries from Apex or API ✓ Available on Salesforce1 Mobile Platform ✓ Package friendly
• 15.
  Pros, Cons andLimitations
• 16.
  Lightning Connect Roadmap ▪Read-only access is GA in Spring ‘15 ▪ Pilot in Spring ’15 – Read/write capability – Real-time cross-org access – Apex Connector library to develop custom connectors ▪ FUTURE* ▪ OData 4.0 – Support for triggers ▪ Custom Reports for External Objects * Safe Harbor
• 18.
  Thank You! Lightning Connect Connectand access data from external sources Salesforce1 Lightning Developer Week March 12, 2015 #UYSDUG Aldo Fernandez Technical Consultant @aldoforce #lightningdevweek #uysdug