Migrate PHP E-Commerce Site to Go
•
1 like•1,754 views
This document summarizes one company's experience migrating their PHP e-commerce site to the Go programming language. It discusses how they initially rewrote their catalog page in AngularJS and Go, but ran into issues with Facebook OpenGraph integration. For their second release, they decided on a hybrid PHP and Go approach, with Go used to power specific backend modules like caching and shopping cart functionality. The author reflects on lessons learned around thoroughly evaluating new technologies before deploying them and making sure any changes have team consensus.
Report
Share
Migrate PHP E-Commerce Site to Go
- 1. Migrate PHP E-Commerce Site to Go Weng Wei, Zalora South East Asia Architect Dec 2013
- 2. Zalora South East Asia • Founded 2012 • Biggest Fashion E-Commence Site in SEA • SG MY ID HK VN TH PH BN • About 1000 employee（IT Department 40）
- 3. PoC start in Aug
- 4. 1st Release in Nov
- 5. Currently • 1st release has been rolled back • Restructuring, fighting for 2nd release
- 6. Today • Share my painful yet joyful experience
- 7. Original Platform • Classic LAMP • Alice: Front-end site for catalog display • Memcached / Solr • Bob: Back-end site for shopping cart & order processsing • MySQL
- 8. Why migrate? • PHP to memcached is fast, but php to solr… • PHP’s synchronous executing mechanism is the bottleneck • Related sharing from shooter.cn: https:// bitbucket.org/PinIdea/fcgi_ext/ (Chinese) • I enjoy challenge ^_^
- 9. • 1st release is experimental
- 10. • They said Google is “simple”, only 2 pages • zalora is two time complicate, it has 4 pages • catalog • product detail • shopping cart • payment
- 11. Experiment Plan • Rewrite “all 4 pages” in GO! • Maybe migrate “1 page” in GO first • nginx route different page to PHP / GO
- 12. nginx Alice memcache solrAll URLs BOB ZRS Tracking (GA / Webtrekk / etc) worker
- 13. Alice product cart.. catalog nginx Tracking (GA / Webtrekk / etc) Eve (GO) memcache solr BOB ZRS worker
- 15. Compatible with PHP stack • Support PHP serialisation/deserialisation in GO • https://github.com/Wuvist/gophpserialize • https://github.com/Wuvist/gophpserialize/pull/1
- 17. Risk Management • Go / PHP stack co-exist • Go Deployment requite no code change at PHP stack • Separate deployment for Go • nginx switch • Go live & rollback at anytime
- 18. PM’s request • user experience of catalog page need improvement • PM:”Give me AJAX…”
- 19. Look Good • Step by step improvement • Improve user experience: meet PM’s need • Migrate tech stack: R & D like challenge
- 20. Ambitious Plan • Split Alice PHP（Alice）: • AngularJS (Eve) Front-end MVVM • GO (Costa) Back-end API
- 21. No more PHP • AngularJS for all page rendering • GO for all API
- 23. • Everything was good, GO live! • Until I took an arrow on my knee • Until I share the new page link to Facebook
- 24. OpenGraph • Unlike Google Plus, FB crawler doesn’t support AJAX • All FB OpenGraph meta（title / text / picture） are wrong • OpenGraph is important to marketing
- 25. • AngularJS + Go API architecture is not design to support such case • Eve (AngularJS) approach can’t be used
- 26. Other Concern • Why AngularJS? Can’t just jQuery? • PHP page rendering is fast
- 27. Costa (GO) is cool
- 28. 2nd Release • PHP + GO, targeted mid Dec • No AngularJS
- 29. Experience • “Think more before do” • PHP is good for what it does • Team consensus is more important • Better understanding of Go’s potential
- 30. • New department for migrate back-end modules
- 31. Go’s potential • GroupCache (Migrate Memcached) • Shopping Cart • Order Processing • Full Page cache on CDN
- 32. Q & A