SUGCON 2015 Modelling

Glass V4, More Info For Your Solution

Mike Edwards Glass

@mikeedwards83@glasslu

Sitecore User Group Conference 2015 1

Glass V4, More Info For Your Solution

ModelingMike Edwards Glass



Hello!


Mike EdwardsSitecore MVP@mikeedwards83@glasslu

Modelling


NOT THIS KIND

Modelling


THIS KIND

Modelling

• Different Patterns• Common Mistakes• Techniques


Common Patterns

• Active Record• Data Mapping• Wrapping


Active Record Pattern

In software engineering, the active record pattern is an architectural pattern found in software that stores in-memory object data in relational databases. The interface of an object conforming to this pattern would include functions such as Insert, Update, and Delete.

- Wiki, Martin Fowler


Active Record Pattern


The Example

Active Record Pattern - Pro’s

Simple to use:


Active Record Pattern - Pro’s

Simple to pass around:


Hidden side effects:

Active Record Pattern - Con’s


Surprise!!Pointless

Active Record Pattern - Cons

Coupled to data source:



Complex:



Hard to test:


How do we mock this??

Ask the FakeDBGuys

Data Mapper Pattern

Data Mapper is a Data Access Layer that performs bidirectional transfer of data between a persistent data store (often a relational database) and an in memory data representation (the domain layer). The goal of the pattern is to keep the in memory representation and the persistent data store independent of each other and the data mapper itself.

- Wiki, Martin FowlerSitecore User Group Conference 2015 16

Data Mapper Pattern


The Example

Data Mapper Pattern

Simple Models


Data Mapper Pattern - Pro’s

Easy Testing



Clear Separation


My World Their World


Store Anywhere



Clear Control


Hello!!

Data Mapper Pattern - Con’s

Map Unused Data



Expensive Upfront



Disconnection from source


Where the hell did youcome from?

Wrappers Models

Wraps the underlying data source and converts the data on demand. The internal model contains a reference to the original data source which it uses to perform data conversion.


Wrappers Models


Wrappers Models - Pro’s

Cheap Up Front


No work done here!

Only accessed propertiesrequire conversion.


Hidden State Changes


What happens if this changes


Hidden State Changes


Are these the same?

Wrappers Models - Con’s

Testing Difficulty


Can’t test becauseof this.

Have to write data conversion code

Need to understandthis

Wrappers Models - Meet my partner

Coupling


I ask for this

Wrappers Models - Meet my partner

Coupling


I get this

Common Problems

• Anemic domain model • Bloated domain model• Skinny domain model• Indiscreet domain model


Anemic Domain Model

Anemic domain model is the use of a software domain model where the domain objects contain little or no business logic (validations, calculations, business rules etc).

- Wiki, Martin Fowler


Anemic Domain Model - Example


Feed Me!!

Anemic Domain Model


Bloated Domain Model

A Bloated Domain Model is the use of a software domain model that contains a large number of properties that are never access or required by the application.

- Mike E



Fixed


Skinny Domain Model

A Skinny Domain Model is the use of a software domain model that contains one or very few properties.

- Mike


Skinny Domain Model

Skinny Domain model


Skinny Domain Model

Fixed


USE THE RAW API!

Indiscreet Domain Model

A Indiscreet Domain Model is the use of a software domain model that exposes all it’s properties publically even if they should or should not be accessed by external code.

- Mike E



Fixed


Techniques


• Interface Models• Template Models• Rendering Models• MVC• MVP

Interface Models


Domain models defined using interfaces only. Interface are dynamically implemented at run time using a proxy framework.

Interface Models


Interface Models

• Multiple Inheritance• Very little code

• Often Anemic• Indiscreet


Interface Models


Spoofing Logic

Template Models


Template Models

• Code generation friendly• Easy to sync• Bloated• Indiscreet• Anemic


Rendering Models


Rendering Models

• Use case specific• Minimum number of properties• Custom methods• Model explosion• Magic Properties Problem• Skinny


MVC Models

Model–view–controller (MVC) is a software architectural pattern for implementing user interfaces. It divides a given software application into three interconnected parts, so as to separate internal representations of information from the ways that information is presented to or accepted from the user.

- - WikiSitecore User Group Conference 2015 58

MVC Models

What do we pass to the view?


MVC Models

The View Model• Explicitly defines the contract• Easy to expand• Use convention• Separates Domain from View


MVC Models


Easy to find

MVC Models


Easy to identify!

And don’t forget MVP!

MVP is a user interface architectural pattern engineered to facilitate automated unit testing and improve the separation of concerns in presentation logic.

- Wiki


MVP


MVP is similar to MVC


MVP or MVC?


Finished!!Questions?


68

Find Me:


Mike EdwardsSitecore MVP


[email protected]

[Reserved for sponsor logo’s]



Thank you

SUGCON 2015 Modelling

Documents

Transcript of SUGCON 2015 Modelling