Conducted CommerceDr. Roman Zenner#eccj15

" ... let's simply build a webstore"

—287-page Word document describing necessary features

—Complex feature matrix in Excel—Constant change of requirements during

implementation—Module incompatibilities and version conflicts

6 months later than planned:

Launch with reduced feature-set and an uncertain future

Heap of HTML

The EHI-Shoplupe-Trusted Shops-X-Paradigm

Implementation vs. Operation

—Focus on implementation in time and budget—Launch is the most important determinant—The "now-we-are-done" fallacy

Monolithic vs. Distributed

—Monolithic core software is used "as is", it cannot be replaced unless the whole architecture is being rebuilt

PersonalizationScalabilityStaying agile

Implementation vs. Operation

—A project is not done and does not run in isolation—Focus on operation—Change is the default

Monolithic vs. Distributed

—Architecture is granular, relying on distributed services where sensible/possible

(Hosted) APIs

Conducted Commerce

—(Micro)-Services are interconnected to form the proper solution for the status quo

—If a service fails or the business models change, individual parts can be replaced

—Configuration instead of implementation

Dr. Roman Zenner

—Autor, Blogger, Referent—SPHERE.IO Developer Expert—@rzenner—shoptechblog.de

Thanksalot!

https://github.com/rzenner/p-conducted-commerce

Images (1)

—All GIFs: GIPHY—"Philae lander (transparent bg)" by ESA/ATG

medialab - https://www.flickr.com/photos/europeanspaceagency/10796307373/. Licensed under CC BY-SA 2.0 via Wikimedia Commons

—"Mambo Kurt" By Thomas W. Fiege (Own work) [CC BY-SA 3.0 (http://creativecommons.org/licenses/by-sa/3.0) or GFDL (http://www.gnu.org/copyleft/fdl.html)], via Wikimedia Commons

Images (2)

—"Orchestra" https://www.flickr.com/photos/vancouver125/, CC BY 2.0