design patterns every salesforce isv needs to know
TRANSCRIPT
Design Patterns Every ISV Needs to KnowAndrey Volosevich
Senior ISV Technical Evangelist
@andreyvol
Mac Anderson
CTO, Fonteva
@macscloud
Ross Belmont
Chief of UX, Appiphony
@rossbelmont
Agenda: Design Patterns Every ISV Needs to Know
• Top Patterns in 2014
• Architecting Large Apps (Mac Anderson, Fonteva)
• Examples from other apps (Ross Belmont, Appiphony)
• Q & A
Two Examples• Secure testing of external web services• Importing a diverse data set while architecting for flexibility
Benefits of This Approach• The app references the correct endpoint at the correct time• Only you (as the ISV) can specify the external endpoint
– If customers configured it themselves, there would be a support burden– No one can set the endpoint maliciously for a “man in the middle” attack
• Swapping the endpoints is simple (just install the extension package)• The extra “testing flag” object doesn’t pollute customer environments
• Creates different marketing campaigns targeted at alumni of specific universities
Different Types of Customers
• Drives marketing based on traditional demographic segmentation– Age– Gender
Benefits of This Approach• Customers can add exactly what they want to the Contact record and layout, and nothing more
• Reporting is simplified by flattening down to the Contact record• A Dossier can be attached to Leads, etc. in the future• Easy to serve new marketing initiatives in the future
– Recent grads vs. 20 year alumni, for example (incorporating Age)