I have experience using both MongoDB and PostgreSQL. While pretty much spoken here is true, there is one more scalability aspect. When a fast moving team builds its service, it tends to not care about scalability. And in PostgreSQL there are much much more features that prevent future scalability. It's so easy to use them when your DB cluster is young and small. It's so easy to wire them up into the service's DNA.
In MongoDB the situation is different. You have to deal with the bare minimum of a database. But in return your data design has much higher horizontal scalability survivability.
In the initial phase of your startup, choose MongoDB. It's easier to start and evolve in earlier stages. And later on, if you feel the need and have resources to scale PostgreSQL, move your data there.
I put in random facts and categorize them. Topic of reading comes up, I can never remember books I’ve read. I started making Anki flash cards of book summaries. I review this and other topics for 15 minutes a day
I had an idea like this for helping introverts with icebreaking small talk. Flash style cards for each person, with info on what you spoke about last time, and a pre-prepared opener for the next time you bump into them. With the card info being updated each time you meet them.
Exactly! I've found I'm a lot more talkative and I appear to be more of a fast thinker with this approach. I have about 15 subjects (outside of coding - sports, wine, pop culture, national parks, current music, popular fiction, tv shows, movies) that I try to be knowledgable on and the flashcards help
This strange solution looks like a legacy of times when Steam used HTTP instead of HTTPS. Maybe they just didn't bother to update working code after migration to HTTPS?
No, I don't want do disallow editing. I do want to allow it but protect the content from accidental edits. Every time I publish a Notion page and forget to lock it, it is being accidentally modified. Some people notice it and undo. Some don't. In the combination with useless page history it is very difficult to reason whether the edit was accidental. The page could remain in accidentally modified state for a long time until author notices it.
Does "lock it" both allow editing and prevent accidental editing? What's the magic going on that distinguishes between real edits and accidental edits?
Go linker generates relatively big binaries due to static linkage. For some cases binary size is becoming an issue. 100+ MB binaries aren't uncommon in Go universe.
In MongoDB the situation is different. You have to deal with the bare minimum of a database. But in return your data design has much higher horizontal scalability survivability.
In the initial phase of your startup, choose MongoDB. It's easier to start and evolve in earlier stages. And later on, if you feel the need and have resources to scale PostgreSQL, move your data there.
reply