Doobie Tutorial: Scala, Databases and pure Functional Programming

[@VitthalMirji]

Daniel I'm waiting for the next part, please upload soon. I can't Thank enough on your effort helping us learn Scala & other FP concepts.

[@miloventimiglia8547]

This is great! Thanks for complementing the Cats courses with a more practical implementation of these concepts!

[@kevalan1042]

Nicely done, thanks! A nice "capstone" example here would have been how to combine a read stream and a write stream. For example, read the actor table, and insert for each actor their evil twin into the table, in a streaming fashion.

[@rockthejvm]

Exercise for the reader :P

[@leorandomnickname]

Hey Daniel, could you do a video on your thoughts about Scala's future, how to succeed in industry being a Scala developer, which libraries to study, ZIO vs Cats, etc etc etc whatever you think about Scala in the next years.

[@anzo.p]

Brilliant

[@kevalan1042]

This is great! Could you do one on Skunk?

[@rockthejvm]

One at a time :D

[@higyedarnold5404]

Great content 👍🙏

[@harelma24]

Thanks Daniel. Cant wait to second part . Is Doobie relevant only to Postgres ? Does it fit to NoSQL like Cassandra ?

[@rockthejvm]

Doobie is a library for JDBC & functional programming, so Cassandra won't work.

[@no_more_free_nicks]

I'm in the middle of your Cats Effects course, without taking the Cats course first. I'm progressing at a slow but steady pace.

[@rockthejvm]

Enjoy! Take your time because the course is tough, but it'll be worth it!

[@no_more_free_nicks]

When I saw "Actor" I thought you are talking about akka Actors :D

[@rockthejvm]

LOL

[@leorandomnickname]

nice tutorial. I have a question regarding the transactor. Is it supposed to be reused like you do for every query or there is some reason one would create separate transactor in a real production app.

[@rockthejvm]

Check out the blog for the _real_ thing to use.

[@mananoreboton]

I'm lazy so I'm not going to search how to do joins. I will wait for chapter 2 😆

[@OnurErenElibol]

I'm very sad that almost every library depends Cats on Scala. This is good for pure FP programmers but I think Scala needs FP + OOP hybrid libraries also. Scala has not a pure FP design and when newcomers like me trying to find a simple DB connector / ORM on Scala have to deal with this interesting, alienish syntax / concepts. This is a very discouraging thing for devs who is trying to learn the language and I think this is why the community is not big yet after years. Scala is a very beautiful hybrid language (best of both worlds) and it really needs hybrid libraries to show its expressiveness. If any newcomers see this comment, please start with Java libraries on Scala. You will see its power. After that try to contribute to libraries in a hybrid way. At least I will try to do like that way.

[@rockthejvm]

This is why the Rock the JVM channel is here - to make the learning curve easier and smoother.

[@OnurErenElibol]

@@rockthejvm You are doing great work. You have fantastic videos and I should say that it made Scala more approachable for me. But my point is; OOP + FP hybrid programming in Scala should be promoted instead of pure FP. May be (or if you want, I don't know) you can introduce Vert.x, instead of http4s, hibernate instead of doobie etc... or may be both of them. Also the thing is I really cannot find a library in Scala which is written in a hybrid way. If you know you can share them also.

[@alaindevos4027]

slick is a good alternative

[@BloodnutXcom]

Funny HC and HPS are named "high level" but are actually low level

[@rockthejvm]

There's (much) lower-level than that - the sql interpolators are just syntax sugars on top of HC and HPS.

[@BloodnutXcom]

@@rockthejvm I know, I'm partly joking as you have called it a lower-level API at 26:00

[@funprog]

Too much boilerplate for simply Using jdbc the benefits are minimal and performance is slow with all the wraping...

[@АлександрВаганов-к6й]

Guys! Could somebody help me, please! Do absolutely the same project, but can not connect to postres catching org.postgresql.util.PSQLException: IMPORTANT: user "postgres" is not authenticated (by password).