Many applications are built around a single data model, typically persisted to a data store via an object-relational mapper (ORM) tool. Sometimes you want to have more flexibility, which requires multiple models. Understanding when one model of data just doesn’t fit all use cases is the challenge for the architect. This article discusses some strategies you can use to handle these situations and develop more layered and robust applications, using objects for data modeling.

Related Content:

• NoSQL Data Modeling
• How to Draw an Architectural Data Model in UML
• Types and Uses of Data Models