From the OOP cult in the 90s to now: What happened? What failed? The current combinations with other software architecture paradigms? 1) The Great Hopes About OOP 2) There is no Silver Bullet 3) Case: Epigami Docker OO Infrastructure

1. Object Oriented Programming in
2014: Standard or Legacy?
Mathieu François
@Universitas Bina Nusantara
07/11/2014

2. Did Object Oriented Dominate
Programming?
Introduction
1. The Great Hopes About OOP*
2. There is no Silver Bullet
3. Case: Epigami OO Infrastructure
* Object Oriented Programming

4. Programming: Art or Science?

5. Computer Science vs Programming
The Art of Computer Programming

6. Practices In Real World

7. Who Studies History In Engineering?

8. The Great Hopes About OOP
Software?

9. • Encapsulation
• Polymorphism
• Inheritance
• Class of objects (constructor)
• Instance of class
• Method vs data
• Message passing
• Abstraction
OOP Definition

10. OOP Hype In The Mid-90s

11. Why the OOP Cult?
OOP perceived as the solution for all software
development challenges:
• Code reuse and recycling
• Encapsulation of knowledge
• Isolation of bug impacts
• Design benefits, especially for very large
programs
• Maintenance

12. Pure languages: Ruby, Python, Smalltalk,
Scala, Eiffel
Languages mainly OOP but also have
procedural elements: C++, Java, C#, VB.NET
Languages historically procedural but
extended with OO features: Pascal, VB,
Fortran, Perl, Cobol 2002, PHP
OOP In Almost Every Languages

13. Profusion Of OOD Solutions

14. 20 Years Later… How Did OOP Succeed?

15. OOP For Kernel Development?

16. OOP For Kernel Development
Linux, Windows, OS X… They are still all
based on good old-fashioned C

17. OOP For Web App?

18. OOP For Web App?
Yes: Languages, DOM, JSON
No: Service Oriented Architecture, Event-
Driven Design
More about SOA in a few slides...

20. There Is No Silver Bullet

21. There Is No Silver Bullet
By Fred Brooks (1986), also author of The
Mythical Man month (1975)
Essential Complexity vs Accidental Complexity
Since ‘modern’ languages (Fortran, COBOL), no
real improvement about accidental complexity

23. org 7C00h
jmp short Start ;Jump over the data (the 'short' keyword makes the jmp instruction smaller)
Msg: db "Hello World! "
EndMsg:
Start: mov bx, 000Fh ;Page 0, colour attribute 15 (white) for the int 10 calls below
mov cx, 1 ;We will want to write 1 character
xor dx, dx ;Start at top left corner
mov ds, dx ;Ensure ds = 0 (to let us load the message)
cld ;Ensure direction flag is cleared (for LODSB)
Print: mov si, Msg ;Loads the address of the first byte of the message, 7C02h in this case
;PC BIOS Interrupt 10 Subfunction 2 - Set cursor position
;AH = 2
Char: mov ah, 2 ;BH = page, DH = row, DL = column
int 10h
lodsb ;Load a byte of the message into AL.
;Remember that DS is 0 and SI holds the
;offset of one of the bytes of the message.
;PC BIOS Interrupt 10 Subfunction 9 - Write character and colour
;AH = 9
mov ah, 9 ;BH = page, AL = character, BL = attribute, CX = character count
int 10h
inc dl ;Advance cursor
cmp dl, 80 ;Wrap around edge of screen if necessary
jne Skip
xor dl, dl

24. OOD Is Not the Only Design Approach
Other Approaches or ‘Schools Of Thought’:
• Functional
• Event-driven
• Data-driven
• ‘Unix Philosophy’

25. Object-Relational Impedance
We use Object Relation Mapping (ORM)
because Object DBs didn’t really take off

26. “organizations which design systems ... are
constrained to produce designs which are
copies of the communication structures of
these organizations”
Bad collaboration or project management
have not solved by OOP
Conway’s Law Still Applies to OOP

27. Conway’s Law Illustrated

28. But The Main, Main Failure Of OOP Is...

29. CORBA, DCOM fundamental flaw was to
assume Location Transparency
Local vs Distributed Objects

30. Network Is Not Transparent

31. Welcome to the REST API Web (Economy)
From OOA to SOA

32. Case: Epigami OO Architecture

33. Why Not Apply OOD To Our Infrastructure?

34. Infrastructure Since 15 years
• Hardware Technologies +++
• Virtualization Technologies +++
• System Configuration Management +

35. ‘Infrastructure As A Code’: Really?
First deployment automation in the 90s
(Jumpstart SUN & Co)
Puppet & Chef are just improved automation,
not a new real paradigm

36. Light virtualization based on containers
From Infrastructure to Application-centric
The New Kid On The Block: Docker

37. Docker In A Nutshell

38. Infrastructure ‘Code’ Lifecycle

39. Infrastructure ‘Code’ Lifecycle
If Infrastructure is Code, why not use OOD?

40. OOD Applied to Docker
Docker
Image Build
Running Container
‘Jailed’ Process
FROM <image>
Init Script
EXPOSE <service>
Container Link
Link Alias
Object-Oriented
Class
Instance of Class
Encapsulation
Inheritance
Constructor
Method
Message Passing
Abstraction

41. Infrastructure Object Hierarchy

42. Benefits
• Isolation
• Security
• Modularity
• Traceability
• Automation (Continuous Deployment)
• Flexibility
• Performance
• Scalability
• Price

43. Summary
• Pros & Cons of OOD
• There is no Silver Bullet
• Continuous Evolution of the design
paradigms, built on top of the previous ones