This post is pretty accurate in my opinion.
Sihl aims to be a set of composable service interfaces for common infrastructure components in web apps like user handling, job queues, authorization, block storage, caching and so on. The goal is to cover those infrastructure concerns that are in between the “lower level” concerns (such as HTTP API, routing, middlewares, persistence API and others) and the application.
The less time we spend implementing CSRF middlewares, the more time we can spend developing nice dashboards for the job queue. So I am exited to see that those (from Sihl’s point of view) lower level concerns are taken care of, by Opium and now Dream.