Http4s
Play
Our great sponsors
Http4s | Play | |
---|---|---|
24 | 31 | |
2,497 | 12,488 | |
0.5% | 0.0% | |
9.8 | 9.8 | |
2 days ago | 4 days ago | |
Scala | Scala | |
Apache License 2.0 | Apache License 2.0 |
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.
Http4s
-
How to get started?
http4s is a Typelevel project, and therefore falls into the "program in Scala as if it were Haskell" category. Many people find this off-putting, but honestly, I think with the resources listed above, this is the option at the best intersection of "mature" and "well-documented" available in Scala. The reason it's off-putting to many people is that Haskell-style pure FP isn't mainstream, so it isn't so much a matter of learning a new technology as it is a matter of learning a new paradigm, which necessarily means surfacing and unlearning things you already know, and perhaps confronting the uncomfortable feeling that things you thought were "fundamental," "have to be that way," aren't, and don't. I personally found this process liberating. But not everyone does.
-
Server Stack Options for Scala
If you want a mature REST API library, I recommend http4s. Be aware, though, that it’s based on purely-functional programming with Cats, cats-effect, and fs2, so if you’re not familiar with them or aren’t prepared to commit to the paradigm, the learning curve may be daunting, seem pointless, or both.
-
Sequential application of a constructor?
See also cats-effect and fs2. cats-effect gives you your IO Monad (and IOApp to run it with on supported platforms). fs2 is the ecosystem’s streaming library, which is much more pervasive in functional Scala than in Haskell. For example, http4s and Doobie are both based on fs2.
-
Grasping the concepts and getting them down to earth
Most important/known: * https://http4s.org/ - an HTTP client/server * https://github.com/typelevel/fs2 - streaming * https://github.com/tpolecat/doobie - JDBC
-
Relative popularity of programming languages on Hacker News
Scala devs are too busy wondering about free monads and F[Request[F] => Response[F]]. I am very pleased by http4s, Doobie, ScalaJS, and the whole ecosystem, really: https://http4s.org
-
http4s as a replacement for akka-http?
In reality, your performance issues will not be http4s, but something else. That being said, there are improvements that http4s can and is making, and I'm quite excited about the future 1.0 release, which has some important and fundamental performance improvements already, like a a 125% performance improvement on the plaintext benchmark from https://github.com/http4s/http4s/pull/6091 - and finally, yes, akka-http does have very good performance, but you can also get good performance out of http4s.
-
Is Scala a good choice for a data intensive web backend?
http4s for REST services.
-
Scala became Typelevel/Zio only ecosystem?
This is a long list of misunderstandings I don’t have the patience to unpack. Instead, let me refer you to the links in my top comment in the thread, then suggest you learn at least http4s, a purely-functional web service library that’s been used in production for a decade or so now.
-
Pleasant to use Scala libraries
I would say http4s and Doobie. Both are pure FP libraries in the Typelevel ecosystem. Both are exceptionally clear, extremely reliable, extremely pleasant to use… I like to point out http4s, in particular, is primarily a collection of types modeling the relevant RFCs. What behavior it has comes overwhelmingly from the underlying Cats, cats-effect, and fs2 libraries. This reflects the generality of those underlying libraries and the intense focus of the http4s team. The same applies to Rob Norris and Doobie, which tames JDBC as well as it can be tamed, IMO.
The most popular nowadays are - I guess - akka-http and http4s. You can also use Play if you don't want to start from scratch but prefer a framework-based approach.
Play
-
Reflex – Web apps in pure Python
My major complain here is that, as far as being a web framework there is precious little information here about the framework. How does this framework scale with multiple requests? What concurrency strategy is it using (threads, processes, actors, etc?). Is this opinionated (it doesn't seem so but it also doesn't say it isn't either). How does this work with popular libraries x,y,z. The full docs have a little bit more information, but not a ton. But mostly there are some cute toy examples and "built in python" and thats about it.
Lets compare this with for example play https://www.playframework.com/ I know from this that it built on Akka, its stateless, aims for predictable resource consumption, has non-blocking io, etc. There is a ton of really important information on what does this web framework actually do that is really important when you are making a choice of a framework.
I have no idea how good this framework is, but besides a few toy examples, I can't see anything that makes me thing "wow this is great I need to use this".
- Scala opensource projects
-
What is scala's modern Web API framework?
Scala 3 migration isn't as simple as migrating other apps, you can track the work at https://github.com/playframework/playframework/issues/11260
-
what library/framework should I use for backend development?
However do note, Play should be perfectly usable as well, and it's still maintained by the community: https://github.com/playframework/playframework/issues/11649
-
Why I selected Elixir and Phoenix as my main stack
In university I learned a bit of Java, so maybe I could use it professionally I guess?. There were many options to choose from. DropWizard, Spark, Play Framework. But the more documented one in the internet I found was Springboot, besides there were some courses in spanish and some friends that knew something about Springboot, so I give it a chance.
-
Make your zip packages for lambdas (and many more use cases) idempotent with a zip-drop-in replacement
See https://github.com/playframework/playframework/issues/10572 and https://github.com/sbt/sbt/issues/6235 for more details and context.
-
Pleasant to use Scala libraries
The most popular nowadays are - I guess - akka-http and http4s. You can also use Play if you don't want to start from scratch but prefer a framework-based approach.
- Why We’re Sticking with Ruby on Rails at GitLab
- O que estou fazendo?? Um projetinho de estudo.
-
Play Framework: first release based at Open Collective
release notes: https://github.com/playframework/playframework/releases/2.8.13
What are some alternatives?
Akka HTTP - The Streaming-first HTTP server/module of Akka
sttp - The Scala HTTP client you always wanted!
Spring Boot - Spring Boot
Scalatra - Tiny Scala high-performance, async web framework, inspired by Sinatra
ZIO - ZIO — A type-safe, composable library for async and concurrent programming in Scala
Quarkus - Quarkus: Supersonic Subatomic Java.
Finch.io - Scala combinator library for building Finagle HTTP services
Finatra - Fast, testable, Scala services built on TwitterServer and Finagle
zio-http - A next-generation Scala framework for building scalable, correct, and efficient HTTP clients and servers
Spray - A suite of scala libraries for building and consuming RESTful web services on top of Akka: lightweight, asynchronous, non-blocking, actor-based, testable
Lift - Lift Framework
Spring - Spring Framework