Skip to content

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

Open

Description

@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?

Activity

  1. ruxy commented on Sep 30, 2021

    @ruxy
    Contributor

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions