The document discusses building a content management framework (CMF) using Symfony 1.4, PHP, MySQL and Apache. It suggests using Redis instead of memcached for faster in-memory storage. The CMF would allow customers to express domains through a web interface. Pages in the CMF would use a hierarchical tree structure and nested sets to organize content in boxes. The CMF would be pluggable and abstract different layers through inversion of control.

1. Approaching unknown unknowns
- CMF for the masses -

3. The problem™

4. The problem™
Too much work

5. The problem™
Too much work
The solution™

6. The problem™
Too much work
The solution™
Work less

7. Be lazy

8. Don't reinvent the
wheel

9. Technologic stack:
php
mysql
apache
symfony 1.4

10. Why not Symfony2?

11. Why not Symfony2?
Sf2 is not ready for
production.

12. We are

13. N customers express
theirselves in one
way:
The Web

14. So you need a tool to
express N domains into the
web.
That is called CMF.

15. How do the CMF
and the customer
domain (DSL)
talk?

16. How does the CMF is bound with the DSL?
There is a hierarchycal Tree.
Containing N Pages.
Pages use nested sets.
Every page containing N Boxes.
Each box containing its Content.

17. How does the CMF is bound with the DSL?
Dependency inversion:
the CMF doesn't know
anything about the DSL

18. How does the CMF is bound with the DSL?
Each box has a content:
the content is an instance of
ConcreteBox

19. The system is
pluggable.
Permissions are an
example:

21. Abstraction over
abstraction over
abstraction over
abstraction over
abstraction....

22. So our well-dressed
CMF will finally look
like...

24. Solution:
a spaghetti coder +
memcached V2.0 +
ANSI C
=

25. Redis
A fast in-memory key-value storage engine written in ANSI-C.
Supports clustering, stores data like PHP arrays, writes to disk.
Instead of memcached 2.0 we can call it memcache 100.0

26. F***
YEAH!
We have NoSQL, we're on the edge!

27. MySQL talks to Redis

28. Cross-DBMS transactions

29. Redis is gently asked by
the front-end

30. So this...

32. ...becomes
this...

34. F***
YEAH!²
We use NoSQL, and we have a reason!

35. A few other
points:

36. Intensive logging
If a transaction fails, we
need to know if it has failed
due to MySQL or Redis.
And then why.

37. REST vs SEO
GET /products/1
or
GET /products/ferrari-f3000

38. REST vs SEO
GET /products/1
or
GET /products/ferrari-f3000
MIX'EM!
Still REST, still SEO!
GET /products/ferrari-f3000-1

39. Thanks!
Alessandro Nadalin
odino.org
twitter.com/_odino_

40. Last but not least!

41. Credits
http://www.flickr.com/photos/whatknot/13198827/sizes/o/in/photostream/
http://www.flickr.com/photos/donnagrayson/195244498/sizes/o/in/photostream/
http://www.flickr.com/photos/sakechaud/4452392482/sizes/o/in/photostream/
http://www.flickr.com/photos/gamergates/3461154165/sizes/o/in/photostream/
http://www.flickr.com/photos/14060551@N06/3050235141/sizes/l/in/photostream/
http://www.flickr.com/photos/33246833@N00/4353212216/sizes/o/in/photostream/
http://www.flickr.com/photos/jurvetson/36572011/sizes/o/in/photostream/
http://www.flickr.com/photos/htcfloorsystems/4008090894/sizes/o/in/photostream/
http://www.flickr.com/photos/mlleglass/491378611/sizes/o/in/photostream/
http://www.flickr.com/photos/rhymereverie/2253533697/sizes/l/in/photostream/
http://www.flickr.com/photos/spunkinator/3050946547/sizes/o/in/photostream/
http://www.flickr.com/photos/725/3524480344/sizes/l/in/photostream/