New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Taking the temperature on our scala stack(s) #72

Open

upperbounds opened this issue Sep 29, 2021 · 1 comment

upperbounds commented Sep 29, 2021

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?

Contributor

ruxy commented Sep 30, 2021

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment