Show HN: Mongita is to MongoDB as SQLite is to SQL
21–30 of 95 posts
Re: Show HN: Mongita is to MongoDB as SQLite is to SQL
#22Earlier quoted context omitted.
The project isn't about performance, it's about providing an embedded version of MongoDB - it clearly states that if you grow too large, then you can easily migrate to the full MongoDB. It also clearly states not to use it if you want a relational database.
Then the comparison with SQLite is totally wrong. SQLite is a production-grade DBMS: though it has fewer features compared to e.g. PostgreSQL, if those feature suffice, you can throw very sizable workloads at it.
Re: Show HN: Mongita is to MongoDB as SQLite is to SQL
#23Cool project but I have to admit I sure wish this was written on top of SQLite, rather than just mentioned it, implementing a query language shim for MongoDB on SQLite would be an amazing project. In the absence of such a project though, this is a pretty great alternative to have.
I could be wrong on that though.
Re: Show HN: Mongita is to MongoDB as SQLite is to SQL
#24Re: Show HN: Mongita is to MongoDB as SQLite is to SQL
#25Earlier quoted context omitted.
The project isn't about performance, it's about providing an embedded version of MongoDB - it clearly states that if you grow too large, then you can easily migrate to the full MongoDB. It also clearly states not to use it if you want a relational database.
Then the comparison with SQLite is totally wrong. SQLite is a production-grade DBMS: though it has fewer features compared to e.g. PostgreSQL, if those feature suffice, you can throw very sizable workloads at it.
Re: Show HN: Mongita is to MongoDB as SQLite is to SQL
#26> Mongita is to MongoDB as SQLite is to SQL it really isn't if it's written in python
Is it semantically perfect? Probably not. Will Mongita be useful to Python developers who are accustomed to saving their data in idiosyncratic JSON files because they don't want the overhead of a MongoDB server? Maybe! I hope so.
Re: Show HN: Mongita is to MongoDB as SQLite is to SQL
#27Earlier quoted context omitted.
The project isn't about performance, it's about providing an embedded version of MongoDB - it clearly states that if you grow too large, then you can easily migrate to the full MongoDB. It also clearly states not to use it if you want a relational database.
Then the comparison with SQLite is totally wrong. SQLite is a production-grade DBMS: though it has fewer features compared to e.g. PostgreSQL, if those feature suffice, you can throw very sizable workloads at it.
Re: Show HN: Mongita is to MongoDB as SQLite is to SQL
#28Earlier quoted context omitted.
The project isn't about performance, it's about providing an embedded version of MongoDB - it clearly states that if you grow too large, then you can easily migrate to the full MongoDB. It also clearly states not to use it if you want a relational database.
Author here. That's exactly it. I think it would be very difficult to completely beat SQLite with a Python library. My goal wasn't to beat it but to have performance that's within an order of magnitude which I think I've achieved. In my opinion, the MongoDB interface has a lot of advantages over SQL that make sense in a lot of use cases. Certainly, there are times when a traditional relational database is the right c…
This is an excellent idea and your library is proof of concept.
Surely one day performance can be improved in the future, and the core logic can be rewritten in a compiled language that can be used from other runtimes.
Re: Show HN: Mongita is to MongoDB as SQLite is to SQL
#29In memory, how does perf compare to https://github.com/nodkz/mongodb-memory-server ?
Re: Show HN: Mongita is to MongoDB as SQLite is to SQL
#30Genuine question!