Saturday, August 5, 2017
Hi,
-- Sorry for the confusion. Currently, I solved (just avoided concurrency) issue by adding a status column to slot model. So when a user trying to purchase that slot I update status column to hold so that other user don't able to book same slot at the same time.
Now I want solve the same problem without adding DB column. How can I do that?
Hope it clarifies.
On Saturday, 5 August 2017 20:28:06 UTC+5:30, Hassan Schroeder wrote:
On Saturday, 5 August 2017 20:28:06 UTC+5:30, Hassan Schroeder wrote:
On Sat, Aug 5, 2017 at 7:27 AM, siva subrahmanyam
<subbu98...@gmail.com> wrote:
> Currently we are building an booking application using ROR with Postgres as
> backend and running over Puma. We have a requirement where user can purchase
> a slot to display their ads. Currently we are relaying on DB, if one user
> doing booking a slot then we are restricting other user to start booking for
> the same slot to avoid concurrency issues. Initially I thought to use redis
> but prior to that I want to inquiry that is there any concurrency framework
> where I can communicate between requests such that I can avoid DB
> dependency?
Can you restate this? I don't understand the problem you're trying
to solve.
I certainly don't understand "avoiding dependency" on something
you already have (and need) by adding yet another dependency.
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/9ae3d37a-c2f5-46b4-9395-f27e31ead326%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment