This talk shows a real-world example of using FLOW3 for a service-oriented enterprise application and what's possible right now. FLOW3 is a framework that's not only great for web applications: with features like AOP, a clean architecture and the domain driven design concept it is very suited for business solutions. And it has the power to take PHP into areas that were previously driven by Java or other languages. This talk will show the benefits and experience of using FLOW3 for building a larger-scale service oriented application. From design and implementation to deployment and operation it'll give an overview what's possible with this new framework.

1. Building a
service oriented
application
with FLOW3

2. Building a
service oriented
application
with FLOW3
Christopher Hlubek
FLOW3 Core Team / networkteam GmbH

3. How I met
FLOW3

4. T3CON06, Karlsruhe

7. The Quest

8. „Provide a convenient and safe
customer account experience
for all websites and services of
the company“

9. Build an application to
centrally manage customer
data

10. Login, session handling
and single sign-on

11. Customer data and address
handling with validation

12. Provide web services
for other systems

13. Central notifications and
handling of email messages

14. Integrated CRM for support
agents

15. Customer chosen
technologies:
CouchDB for persistence
SOAP for webservices

16. Implications

17. Cutomer data == Security

18. Store sensitive data
securely

19. Fine grained access control

20. Scale to millions of
customers

21. High availability

22. Extending and maintaining
business logic must be
easy

23. Why we chose
FLOW3
More than one year ago

24. Domain-driven design
allows for good modeling
of the business logic

25. Security framework with
rich authentication and
authorization

26. Support for a clean
application architecture

27. High coding standards and
focus on automated tests

28. PHP has good SOAP
support

29. Well, not out of the box

30. What we learned
and improved
Along the way

32. „Eat your own dog food“

33. Unit tests are nice but you
need to test the whole
system

34. Being able to deploy easily
and often is crucial

35. Every Software has bugs,
FLOW3 has bugs

36. FLOW3 and TYPO3 have the
infrastructure to cope with that
[Gerrit, Hudson, Forge]

37. Working with a moving
target is sometime hard and
impossible without tests

39. Easy to use for developers,
hard to develop

40. What we achieved
Thanks FLOW3

41. Rich domain model

42. Parts of the domain

43. Future proof Web Service
architecture

44. Service
Consumer
Customer
SOAP service
Customer
Domain service
Security

45. Service Service
Consumer Consumer
Customer Customer
SOAP service V1 SOAP service V2
Customer
Domain service
Security

46. Customer Customer
SOAP service V1 SOAP service V2
Data Transfer Data Transfer
Objects V1 Objects V2
Domain Model
Customer
Domain service

47. Great SOAP server on
FLOW3

48. Solid CouchDB object store

49. Scalable architecture

50. Load balancer
Load balancer
Frontend node Frontend node Frontend node Frontend node
FLOW3 FLOW3 FLOW3 FLOW3
Load balancer
Load balancer
Database Database
CouchDB CouchDB

51. Fixed lots of FLOW3 bugs,
improved FLOW3 features

52. Full Security Framework
integration

53. Logging tools
for debugging and
monitoring

54. Transparent encryption of
data

55. Integrated deployment
solution based on FLOW3

56. Why I would
choose FLOW3 again
Right now

57. Focus on building
excellent software
of a high quality

58. Development teams spend up to
90%
of their capacity to fix bugs.

59. Agile and fast
programming model

60. Integrated feature set for
enterprise applications

61. Growing ecosystem for
delivering software with
high quality

62. Maturing API and features

63. Questions?
Please...