• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Developer Conference 11-6-13
 

Developer Conference 11-6-13

on

  • 226 views

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

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

Statistics

Views

Total Views
226
Views on SlideShare
226
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Over 100,000 lines of codeHand-outsRemember ‘business rules’Imagine adding GTIN to the product page…. So imagine we wanted to spruce up the content management for topics pages!
  • The next slide reveals the lid on ADNSF – make it important. Stop. Take time to really explain, this is DRAMATIC – storefront gets an extra layer of intelligence. Not just feeds, but ANYTHING might want to do with data

Developer Conference 11-6-13 Developer Conference 11-6-13 Presentation Transcript

  • 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
  • About AspDotNetStorefront and where we are taking it. Product Page Category Page Search Results Homepage Browsing Search/Nav. Calculate Costs Checkout Admin Retention
  • 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 Bus Channel Advisor Navision StoneEdge Fishbowl Sports 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”
  • Transform/Transport Engine Product Page Category Page Search Results Homepage Browsing Search/Nav. Calculate Costs Checkout Admin Retention
  • 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
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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