Skip to content
0:00 / 0:00

#quill#doobie#scala

Scale By The Bay 2019: Alexander loffe, Quill + Doobie = Better Together

FunctionalTV

10K subscribers • 19 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Alexander Ioffe, Quill contributor

Intermediate. Assumes working knowledge.

3.3K views6 years ago2 recommendations

Databases and dataProgramming languagesScalaPostgresSQL

Alexander Ioffe explains how to combine Quill and Doobie for type-safe, functional database access in Scala.

This talk video is a node in devreal.ai, the developer community graph. It connects to: Talk: Scale By The Bay 2019: Alexander loffe, Quill + Doobie = Better Together — devreal.ai/t/2019-scale-bay-2019-alexander-loffe-quill-doobi… Interview: Scale By The Bay 2019: Alexander Ioffe Interview — devreal.ai/t/2019-scale-bay-2019-alexander-ioffe-interview-s… Speaker: Alexander Ioffe — devreal.ai/n/alexander-ioffe Company: Nasdaq — devreal.ai/c/nasdaq Event: Scale by the Bay — devreal.ai/e/2019-scale-by-the-bay-conference Explore these connections and related videos, photos, speakers’ blogs and podcasts, and other By the Bay networks. ----- The power of today’s Open Source libraries is integration, and the Cats ecosystem is a great case-in-point. Combining Http4s, fs2, and Doobie makes for a powerful recipe that is ridiculously easy to use. As of Doobie 0.7.0, Quill has joined the fray, bridging the gap to the database layer. You can now model your data layer, compose it into queries, transact it, and send it out to the world, without ever having to leave the functional paradigm. By creating this integration, both Doobie and Quill get more than the sum of their parts. Doobie for instance, leverages fs2 to get rich set of effect-level JDBC operations that support everything from parallel-streaming queries, to reactive monitoring of asynchronous events from database change-listeners. Typically, the SQL queries for these varying use-cases will be similar but also different in non-trivial ways. This is where Quill comes to the rescue, allowing the common parts of SQL-queries to be abstracted away from the uncommon parts, ensuring a very DRY and maintainable solution, especially when the queries get very, very big. Join us on the next step of this wonderful journey!

Why it's here

2 people recommend this

What people say. Recommended as a great resource for integrating Quill and Doobie in Scala database applications.

u/Apellumin r/scala • Recommends

On “Good Database framework for small projects”

I have been battling this for the past few days as well and feel like I've gotten no where other than researching setups / configs for all of the libraries. I will say that so far Doobie seems to be quite popular. I was initially trying to implement ScalikeJDBC since it is what I used at my internship last and it felt comfortable to write queries and I didn't feel like any of the its queryDSL felt constraining, but there was one problem in my `build.sbt` file that wasn't getting resolved, and the documentation / examples are slightly few and far between lol. One interesting conference video I watched yesterday was about combining both Doobie and Quill, using Doobie for more Connection, IO…

u/Storiniin r/scala • Recommends

On “Best Way to Connect Scala API to MySql Database”

Quill + Doobile looks interesting [video , details at https://tpolecat.github.io/doobie/docs/17-Quill.html