Building Graphite: our experience with TypeORM | Graphite
graphite.dev · 944 words · saved by 1 readers
Graphite is modern code review for fast-moving teams - we help engineers write and review smaller pull requests, stay unblocked, and ship faster.
TypeORM at Graphite: a technical retrospective We're constantly iterating, learning and growing while building Graphite - that means looking back at our technical decisions and reflecting on what we could have done better. One such critical decision we took early on in our journey was the adoption of TypeORM , an Object-Relational Mapping (ORM) tool for TypeScript and JavaScript. In this post, I will share our journey with TypeORM, the challenges we encountered, and the steps we are taking to overcome them. Why TypeORM? We chose TypeORM due to the fact that it was the most mature TypeScript OR
related reading
- Building data-centric apps with a reactive relational databaseriffle.systems
- Why, after 6 years, I’m over GraphQLbessey.dev
- The Mom Testgraphite.dev
- What is Prisma ORM? (Overview) | Prisma Documentationprisma.io
- Python: Just write SQLjoaodlf.com
- How I Build — Adam Montgomerymontasaurus.com
- Building an LLM safe design systempolar.sh
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- GitHub - jorzel/concurrency-control: In this repo I would like to show 4 strategies of concurrency control for writing data using Python SQLAlchemy ORM and PostgresSQL (however this examples could be easily transformed to plain SQL).github.com
- Software development topics I've changed my mind on after 10 years in the industrychriskiehl.com
- The Problem with OpenTelemetrycra.mr
- The startup's Postgres survival guidehatchet.run