Greg, am I correct in thinking azure table storage is only a cheaper option when the number of reads is light? Preet mentions he will need reporting and depending on how heavy those are hit azure table storage could get expensive.
On Mon, Jun 6, 2016 at 10:59 PM, Greg Keogh <gfke...@gmail.com> wrote: > For the DB I suspect the latest entity framework will be sufficient but am >>>> open to ideas about other technologies that might not have been present >>>> when I last worked with it 5 years ago. >>>> >>>> This service will only be used in house, but might be housed in the >>>> cloud and security is a very high consideration. >>>> >>> > I forgot to mention ... don't forget Azure Table Storage! I've been really > loving it recently and using it where a SQL Db would be overkill. The API > is dead simple, vast capacity, cheap, and build and runtime dependencies > are trivial -- *GregK* > >
