71–80 of 119 posts
I think Microsoft should implement basic aggregation functions first.
AWS needs something like this. The missing piece for the AWS serverless story is a database that is suitable for writing real world applications. DynamoDB is far from suitable for that task, which leaves AWS serverless with no good database.
I think Microsoft should implement basic aggregation functions first.
Implementing aggregation at query time is a temporary solution. For systems like this aggregation should be done on insert time - many hugely popular databases do not provide much more than a basic get operation for this reason
Never looked at DocumentDB before. So if I get this straight, I can get a fully managed DB that can scale easily, but still have all the advantages and compatibility of a regular NoSQL like Mongo? I think that's a first, right?
Never looked at DocumentDB before. So if I get this straight, I can get a fully managed DB that can scale easily, but still have all the advantages and compatibility of a regular NoSQL like Mongo? I think that's a first, right?
Percona have their drop-in MongoDB replacement that uses TokuMX under the hood and they'll manage it for you.
MongoDB Atlas will manage MongoDB for you
Interesting... So compatible with Mongodb protocol but not using mongodb internally ? What is your view of services, which provide functionality of some other software or SAAS and is API / Protocol compatible ? Can API / protocols be copyrighted or patented? I believe not based on Google vs Oracle.
Hasn't tokuMX already put a 'proper' solid DB behind the mongo API?
Earlier quoted context omitted.
Probably around the same time ops were deemed useless :) [1] https://news.ycombinator.com/item?id=13644789
I saw that chain too. I guess I do devops differently. Since I'm bootstrapping I don't have money for an ops person. So I've set about learning ufw, let's encrypt, nginx/tls termination to a service only accepting local connections to the port, etc. I see devops as the developer learning the ops side to take responsibility for the whole stack.
Earlier quoted context omitted.
Implementing aggregation at query time is a temporary solution. For systems like this aggregation should be done on insert time - many hugely popular databases do not provide much more than a basic get operation for this reason
You might be right but Mongo supports them and Microsoft says that we can start using DocumentDb without changing any line of code which is not true.
"As we were developing our new financial benchmarking service last year, we evaluated Microsoft’s Azure DocumentDB, but MongoDB offered much richer query and indexing functionality"
KPMG France https://www.mongodb.com/blog/post/kpmg-france-enters-the-clo...