Open Source Commerce Melee
•
1 like•173 views
It's no doubt that when a website needs a commerce component, open source provides the most control - but how do you know which one is the best choice? While it's easy to go with a system built on your favorite framework, it may not be the best choice based on business needs. This talk takes an objective look at the open source commerce ecosystem and provides a set of questions and guidelines to use to find the right system for your application.
Recommended
More Related Content
Similar to Open Source Commerce Melee
Similar to Open Source Commerce Melee (20)
More from Ben Marks
More from Ben Marks (10)
Recently uploaded
Recently uploaded (20)
Open Source Commerce Melee
- 1. OSS Commerce Melee Ben Marks // @benmarks ben@magento.com
- 3. humankind learned the value of “things”.
- 5. we learned the value of exchanging things of value
- 8. Exchanging things of value is in our DNA.
- 9. Marijuana was the first* Internet transaction. "In 1971 or 1972, Stanford students using Arpanet accounts at Stanford University's Artificial Intelligence Laboratory engaged in a commercial transaction with their counterparts at Massachusetts Institute of Technology… http://www.neatorama.com/2013/04/21/The-Worlds-First-E-Commerce-Transaction-Was-a-Drug-Deal/
- 10. Marijuana was the first* Internet transaction. ”…Before Amazon, before eBay, the seminal act of e-commerce was a drug deal.The students used the network to quietly arrange the sale of an undetermined amount of marijuana.” http://www.neatorama.com/2013/04/21/The-Worlds-First-E-Commerce-Transaction-Was-a-Drug-Deal/
- 11. Fortunately, humankind’s value of exchange was not, and is not limited to physical goods.
- 12. “Open-source software” – Christine Peterson https://sdtimes.com/os/history-behind-term-open-source/
- 13. “Open source can propagate to fill all the nooks and crannies that people want it to fill.” - Mitch Kapor https://www.wired.com/2003/11/opensource/
- 14. “I think, fundamentally, open source does tend to be more stable software. It's the right way to do things.” - LinusTorvalds https://bazaarmodel.net/phorum/read.php?1,7899
- 15. “The strategic marketing paradigm of Open Source is a massively-parallel drunkard's walk filtered by a Darwinistic process.” - Bruce Perens http://www.osadl.org/Bruce-Perens-The-Emerging-Economic-Para.bruce-perens.0.html
- 16. “massively-parallel drunkard's walk filtered by a Darwinistic process”
- 17. 😂
- 18. The Story of OSS & Commerce…
- 19. …is too long to tell here.
- 20. So, a quick summary:
- 21. eComm Prehistory: Viewtron (1983)
- 22. CompuServ’s “Electronic Mall” (1984)
- 23. WWW, HTML Created (1990/91)
- 24. Netscape 1.0 released, SSL established (1994)
- 25. And then,1995.
- 27. Honorable Mention (2000): The Exchange Project, a.k.a.
- 28. TEP / osCommerce proved that OSS & ecommerce were not just viable, but VIBRANT.
- 29. Evaluating OSS Commerce Solutions
- 30. App, Component, or Framework?
- 31. App • Self-contained • Owns Request • Turnkey • Many TPEs Component • Tiny App • Complementary App • Highly Portable Framework • Complements & Sets Conventions • Likely Many TPEs
- 32. The Four Cs of Commerce Sites Content Catalog Customers Cart
- 33. The Four Cs of Commerce Sites Content Catalog Customers Cart
- 34. The Four C’s of Commerce Sites Content Catalog Customers Cart • Who is managing it? • How is it managed? (Editors, reviews, rollbacks, import, etc.) • Where is it used? • Are there variations based on locale?
- 35. The Four Cs of Commerce Sites Content Catalog Customers Cart • How many products? • How are they grouped? (attributes, categories, sets, etc.) • Are there attribute variants which should be presented?
- 36. The Four Cs of Commerce Sites Content Catalog Customers Cart • What state-dependent interaction is needed? • Analytics • CRM • Wishlist
- 37. The Four Cs of Commerce Sites Content Catalog Customers Cart • What cart behaviors are required? • How varied are the orders? • Which payment vendors are needed? • How are orders processed?
- 38. The Fifth C: Customization*
- 39. * “Commerce is always custom.” - @benmarks, just now
- 40. Customization • Third-party integrations (maintenance, support) • Underlying frameworks & standards • Test framework, Continuous Integration • Integration to existing systems • Speed to iterate Custom needs determine:App, Component, or Framework
- 41. The Sixth C: Community
- 42. Community • Core development • Developers (agency, consultant, employees; markets) • Long-term maintenance • Self-service support • Third-party integrations • Corporate stewardship
- 43. The Seventh C: Conclusion
- 44. Conclusion • Any approach is on the table at first • Content-first approach puts content needs at the beginning of a decision tree • Ecosystem effects abound: • Third-party extension, integration, and support • Customizations • Coporate backing