softwaremill / softwaremill/elasticmq
Rewrite http layer to replace akka
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.9k
- Forks
- 203
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 6
Description
Use http4s? zio-http? tapir + netty? tapir + vertx? There's a couple of options.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by mapping the current HTTP layer and comparing the options named in the issue: http4s, zio-http, tapir with Netty, and tapir with Vert.x. The work is complete when one approach has been selected and the Akka-based HTTP layer is replaced while preserving ElasticMQ’s Amazon SQS-compatible interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100