Slides of the 'Design patterns in Javascript' talk in @MadridJS Code from talk can be found in: https://github.com/tcorral/DesignPatterns_code Running examples in: http://tcorral.github.com/Design-Patterns-in-Javascript/ Code of examples in: https://github.com/tcorral/Design-Patterns-in-Javascript

4. Someone has already solved
your problems.

5. • Abstract those that vary.
• Program to an interface not an
implementation.
• Favor composition over inheritance.
• Strive for loosely coupled designs
between objects that interact.
• Classes should be open for extension
but closed for modification.
• Depend on abstraction. Do not
depend on concrete classes.

7. Restricts the instanciation of a class to one object.

11. Avoids polluting globals.

14. Allow to use ‘function’ to obtain new objects.

17. Used to clone objects.
In Javascript is used to create inheritance.

20. Decouple parts of the code in modules.
Avoid failing your full application for some little
error in one module.

23. Allows to execute more than one method at the
same line.
Only one instance of object is needed.

26. Overwritte the behaviour of one method/function
to reduce time on further executions.
Ideal for updates.

29. Memoize the executions that have been done.
Reduce time on expensive jobs.

31. Nullify

32. Removes all references to local variables to avoid
memory leaks.

35. Removes all references to local variables to avoid
memory leaks when the method/function
returns something.

37. Adapter

38. Converts the interface of a class into another
the clients expect.
Lets classes work together that couldn't otherwise
because of incompatible interfaces.

41. Decorator

42. Attach additional responsibilities to an object
dynamically.
Decorators provide a flexible alternative to
subclassing for extending functionality

45. Factory

46. Defines an interface for creating an object, but
lets subclasses decide which class to instanciate.
Factory Method lets a class defer instanciation
to subclasses.

49. Observer

50. Defines a one-to-many dependency between
objects so that when one object changes state,
all its dependents are notified and updated
automatically.

53. Command

54. Encapsulates a request as an object, thereby letting
you parameterize other objects with different
requests, queue or log requests, and support
undoable operations.

57. Facade

58. Provides a unified interface to a set of interfaces
in a subsystem.
Defines a higher-level interface that makes the
subsystem easier to use

61. Mediator

62. Defines an object that encapsulates how a set of
objects interact.

65. State

66. Allows an object to alter its behavior when its
internal state changes.
The object will appear to change its class.

69. Strategy

70. Defines a family of algorithms, encapsulates each
one, and makes them interchangeable.

74. Compose objects into tree structures to represent
part-whole hierarchies.
Lets clients treat individual objects and
compositions of objects uniformly.

78. Separates elements of the application in layers.
Logic, data and views are separated.

79. M.V.C

80. M.V.C

81. M.V.V.M

84. http://bit.ly/softhire