Hi Tomek,
Just my idea
1/ That's just because they are old system, and relational databases are
just traditional databases. They have a lot of limitation, and unusable in
Big Data scenario.
2/ If set of links is really big, I believe that is a mistake in your
database modelling. For references, we should have n->1, and should not
1->n. Even if they are huge, OrientDB is very good at it. Yes, it's
extremely fast.
3/ OrientDB now is pretty fast, much faster than traditional databases.
Especially in case of doing aggregation.
4/ OrientDB SQL + Fetching Strategy also give you a big advantage than
other databases in querying, you will reduce a huge of database hits.
Hope it helps.
My Best,
Hung Tran
On Monday, March 7, 2016 at 8:38:05 PM UTC+7, TomaszK wrote:
>
>
> I have few questions about OrientDB. Can you please dispel my doubts?
> 1) Is a document-oriented database like OrientDB, a good choice for
> financial system? All financial systems I know use relational databases.
> 2) Is using a LINKSET is good idea if set of links is really big? Its all
> in one JSON like {"name":"ABC","links":[ref1,ref2,...ref29234]}
> Will it work quite fast to add or remove a link when this set is so big?
> 3) Assuming the use of the scheme-full model does aggregation (SUM) are as
> fast as in a good relational database?
>
> Best Regards
> Tomek
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
