Taking the temperature on our scala stack(s)

[upperbounds]

We have a mixture of play/akka/http4s/fs2, etc.

• are there approaches we like better than others that we may want to consolidate on?
• are there approaches that may be preferable in terms of recruitment/retention?

[ruxy]

Considerations here:

• spec vs apibuilder (maintainability, community, features)
• deployment to SDLC account
• hiring (scala community moving away from play/akka)
• ease of standardizing in one direction
• supply chain is staying in https/fs2

next steps:

• Barry looking at spec, estimating moving over preferences-api or recommendations-api to http4s
• Need a small template for http4s to get it into SDLC (Vlad, Brian & Patka)