Tasks that need to be performed on a certain date in Azure -
i developing application using azure cloud service , web api. allow users create consultation session ability change price of session, allow users 30 days leave session before new price affects price members signed session. first thought use queue storage , set visibility timeout 30 day time limit, seems grow queue fast on time, if message should not run 30 days; not mention ordering issues. looking @ task scheduler session pricing changes not recurring concept more random. queue idea approach or there better , more efficient way accomplish this?
the stuff trying should done relational database. can use timestamps record when prices session changed. wouldn't use queue @ this. queue more passing messages in distributed system. problem tracking prices changed on sessions , when. data should modeled in database.
Comments
Post a Comment