AspDotNetStorefront and DotFeed

This morning’s session is designed to explain the path ahead for AspDotNetStorefront and why DotFeed Cloud will add massive value.

• Exploration of AspDotNetStorefront• History of service-oriented framework (DotFeed)• Marriage of AspDotNetStorefront and DotFeed• Early hints to stir your imagination

Admin

BrowsingSearch/Nav.

Hom

epag

e

Sear

ch R

esul

ts

Cate

gory

Pag

e

Prod

uct P

age

CalculateCosts

Checkout Retention

About AspDotNetStorefront and where we are taking it.

What we want (desperately) for our users:

• Add features• Minimal disruption• Easy upgrade

Additionally, the world of online computing is headed into the cloud.By extending our own reach into the cloud we can allow:

• Movement of data between storefront and other business applications• Owner defined manipulation of data• Sharing of destinations, managed costs

Vortx Inc.- data management- data analysis- specifically e-commerce= bringing ‘data mobility’ to e-commerce users

2009, Enterprise Service BusChannel AdvisorNavisionStoneEdgeFishbowlSports South (distributor)

September 2011,

Google Product Search

Refactored integration platform- insistence on services- massive scalability

Surfaced not the platform, but the application

“DotFeed for Google Product Search”

Admin

BrowsingSearch/Nav.

Hom

epag

e

Sear

ch R

esul

ts

Cate

gory

Pag

e

Prod

uct P

age

CalculateCosts

Checkout Retention

Transform/Transport Engine

DotFeed for Google Product Search

One app, representing massive potential:

Remember, we:• love data• want to give store-owners more freedom to work with their data• want to keep expanding the capacity of our storefront

Admin

BrowsingSearch/Nav.

Hom

epag

e

Sear

ch R

esul

ts

Cate

gory

Pag

e

Prod

uct P

age

CalculateCosts

Checkout Retention

Transform/Transport EnginePulll Transform Output l

8.x – 9.x

Transform/Transport EnginePulll Transform Output l

ONE EXAMPLEFor Google:

PULL : All products are pulled

TRANSFORM:(a) Breaks products into ‘items’(b) Filters on storefront factors(c) Provides an interface so that owner of data can optimize(d) E.g. adding google taxonomy(e) Converted into XML

Output: Destination is Google endpoint.

Transform/Transport EnginePulll Transform Output l

ANOTHER EXAMPLEFor Amazon:

PULL : All products are pulled

TRANSFORM:(a) Breaks products into ‘items’(b) Filters on storefront factors(c) Provides an interface so that owner of data can optimize(d) E.g. deleting all sales prices(e) Converted into XML

Output: Destination is FTP location for Amazon.

Transform/Transport EnginePulll Transform Output l

ANOTHER EXAMPLE - DIFFERENTFor Google Trusted Stores:

PULL : All orders and shipments are pulled

TRANSFORM:(a) Owner of the data can use interface to make changes(b) E.g. add tracking data(c) E.g. add ‘reason for cancellation’

Output: Destination is Google Endpoint.

Transform/Transport EnginePulll Transform Output l

How about this, to imagine?For managing topics:

PULL : All topics are pulled

TRANSFORM:(a) Owner of the data can use really cool drag/drop and search/replace and

preview interface to make changes(b) Versions can be stored and rolled back.(c) Topic navigation/hierarchy can be established

Output: Destination is back to the storefront.

After a break, we’ll demo yet another app, this time all the way different.

First, though, did I cover it?

• Exploration of AspDotNetStorefront• History of service-oriented framework (DotFeed)• Marriage of AspDotNetStorefront and DotFeed• Early hints to stir your imagination