Slides of the session as part of the International PHP Conference in Munich 2014. Today's websites are rather complex applications which try to create the illusion of an homogeneous user experience. A content management system might ultimately render the markup, but shops, product information systems or booking engines deliver content, too. Which architecture and mechanisms are necessary to seamlessly integrate third party systems into a CMS? Which strategies allow you to make your website scalable and perform well? This session doesn't provide you with a one-fits-all solution but rather shows the thinking behind a typical project architecture and the pros and cons of different options. Includes examples based on TYPO3 Neos.

1. Robert Lemke | TechDivision GmbH
Seamless Integration Architecture for
Content Commerce Websites

2. project founder of TYPO3 Flow
and TYPO3 Neos
co-founder of the TYPO3 Association
software architect at TechDivision
38 years old
lives in Lübeck, Germany
1 wife, 2 daughters, 1 espresso machine
likes drumming

3. Integrate ...

9. Content-Driven eCommerce

10. Neos Magento

13. Approaches
side-by-side (hybrid)
WCMS leads
shop leads
“Commerce And Content: The Odd Couple Or The Power Couple?,” Forrester Research

14. Challenges

15. common design

20. common navigation

24. cross linking

25. up to date content

27. REST

29. raw vs. prepared

30. actions

31. Approaches
side-by-side (hybrid)
WCMS leads
shop leads
something else leads

34. scale

36. Gearman
beanstalkd
Rabbit MQ
Amazon Simple Queue

38. Mandrill
Postmark
Sendgrid
Mailgun

40. TEXT HERE
@robertlemke
robertlemke.com
flow.typo3.org
neos.typo3.org
techdivision.com