Is it wise to use ES for saving shopping Carts?


(Matthias Feist) #1

Hi Guys,

I'm working on an online shop. Currently we are storing the cart's content
in a MySQL Database so we can very easy access the amount of a certain
product and determine the reserved quantity.
This is very important as the amount in the user's carts is reserved so
other users my not by them.

What do you think: Is it wise to implement such a system in elasticsearch?
I'm mostly worried about the time between the "add to cart" (inserting a
document) and being able to access the total value due to the flushing
delay.

Thanks for your advice.

Kind regards
Matthias

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0c48d418-b8b9-4d9a-b659-5aca07e60eb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Mark Walkom) #2

ES is eventually consistent, so it may not make sense if you're latency
requirements are very strict.
If you can introduce a delay then it should work.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 22 May 2014 23:54, Matthias Feist matf.de@gmail.com wrote:

Hi Guys,

I'm working on an online shop. Currently we are storing the cart's content
in a MySQL Database so we can very easy access the amount of a certain
product and determine the reserved quantity.
This is very important as the amount in the user's carts is reserved so
other users my not by them.

What do you think: Is it wise to implement such a system in elasticsearch?
I'm mostly worried about the time between the "add to cart" (inserting a
document) and being able to access the total value due to the flushing
delay.

Thanks for your advice.

Kind regards
Matthias

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/0c48d418-b8b9-4d9a-b659-5aca07e60eb4%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/0c48d418-b8b9-4d9a-b659-5aca07e60eb4%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624ZM_fk9i49SpQtRmb2rr5Xy6WV3omwsCB8baBh4tic3Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(Adrien Grand) #3

On Thu, May 22, 2014 at 3:54 PM, Matthias Feist matf.de@gmail.com wrote:

What do you think: Is it wise to implement such a system in elasticsearch?
I'm mostly worried about the time between the "add to cart" (inserting a
document) and being able to access the total value due to the flushing
delay.

For your information, this flushing delay only exists for search
operations. We call it a near realtime operation because of this delay that
you need to wait after having indexed a document and before being able to
search for it (1 second by default).

However Elasticsearch doesn't only have a search API, it also has a GET API
that is realtime[1] and basically allows you to use Elasticsearch as a
key-value store.

[1]
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/docs-get.html#realtime

--
Adrien Grand

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j49hmhz7Av15FM13Nnpizh6GZEwn3dWmE_d2nZNCSXvow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(Matthias Feist) #4

Thanks for your help.
I will take a look into your links.

Matthias

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/228e8183-faaa-41f9-935e-60809bad6daf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #5