You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Pothanaboyina <ba...@techouts.com> on 2017/05/23 15:46:09 UTC
Application Stack for Heavy transactions sustainability for
analytic engine
Hi,
I have a requirement where i get to collect almost 8millons of record which
should process simltaneuosly and should be allowed for regular read purpose.
we thought of two options
1)mongo db as database and apache ignite as cache with write back approach.
2)mysqldb as database and apache ignite as cache with write back approach.
Requested suggest me scalable architecture for my requirement
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Application-Stack-for-Heavy-transactions-sustainability-for-analytic-engine-tp13095.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Application Stack for Heavy transactions sustainability for
analytic engine
Posted by Pothanaboyina <ba...@techouts.com>.
Thanks @agura,
my question was related to performence of database or behavior under some
loaded conditions ,finally after some tests we have decided to go with mongo
the kind of flexibility it offers and sharding feasability.Thanks for your
response.please do share if you have any use cases related analytics
appliaction building
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Application-Stack-for-Heavy-transactions-sustainability-for-analytic-engine-tp13095p14588.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Application Stack for Heavy transactions sustainability for
analytic engine
Posted by Andrey Gura <ag...@apache.org>.
Hi,
There are no silver bullet answer for your case. Scalability will
depend on your Mongo or MySQL set up, data schema, engines, etc. It is
different databases with different ways to ensure scalability. So you
should consider this ways and may be create some POC's with
performance tests.
On Tue, May 23, 2017 at 6:46 PM, Pothanaboyina <ba...@techouts.com> wrote:
> Hi,
>
> I have a requirement where i get to collect almost 8millons of record which
> should process simltaneuosly and should be allowed for regular read purpose.
> we thought of two options
>
> 1)mongo db as database and apache ignite as cache with write back approach.
> 2)mysqldb as database and apache ignite as cache with write back approach.
>
> Requested suggest me scalable architecture for my requirement
>
>
>
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Application-Stack-for-Heavy-transactions-sustainability-for-analytic-engine-tp13095.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.