If you run multiple batch updates in postgres, you may run into deadlocks.

We’ll look into why this happens and how we can prevent it.

There are 2 broad extremes when doing Scrum. To make scrum-items based on tasks or on functionality.

Config derivation with ZIO config and Magnolia.

With simple ZIO layer creation, it’s convenient to use +`, `>>>` and `>> to compose layers.

When layers and dependencies get more complex, ZLayer.make is there to help.

We’ll compare some code written with Either with similar code written using Exceptions and see how they are the same and how they differ.

Preferable you start a ZIO application with just one runtime.unsafeRun.

But when you’re migrating an old application to ZIO, you likely have multiple places to do runtime.unsafeRun. We will investigate how to deal with the environment (layers).

We’ll look at some examples of different kinds of exceptions and how we can deal with them in ZIO.

We’re making an API to collect cats. We’ll be using ZIO 2.0, and Caliban

In Akka Typed we need an ActorContext to create new actors.

This poses some problems if we want to create an actor inside a class that’s not an actor. We can pass around an ActorContext from a (higher level) actor. But if this is a longer-lived class, we have to keep in mind that this ActorContext is only valid during construction. So it’s generally frowned upon to pass around the ActorContext.

We’re going to explore how we can use a default value for a value class in Sangria.

This builds on the previous blog post about Sangria.

What is Akka Serverless?

In short: There are no actors. It’s a 4GL framework in the cloud.

Setting: We serve a GraphQl API using Sangria and Akka HTTP.

We’ll go through the steps necessary to parse value classes.