FCfcoury·Aug 11, 2023
Sorry about that, it's just a shortcut for https://github.com/fcoury/oxide.
In SQLite Functions for Working with JSONfcoury
oxide
Rust2022–2023
fcoury / oxide
oxide
:floppy_disk: Teach your PostgreSQL database how to speak MongoDB Wire Protocol
2Distinct people
5Mentions
0Explicit recommenders
286GitHub stars
What to know before exploring
What it is
:floppy_disk: Teach your PostgreSQL database how to speak MongoDB Wire Protocol
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month5 dated mentions
Observed mentions: 2022-07-29 01:55:15 UTC to 2023-08-11 11:55:14 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jul 2022 | 2022-07-01 00:00:00 UTC | 2022-08-01 00:00:00 UTC | 2 | 2 | 0 |
| Aug 2022 | 2022-08-01 00:00:00 UTC | 2022-09-01 00:00:00 UTC | 1 | 1 | 0 |
| Sep 2022 | 2022-09-01 00:00:00 UTC | 2022-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2022 | 2022-10-01 00:00:00 UTC | 2022-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2022 | 2022-11-01 00:00:00 UTC | 2022-12-01 00:00:00 UTC | 1 | 0 | 1 |
| Dec 2022 | 2022-12-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2023 | 2023-01-01 00:00:00 UTC | 2023-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2023 | 2023-02-01 00:00:00 UTC | 2023-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2023 | 2023-03-01 00:00:00 UTC | 2023-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2023 | 2023-04-01 00:00:00 UTC | 2023-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2023 | 2023-05-01 00:00:00 UTC | 2023-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2023 | 2023-06-01 00:00:00 UTC | 2023-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2023 | 2023-07-01 00:00:00 UTC | 2023-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2023 | 2023-08-01 00:00:00 UTC | 2023-09-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
5 sourceshttps://github.com/fcoury/oxide even though not 100% there yet, got tired of telling customers they needed a MongoDB instance just for my apps :-)
In Ask HN: What are your “scratch own itch” projects?Show HN: OxideDB – Teach PostgreSQL Database How to Speak MongoDB Wire Protocol
Hey everyone! I have created a product that relies on MongoDB for a document store but doesn't really need any of the distributed features to really justify having a hosted MongoDB or DocumentDB instance. Now that we're trying to turn this into a product, we're seeing that some companies have a little bit of resistance around managing yet another database. Most of our clients already have and manage PostgreSQL in one form or another.
I knew that PostgreSQL already offered first class JSON support, but I didn't want to rewrite the application data layer from scratch if I could avoid it. That's when I started researching if there was a "proxy" that would translate the MongoDB protocol - that I was completely ignorant about - into PostgreSQL. To my surprise there was nothing ready for production use but I found MangoDB that later on became F
Read the rest
erretDB. I delved into the code and was in love with the idea. The team around is really nice, but I found that they had greater ambitions - they basically wanted to offer multiple backends, namely Tigris, on top of PostgreSQL.
On the other hand, I have been waiting to find an excuse to delve deeply into the rust ecosystem but never really found something I was passionate about until I had the idea of challenging myself to see if I could learn about the protocol that MongoDB uses by relying on their public documentation and the hints I found on FerretDB.
Fast forward 3 weeks and I have something I am almost comfortable on sharing yet super excited to get feedback on. It's in very early stages, and it's work from someone that is not yet super comfortable with the stack. Please don't be too harsh and keep in mind this is the beginning of a journey for me that I embarked out of pure joy on getting a tiny bit better on rust and making things click internally.
Thank you for your time and if you would like to help me on this project please be more than welcome to reach out, either here, via email or directly on the GitHub repo. (heavy breathing before clicking submit :-) )
PS: I forgot to mention, but another thing I added to my toolbelt while developing this was about creating parsers. In order to transform MongoDB JSON to SQL queries, I ported an existing library from the MongoDB team from PEG.js to pest.rs!
OxideDB – Teach PostgreSQL Database How to Speak MongoDB Wire Protocol
16 points · Open discussionShow HN: OxideDB – Teach PostgreSQL Database How to Speak MongoDB Wire Protocol
Hey everyone! I have created a product that relies on MongoDB for a document store but doesn't really need any of the distributed features to really justify having a hosted MongoDB or DocumentDB instance. Now that we're trying to turn this into a product, we're seeing that some companies have a little bit of resistance around managing yet another database. Most of our clients already have and manage PostgreSQL in one form or another.
I knew that PostgreSQL already offered first class JSON support, but I didn't want to rewrite the application data layer from scratch if I could avoid it. That's when I started researching if there was a "proxy" that would translate the MongoDB protocol - that I was completely ignorant about - into PostgreSQL. To my surprise there was nothing ready for production use but I found MangoDB that later on became F
Read the rest
erretDB. I delved into the code and was in love with the idea. The team around is really nice, but I found that they had greater ambitions - they basically wanted to offer multiple backends, namely Tigris, on top of PostgreSQL.
On the other hand, I have been waiting to find an excuse to delve deeply into the rust ecosystem but never really found something I was passionate about until I had the idea of challenging myself to see if I could learn about the protocol that MongoDB uses by relying on their public documentation and the hints I found on FerretDB.
Fast forward 3 weeks and I have something I am almost comfortable on sharing yet super excited to get feedback on. It's in very early stages, and it's work from someone that is not yet super comfortable with the stack. Please don't be too harsh and keep in mind this is the beginning of a journey for me that I embarked out of pure joy on getting a tiny bit better on rust and making things click internally.
Thank you for your time and if you would like to help me on this project please be more than welcome to reach out, either here, via email or directly on the GitHub repo. (heavy breathing before clicking submit :-) )
PS: I forgot to mention, but another thing I added to my toolbelt while developing this was about creating parsers. In order to transform MongoDB JSON to SQL queries, I ported an existing library from the MongoDB team from PEG.js to pest.rs!