61–69 of 69 posts
This will be even cooler if they add 'turn-key' scaling. Their scaling approach is still a work in progress. http://www.arangodb.org/2013/05/22/replication-and-sharding-... Anyhow, good job so far to ArangoDB team.
I'm really excited about the look of this. Being a big fan of Mongo et al. for the structurelessness I also sometimes miss the graph-like structure that you can easily create with SQL. Arango looks cool. I shall try it :)
There is a screencast by McHacki about the graph explorer he wrote: https://www.arangodb.org/2013/11/29/visualize-graphs-screenc...
This will be even cooler if they add 'turn-key' scaling. Their scaling approach is still a work in progress. http://www.arangodb.org/2013/05/22/replication-and-sharding-... Anyhow, good job so far to ArangoDB team.
Thanks, and: you are right, scaling by sharding is important, and that is why we have made this our top priority for the coming three months.
It doesn't seem to support interactive transaction. That means only simple batch read & write, no complex transaction. It seems in between CAS and real generic transaction. Doesn't seem to be much useful.
Earlier quoted context omitted.
I'd say that one of the biggest thing that many of these NoSQL data stores brings is auto-sharding and being able to query/map reduce a distributed data source. Relational dbs work pretty well so long as you can vertically scale your data and or don't need to query across databases. Horizontal scaling is the tricky part for relational dbs that NoSQL data stores market as their big selling point.
Indeed, an the AQL looks interesting for the use case where Mongo fails, e.g. http://www.sarahmei.com/blog/2013/11/11/why-you-should-never...
Earlier quoted context omitted.
Indeed, an the AQL looks interesting for the use case where Mongo fails, e.g. http://www.sarahmei.com/blog/2013/11/11/why-you-should-never...
I remember reading that article. The article spoke like the lessons of an inexperienced developer, and not necessarily the problems of technology they were complaining about. BTW, what do you mean by AQL.
Quickstart link doesn't exist: http://www.arangodb.org/quickstart Looking forward to learning more when it's online!
Earlier quoted context omitted.
I remember reading that article. The article spoke like the lessons of an inexperienced developer, and not necessarily the problems of technology they were complaining about. BTW, what do you mean by AQL.
The idea of AQL (ArangoDB Query Language) is to bring an SQL query-like language to a document-store, most notably enabling joins between documents.
> In ArangoDB, a transaction is always a server-side operation, and is executed on the server in one go, without any client interaction. It doesn't seem to support interactive transaction. That means only simple batch read & write, no complex transaction. It seems in between CAS and real generic transaction. Doesn't seem to be much useful.