It depends of the latency you are looking for.
If you are ok with a relational database, probably OrientDB is OK too.
If you are looking for microsecond performance and high frecuency trading,
then you put all in ram. No Odb, no SQL.
Your question is too wide. Could you narrow it?
Pablo
On Monday, March 7, 2016 at 5:38:05 AM UTC-8, 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.
