✳flâneur — a map of the web's best reading
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
Explore this link on the map →related reading
- What is Prisma ORM? (Overview) | Prisma Documentationprisma.io
- Choose Boring Technologyboringtechnology.club
- Why, after 6 years, I’m over GraphQLbessey.dev
- Against SQLscattered-thoughts.net
- From good to graph: Choosing the right databaseneo4j.com
- A mental model for Prisma Migrate | Prisma Documentationprisma.io
- TypeScript: Documentation - The Basicstypescriptlang.org
- Databases are Fucking Stupid | Probably Danceprobablydance.com
- Just Use Postgres for Everything | Amazing CTOamazingcto.com
- A Graph-Based Firebasestopa.io
- The Mom Testgraphite.dev
- Pyrefly vs. ty: Comparing Python’s Two New Rust-Based Type Checkers | Edward Li's Blogblog.edward-li.com