I'm a one-man shop and I'm planning to start working on an app soon. I'd 
traditionally use a relational system, but frankly, the process of mapping 
Java objects to MySQL tables is getting to be quite annoying. That and 
keeping the schema updated after every class change.

As far as the data structure goes, it's not terribly complex; there are 
some foreign keys here and there - Product -> shopping cart, order item -> 
order, order -> user, etc - Referential integrity would be nice, although 
it's not very difficult to manage by hand. I also render pretty much 
everything as JSON for consumption on the client side.

I don't foresee the data growing to the point where I need multiple 
database servers in a cluster to store it all and I don't think sharding 
will be in the cards either.

I'm just looking for a nice, ergonomic way to rapidly develop app and get 
it to production. Is this a good candidate case for ArangoDB or should I 
bite the bullet and continue using MySQL?

I see ArangoDB has an AQL language as well, would this suit my needs for 
doing stuff like generating monthly reports as well?

-- 
You received this message because you are subscribed to the Google Groups 
"ArangoDB" 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.

Reply via email to