Some weeks ago, in this post, I tried to solve one of the questions that was asked to me in London’s Calling presentation about how to unit test Lightning Connect apps. There was still another question in the session that encouraged me to perform an investigation on the differences in performance of using a Lightning Connect custom adapter vs implementing the same behaviour through REST callouts.
The investigation has consisted of performing a set of measures using three different scenarios: REST Callouts, Lightning Connect custom adapter with high-volume external datasource and Lightning Connect custom adapter with no high-volume external datasource. If you don’t know the differences between a high-volume and a no high-volume external datasource, you can take a look at this post.
Continue reading “Lightning Connect vs REST callouts”
This month I had the pleasure of presenting at London’s Calling event an application I have done for learning how to use Lightning Connect to retrieve data from an external datasource, which in my case is Google Places API. If you want to know more about the application, here is the video of the presentation.
In the Q&A I had a question about Unit test, that at the moment I couldn’t shown. That question encouraged me to do some unit tests! So, here we have the results.
Continue reading “Unit testing Lightning Connect Apps”
Lightning Connect is a Salesforce feature that allows integrations with external systems. Before Winter 16 release, it only read-only capabilities were provided. Since Winter 16, writable datasources were delivered, making Lightning Connect a very interesting option to think about.
Continue reading “High Data Volume External DataSources”