T3CON11 Building a service oriented application with FLOW3
4 likes2,371 views
The document discusses the development of a service-oriented application using Flow3, focusing on creating a secure and convenient customer account management system that integrates various technologies. Key features include centralized customer data handling, validation, and a scalable architecture to support millions of users. The author highlights lessons learned, the importance of testing, and the advantages of using Flow3 for building high-quality software.
![FLOW3 and TYPO3 have the
infrastructure to cope with that
[Gerrit, Hudson, Forge]](https://image.slidesharecdn.com/t3con11-service-oriented-applications-flow3-111010052935-phpapp02/85/T3CON11-Building-a-service-oriented-application-with-FLOW3-36-320.jpg)
T3CON11 Building a service oriented application with FLOW3
- 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
- 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
- 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
- 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
- 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...
Editor's Notes
- #2: \n
- #3: \n
- #4: \n
- #5: \n
- #6: \n
- #7: \n
- #8: \n
- #9: \n
- #10: \n
- #11: \n
- #12: \n
- #13: \n
- #14: \n
- #15: \n
- #16: \n
- #17: \n
- #18: \n
- #19: \n
- #20: \n
- #21: \n
- #22: \n
- #23: \n
- #24: \n
- #25: \n
- #26: \n
- #27: \n
- #28: \n
- #29: \n
- #30: \n
- #31: \n
- #32: \n
- #33: \n
- #34: \n
- #35: \n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: \n
- #47: \n
- #48: \n
- #49: \n
- #50: Multi API with central business logic,\ncentral security\n
- #51: Versioned service endpoints\n\n
- #52: DTOs to versionize model\nGive good example\n\n
- #53: Automatic Object Mapping\nAutomatic WSDL generation\n
- #54: \n
- #55: \n
- #56: \n
- #57: \n
- #58: \n
- #59: \n
- #60: Multi account authentication\n
- #61: Audit-Log in CouchDB\n
- #62: \n
- #63: \n
- #64: \n
- #65: \n
- #66: Lösungen: TDD, Code Inspection (Reviews, Pair Programming, ...), Framework?\n
- #67: \n
- #68: \n
- #69: \n
- #70: \n
- #71: \n