tapir
tyrian
tapir | tyrian | |
---|---|---|
14 | 24 | |
1,298 | 318 | |
1.6% | 6.3% | |
9.8 | 8.7 | |
4 days ago | 16 days ago | |
Scala | Scala | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tapir
-
what library/framework should I use for backend development?
You're not confined to the usual suggestions below (play, http4s). There's a ton of options. (I wrote test cases using a bunch of different frameworks a few years ago at https://github.com/hohonuuli/msdemos). Having written services using a variety of frameworks in production, I would strongly suggest using one that auto-generates API docs (openapi, swagger) for you. That will save you a huge amount of time later on. For heavier services, like the one at https://fathomnet.org/, I tend to the Java side (Quarkus is my current top choice, but Micronaut and Helidon are both great). For everything else I use Scala. My go-to right now is tapir using a vertx backend. See https://tapir.softwaremill.com/
-
Micronaut vs others(Spring Boot, Quarkus and co.)
Tapir is a Scala framework. (which runs on the JDK) Since the recent release of version 1.0, it's become my go to for many projects. It doens't provide much in the way of integrations with 3rd party frameworks, but I actually prefer that. It does autogenerate great swagger docs though.
-
Programming language comparison by reimplementing the same transit data app
I do wonder where the recommendation to use http4s for beginners came from. http4s is a very capable library (and if you care much about composition it is excellent), but I wouldn't describe the documentation as beginner friendly.
A slightly better starting point for scala 3 + type-safe server building is tapir e.g. https://github.com/softwaremill/tapir/blob/master/examples3/... . With that, you get a declarative definition of your endpoints (+ error types, auth, etc.) that you can use for both servers and clients, which comes very handy when writing integration tests of course.
> absolutely ridiculous the fetishization of extremely complex FP and type-level hacking that goes on in the ecosystem
An alternative way to look at it is that there is a lot of essential domain complexity that gets encoded via the type system to let the compiler do the hard work. That "extremely complex FP" does not arrive out of nowhere - I really recommend at least skimming through the slides from rossabaker, the http4s designer, that motivate where the core type signature comes from https://rossabaker.github.io/boston-http4s/#2
I suppose one of the "features" that I like about the (typelevel) community is that the approach of "worse is better" is not taken, and a lot of effort is expended to make things correct, modular and orthogonal. This has the drawback of increased upfront complexity, that anecdotally pays off the moment your compiler does not error and the program runs as intended.
-
Scala.js AWS Lambda, using Scala 3
Did you try tapir? There is a module for deploying aws lambda with Scala js. Not sure whether it is compatible with Scala 3, I am sticking with Scala 2 until Scala 3 gets more mature.
-
Library recommendations?
I'm aware, but it's a design decision that was made on purpose, and which I find in practice not a big problem at all.
-
Monorepo: seeking for an advice for bi-lang project
Backend is source of truth for types on frontend (backend generated OpenAPI definition with tapir, frontend takes it with orval)
-
Experienced dev new to Scala looking for a quick answer to get me on the right track - Advice on *standard* Scala framework stack to quickly set up a web-app backend ;
In all cases I would strongly suggest to have a look at Tapir, regardless of the server implementation that you pick.
-
tAPIr 1.0 release [INFOGRAPHIC]
Check the infographic below, to see this tool history, functionalities and more. Make sure, to take tAPIr for a spin here and share your feedback with us in the comment section!
-
Scala vs Kotlin for REST API
Tapir is awesome, and you can pick the server backend according to your preferred ecosystem (for instance http4s + doobie, Zio + Quill, Akka + Slick, ...)
-
Resources for learning about http4s and Typelevel ecosystem?
Finally I would strongly recommend having a look at Tapir. Even if you don't need to share endpoints or generate OpenAPI documentation, it provides a really neat abstraction on top of http4s.
tyrian
- Tyrian – The Elm Architecture for Scala.js
-
Learning Elm by porting a medium-sized web front end from React (2019)
If you want to try TEA, but not Elm I reccomend Scala.js with Tyrian[1]. Scala.js is a wonderful, mature project and Tyrian gives you the elm architecture in a very pragmatic way.
[1]: https://tyrian.indigoengine.io/
- At long last.. Tyrian (0.7.0) get's frontend routing!
-
Designing an HTML Component system
Have you looked at Laminar and Tyrian? Especially Tyrian seems to be close to what you're looking for.
-
What does the future look like?
What I wrote is obviously based on my experience as backend and data engineer. I'm so happy to see an adoption on the Frontend side (with things like Tyrian or OutWatch) and would be even happier if there was a clean path to Android. Out of curiosity, what do you find appealing in Scala, compared to e.g. Kotlin?
- Tyrian: Elm-inspired, purely functional UI library for Scala 3
- Tyrian 0.6.2 released
-
Released: Tyrian 0.6.0 & Indigo 0.14.0
Documentation can be found at https://indigoengine.io/ and https://tyrian.indigoengine.io/.
-
Monorepo: seeking for an advice for bi-lang project
Yes, I have. It didn't work out. There are quite neat libs like Tyrian, but they lack any ecosystem and I struggled to integrate it with pure JS libs - yet our app has a lot of very common components/widgets that we're really hesitating to write ourselves.
- Scala Multiplatform. Across the Universe
What are some alternatives?
smithy4s - https://disneystreaming.github.io/smithy4s/
Laminar - Simple, expressive, and safe UI library for Scala.js
http4s-jwt-auth - :lock: Opinionated JWT authentication library for Http4s
scalajs-react - Facebook's React on Scala.JS
distage-example - Example project built using distage, tagless final, http4s, doobie and zio
scala-webapp-template - A pragmatic skeleton to build web applications in Scala/Scala.js, including user registration, login, admin portal, and, deployments
scala-http-client - Extends the akka-http-client with retry logic, error handling, logging and signing
Converter - Typescript to Scala.js converter
pfps-shopping-cart - :shopping_cart: The Shopping Cart application developed in the book "Practical FP in Scala: A hands-on approach"
slinky - Write Scala.js React apps just like you would in ES6
AkkaGRPC - Akka gRPC
effect - An ecosystem of tools to build robust applications in TypeScript.