Presentation by Jo Benson at the Developer Conference in Ashland, Oregon on November 6, 2013.

1. 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

2. About AspDotNetStorefront and where we are taking it.
Product Page
Category Page
Search Results
Homepage
Browsing
Search/Nav.
Calculate
Costs
Checkout
Admin
Retention

3. 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

4. Vortx Inc.
- data management
- data analysis
- specifically e-commerce
= bringing ‘data mobility’ to e-commerce users
2009, Enterprise Service Bus
Channel Advisor
Navision
StoneEdge
Fishbowl
Sports South (distributor)

5. 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”

6. Transform/Transport Engine
Product Page
Category Page
Search Results
Homepage
Browsing
Search/Nav.
Calculate
Costs
Checkout
Admin
Retention

7. 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

8. Transform
Pulll
Transform/Transport Engine
8.x – 9.x
Product Page
Category Page
Search Results
Homepage
Browsing
Search/Nav.
Calculate
Costs
Checkout
Admin
Retention
Output l

9. Pulll
Transform
Transform/Transport Engine
Output l
ONE EXAMPLE
For 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.

10. Pulll
Transform
Transform/Transport Engine
Output l
ANOTHER EXAMPLE
For 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.

11. Pulll
Transform
Transform/Transport Engine
Output l
ANOTHER EXAMPLE - DIFFERENT
For 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.

12. Pulll
Transform
Transform/Transport Engine
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.

13. 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