RE: design principle to manage roll back

2020-07-14 Thread Manu Chadha
> Sent from Mail for Windows 10 > > > > From: onmstester onmstester > Sent: 14 July 2020 08:04 > To: user > Subject: Re: design principle to manage roll back > > > > Hi, > > > > I think that Cassandra alone is not suitable for your use case. Y

RE: design principle to manage roll back

2020-07-14 Thread Manu Chadha
Thanks. Will check Scalar DB. I avoid b Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Hiroyuki Yamada<mailto:mogwa...@gmail.com> Sent: 14 July 2020 09:26 To: user@cassandra.apache.org<mailto:user@cassandra.apache.org> Subject: Re: design p

Re: design principle to manage roll back

2020-07-14 Thread Hiroyuki Yamada
mstester > Sent: 14 July 2020 08:04 > To: user > Subject: Re: design principle to manage roll back > > > > Hi, > > > > I think that Cassandra alone is not suitable for your use case. You can use a > mix of Distributed/NoSQL (to storing single records

RE: design principle to manage roll back

2020-07-14 Thread Manu Chadha
ent: 14 July 2020 08:04 To: user<mailto:user@cassandra.apache.org> Subject: Re: design principle to manage roll back Hi, I think that Cassandra alone is not suitable for your use case. You can use a mix of Distributed/NoSQL (to storing single records of whatever makes your input the big

Re: design principle to manage roll back

2020-07-14 Thread onmstester onmstester
Hi, I think that Cassandra alone is not suitable for your use case. You can use a mix of Distributed/NoSQL (to storing single records of whatever makes your input the big data) & Relational/Single Database (for transactional non-big data part) Sent using https://www.zoho.com/mail/ O