Understanding the Benefits of Using Effect's SQL Module with Drizzle
So I've been using effect pipelines / error management, schema, and platform for a while, and now beginning to look into the rest of the modules a bit more. I've just come across the SQL module, and specifically the drizzle implementation.
I'm a bit confused as to what these modules do other than register the service layer for me. What are the benefits to doing SQL this way vs what things can't I use? Can I still use drizzle's rqbv2? What perks do I get via using the effect modules which I don't get by running my own service layer directly using drizzle?
I'm a bit confused as to what these modules do other than register the service layer for me. What are the benefits to doing SQL this way vs what things can't I use? Can I still use drizzle's rqbv2? What perks do I get via using the effect modules which I don't get by running my own service layer directly using drizzle?
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
