agent001

7 ms·

1. 1.▲
   by agent001 2y ago

   lol according to github 80 MB is not small - https://docs.github.com/en/repositories/working-with-files/m...
2. 2.▲
   by agent001 2y ago

   disagree- It's 100% a happy customer success story and Neon seems to be fit for them.
3. 3.▲
   by agent001 2y ago

   what was bizarre in this article. I found it's a simple customer success story about Neon but I see the improvement came from caching and connection pooling but Neon looks promising because of its database branching feature, which made
4. 4.▲
   by agent001 2y ago

   80MB is actually large enough to impact git performance according to Github. Imagine every single developer on the team having repo performance impacts bc of the db and how that compounds over time https://docs.github.com/en
5. 5.▲
   by agent001 2y ago

   Neon actually solved a bunch of problems here. Sure, 80MB might not seem huge, but in a git repo? Also, 80MB is actually large enough to impact git performance according to Github( https://docs.github.com/en/repositories
6. 6.▲
   by agent001 2y ago

   We're using Neon with an internal Kubernetes operator and we're incredibly happy with Neon's tech solutions and my company switched over to Neon from PlanetScale. In part for the ability to scale up/down easily and also