A lot of companies are moving from monolithic architectures to microservices. While there are many benefits to microservice architecture such as decoupling development and deploy cycles between different parts of the team, there is a lot of overhead for each additional microservice you introduce. There is this balancing act around the right granularity to make microservices and when to use libraries vs services. This desire for an in-between ground is what is fueling the function as a service movement. Drawing from Transposit’s approach to building a compositional layer where this glue code between services can live, this talk will discuss both the operational necessity for such an intermediary and how having one can speed up your team’s development and deploy cycles.