A baryklo design-patterns

AMIR BARYLKO
ADVANCED
DESIGN PATTERNS

Amir Barylko Advanced Design Patterns

WHO AM I?

• Software quality expert

• Architect

• Developer

• Mentor

• Great cook

• The one who’s entertaining you for the next hour!
Amir Barylko Advanced Desing Patterns

RESOURCES

• Email: amir@barylko.com

• Twitter: @abarylko

• Blog: http://www.orthocoders.com

• Materials: http://www.orthocoders.com/presentations


PATTERNS
What are they?
What are anti-patterns?
Which patterns do you use?


WHAT ARE PATTERNS?

•Software design Recipe
•or Solution
•Should be reusable
•Should be general
•No particular language

ANTI-PATTERNS
• More patterns != better design

• No cookie cutter

• Anti Patterns : Patterns to identify failure

• God Classes

• High Coupling

• Breaking SOLID principles....

• (name some)

WHICH PATTERNS
DO YOU USE?
• Fill here with your patterns:


ADVANCED PATTERNS
Let’s vote!


SOME PATTERNS...

• Chain of resp. • List • Composite
Comprehension
• Proxy • State
• Object Mother
• ActiveRecord • Strategy
• Visitor
• Repository • Iterator
• Null Object
• Event Aggregator • DTO
• Factory
• Event Sourcing • Page Object
• Command

CHAIN OF RESPONSIBILITY

• More than one object may handle a request, and the handler
isn't known a priori.

• The handler should be ascertained automatically.

• You want to issue request to one of several objects without
specifying The receiver explicitly.

• The set of objects that can handle a request should be
speciﬁed dynamically


PROXY

• Avoid creating the object until needed

• Provides a placeholder for additional functionality

• Very useful for mocking

• Many implementations exist (IoC, Dynamic proxies, etc)


ACTIVERECORD

• Isa Domain Model where classes match very closely the
database structure

• Each table is mapped to class with methods for ﬁnding,
update, delete, etc.

• Each attribute is mapped to a column

• Associations are deduced from the classes


create_table "movies", :force => true do |t|
t.string "title"
t.string "description"
t.datetime "created_at"
t.datetime "updated_at"
end

create_table "reviews", :force => true do |t|
t.string "name"
t.integer "stars"
t.text "comment"
t.integer "movie_id"
t.datetime "created_at"
t.datetime "updated_at"
end

class Movie < ActiveRecord::Base
validates_presence_of :title, :description
has_many :reviews
end
class Review < ActiveRecord::Base
belongs_to :movie
end


REPOSITORY

• Mediator between domain and storage

• Acts like a collection of items

• Supports queries

• Abstraction of the storage


http://martinfowler.com/eaaCatalog/repository.html

EVENT AGGREGATOR

• Manage events using a subscribe / publish mechanism

• Isolates subscribers from publishers

• Decouple events from actual models

• Events can be distributed

• Centralize event registration logic

• No need to track multiple objects

Channel events
from multiple
objects into a
single object to
s i m p l i f y
registration for
clients


MT COMMONS


EVENT SOURCING

• Register all changes in the application using events

• Event should be persisted

• Complete Rebuild

• Temporal Query

• Event Replay


http://martinfowler.com/eaaDev/EventSourcing.html

LIST COMPREHENSION

• Syntax Construct in languages

• Describe properties for the list (sequence)

• Filter

• Mapping

• Same idea for Set or Dictionary comprehension


LANGUAGE COMPARISON
• Scala
for (x <- Stream.from(0); if x*x > 3) yield 2*x

• LINQ
var range = Enumerable.Range(0..20);
from num in range where num * num > 3 select num * 2;

• Clojure
(take 20 (for [x (iterate inc 0) :when (> (* x x) 3)] (* 2 x)))

• Ruby
(1..20).select { |x| x * x > 3 }.map { |x| x * 2 }


OBJECT MOTHER / BUILDER

• Creates an object for testing (or other) purposes

• Assumes defaults

• Easy to conﬁgure

• Fluid interface

• Usually has methods to to easily manipulate the domain


public class When_adding_a_an_invalid_extra_frame
{
[Test]
public void Should_throw_an_exception()
{
// arrange
10.Times(() => this.GameBuilder.AddFrame(5, 4));

var game = this.GameBuilder.Build();

// act & assert
new Action(() => game.Roll(8)).Should().Throw();
}
}

http://orthocoders.com/2011/09/05/the-bowling-game-kata-ﬁrst-attempt/


VISITOR

• Ability to traverse (visit) a object structure

• Different visitors may produce different results

• Avoid littering the classes with particular operations


http://en.wikipedia.org/wiki/Visitor_pattern#Diagram

NULL OBJECT

• Represent “null” with an actual instance

• Provides default functionality

• Clear semantics of “null” for that domain


class animal {
public:
virtual void make_sound() = 0;
};

class dog : public animal {
void make_sound() { cout << "woof!" << endl; }
};

class null_animal : public animal {
void make_sound() { }
};

http://en.wikipedia.org/wiki/Null_Object_pattern


FACTORY

• Creates instances by request

• More ﬂexible than Singleton

• Can be conﬁgured to create different families of objects

• IoC containers are closely related

• Can be implemented dynamic based on interfaces

• Can be used also to release “resource” when not needed

interface GUIFactory {
public Button createButton();
}

class WinFactory implements GUIFactory {
public Button createButton() {
return new WinButton();
}
}
class OSXFactory implements GUIFactory {
public Button createButton() {
return new OSXButton();
}
}

interface Button {
public void paint();
}

http://en.wikipedia.org/wiki/Abstract_factory_pattern

STRATEGY

• Abstracts the algorithm to solve a particular problem

• Can be conﬁgured dynamically

• Are interchangeable


http://orthocoders.com/2010/04/

DATA TRANSFER OBJECT

• Simpliﬁes information transfer across services

• Can be optimized

• Easy to understand


http://martinfowler.com/eaaCatalog/dataTransferObject.html

PAGE OBJECT

• Abstract web pages functionality to be used usually in testing

• Each page can be reused

• Changes in the page impact only the implementation, not the
clients


public class LoginPage {
public HomePage loginAs(String username, String password) {
// ... clever magic happens here
}

public LoginPage loginWithError(String username, String
password) {
// ... failed login here, maybe because
// one or both of the username and password are wrong
}

public String getErrorMessage() {
// So we can verify that the correct error is shown
}
}

http://code.google.com/p/selenium/wiki/PageObjects

QUESTIONS?


RESOURCES

• Email: amir@barylko.com, @abarylko

• Slides: http://www.orthocoders.com/presentations

• Patterns: Each pattern example has a link


RESOURCES II


RESOURCES III


CLOJURE TRAINING

• When: Nov 6, 7 & 8

• More info: http://www.maventhought.com

• Goal: LearnClojure and functional programming with real
hands on examples


A baryklo design-patterns

More Related Content

Viewers also liked (7)

Similar to A baryklo design-patterns (20)

More from sdeconf (14)

Recently uploaded (20)

A baryklo design-patterns