A brief file about the origin of the tool that facilitated database access and increased productivity for the JavaScript/TypeScript ecosystem
Divided into
three layers as the core of its architecture, Prisma was born in the JavaScript ecosystem with the promise of being a facilitating and productive tool for devs who work directly with databases. For a number of reasons, the technology has come to be recognized as “one of the best things that ever happened” in backend programming among Node.js users.
This week’s article aims to raise a file about Prisma and understand why the technology has gained so much relevance over the years. If you follow our platform and have recently accessed our content on YouTube, you must have noticed that we have been keeping an eye on Prisma’s performance for a long time.
There is not exactly a date to point to as “the day it was released”, however , if we go into the GitHub logs, we notice that the first Prisma repositories appeared in mid-2017, with signatures by Lukáš Huvar and Johannes Schickling.
Before being Prisma, the small project was called Graphcool and had a small team of five devs who intended to develop a solution as a backend-as-a-service for GraphQL. Graphcool at the time was well received by the community, mainly because it was “easy to use” even for Frontend devs.
Nikolas Burk, one of the team’s first devs, acknowledged in this thread that, despite the project having potential at the time, it was not able to scale due to lack of flexibility . The solution was to develop, over a series of attempts, Prisma 1.0 in 2018. Prisma Client was announced months later.
