Timeline for Can I create "Other customers also bought..." recommendations using Sitecore xDB?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 13, 2016 at 18:44 | vote | accept | Søren Engel | ||
| Oct 6, 2016 at 16:02 | comment | added | Pete Navarra | I do agree with you that xDB is intended for real time response. Use of machine learning tools I think will really drive this desire forward. | |
| Oct 6, 2016 at 16:01 | comment | added | Pete Navarra | There are limits here: If you are using xDB cloud, you can't use custom facets due to the hosted aggregation/processing server. In addition, adding a lot of additional data to xDB is going to exponentially increase the disk space needed for Mongo, something thta was recently brought to my attention by Sitecore. | |
| Oct 6, 2016 at 15:33 | comment | added | nickwesselman | There may be architectural limitations currently, but I have to believe this is part of Sitecore's vision for its marketing platform -- real time response to customers based on historical data. Though not created directly by Sitecore, WeBlog uses the RDB to display popular posts. | |
| Oct 6, 2016 at 15:29 | comment | added | Dmytro Shevchenko | That's a very interesting suggestion! I haven't thought about using the RDB to store entity-level relationships. I don't believe xDB was necessarily built with such use cases in mind, since the RDB is normally only used in reports, not on every page load. It can even be inaccessible to content delivery servers. Anyway, I suppose your suggestion can work. A lot of performance issues should be considered and addressed, and I still believe building a custom data store will be easier and better suited for performance optimizations. | |
| Oct 6, 2016 at 15:21 | history | edited | nickwesselman | CC BY-SA 3.0 |
more detail
|
| Oct 6, 2016 at 15:16 | history | answered | nickwesselman | CC BY-SA 3.0 |