I recently had the opportunity to deliver my presentation Force.com Data Modeling: The Advantages of Denormalization to a sold out room at Dreamforce ’13. Based on the enthusiastic response and the feedback we received following the presentation about the lack of resources available on Salesforce Platform data modeling, I wanted to post highlights from the session here to give the community a starting point when thinking about designing a Salesforce data model. The session was inspired by a post entitled Force.com Data Modeling – Normalization is Not Your Friend that we published on this blog in 2010.
Posts tagged ‘denormalization’
Force.com makes configuring the data model deceptively simple; creating new custom objects and custom fields can be accomplished with a few clicks and in a matter of seconds. This simplicity can end up creating stifling complexity, because the tendency of developers new to the platform is to apply traditional relational design techniques to the Force.com data model, which is a mistake.
In a traditional relational database, data can be easily stored and retrieved by traversing the relationships between tables. In Force.com, the misuse of relationships by applying normalization patterns can significantly increase coding requirements and create major performance issues due to limitations imposed to govern the use of resources in the multitenant environment.