Spray or Akka-http

383 views
Skip to first unread message

Fernando Benjamin

unread,
Mar 11, 2015, 4:48:53 PM3/11/15
to spray...@googlegroups.com
After reading the closing comment on this issue https://github.com/spray/spray/issues/1016,
I would like to know if it makes sense to use spray for new projects?
Or can I start using akka-http? And where can I find the source?

thnx



Stevo Slavić

unread,
Mar 11, 2015, 6:06:37 PM3/11/15
to spray...@googlegroups.com
Hello Fernando,

As always, it depends. If it's just for that issue, I wouldn't, yet. Btw, I've add my comment to that issue, with a workaround that can be applied with existing spray APIs.

Since akka-http (experimental) is part of akka, sources are in akka github repository, release-2.3-dev branch (see https://github.com/akka/akka/tree/release-2.3-dev ). Besides binaries, source jars are published with releases and available on Maven Central repo - just look under http://repo1.maven.org/maven2/com/typesafe/akka/ for all artifacts starting with akka-http.

Most recent release of akka-http (experimental) is 1.0-M4. M stands for milestone. In recent thread on akka user mailing list it was explained that milestone is considered to be pre-alpha code (see https://groups.google.com/d/msg/akka-user/PCNEqTBTWpU/SYTYeiZg-yIJ ).
akka-http is based on akka-streams, another new experimental akka module. In a different akka user mailing list topic it was mentioned by akka team that the performance tuning is not goal for milestones, mostly they try to reach api stability first (see https://groups.google.com/d/msg/akka-user/zI0iXocMtig/6y9jdlAsRLgJ ).

So, if planning to release/go-live soon, before akka-http and akka-streams reaches general availability, I know I wouldn't go with akka-http yet.
Otherwise, if you can afford luxury and wait for GA, starting with akka-http should cut down the costs - with spray one will eventually have to migrate to akka-http. I guess akka team is eager to get more feedback and testing from community on akka-http APIs. You have opportunity to shape the APIs before they become generally available, later they would be harder to change - as Joshua Bloch phrased it "Public APIs are forever - one chance to get it right" (see http://lcsd05.cs.tamu.edu/slides/keynote.pdf ). Be aware also, that akka modules labeled as experimental are not labeled like that just for fun. People got burnt in the past depending too much on experimental akka features/modules (see https://groups.google.com/d/msg/akka-user/8fZ75MlVEYc/YaZGsysG8mcJ ). I personally doubt akka-streams and akka-http will have same destiny as akka io pipelines, still be cautious when making your decision.

All this may bring you to yet another question, when will akka-http/akka-streams be released - some hints you can find in related recent discussion on akka user mailing list at https://groups.google.com/d/msg/akka-user/ZA8aAec4NQE/qTvm69MEAggJ and akka team blog post about akka roadmap https://typesafe.com/blog/akka-roadmap-update-dec-2014

Kind regards,
Stevo Slavic.

--
You received this message because you are subscribed to the Google Groups "spray.io User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spray-user+...@googlegroups.com.
Visit this group at http://groups.google.com/group/spray-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/spray-user/27cfa770-8735-40dc-b991-aad59e5bdd58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mathias Doenitz

unread,
Mar 12, 2015, 5:13:27 AM3/12/15
to spray...@googlegroups.com
Thanks, Stevo, for this excellent and comprehensive answer!

Cheers,
Mathias

---
mat...@spray.io
http://spray.io
> To view this discussion on the web visit https://groups.google.com/d/msgid/spray-user/CAAUywg_67MUeNaFkNW4PczB0wOhthX-r9N%2BsagTTfwvhZRqCFA%40mail.gmail.com.

Fernando Benjamin

unread,
Mar 12, 2015, 5:24:20 PM3/12/15
to spray...@googlegroups.com
Hello Stevo,

Thank you very much for this detailed answer.

Harit Himanshu

unread,
Jun 12, 2015, 3:23:18 AM6/12/15
to spray...@googlegroups.com
Its been couple of months and situation may have changed so though of asking again

I am planning to build a new project that would serve as an API Server. I wanted to check if I should be using Spray or akka-http?

Also, if I start using Spary.io, this may get deprecated soon once akka-http gets released, right?

so I am confused as you could see

Thanks

Mathias Doenitz

unread,
Jun 16, 2015, 8:05:35 AM6/16/15
to spray...@googlegroups.com
Harit,

as of this point spray is still the more stable and more efficient solution.
So, if you don’t have any special needs with regard to streaming requests and/or responses you’ll probably be fine with spray for the time being.

> Also, if I start using Spary.io, this may get deprecated soon once akka-http gets released, right?

spray will be supported for another 2 years or so.
That being said, all new development will happen on akka-http, so you shouldn’t expect any new major features coming into spray.

Cheers,
Mathias

---
mat...@spray.io
http://spray.io

> --
> You received this message because you are subscribed to the Google Groups "spray.io User List" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to spray-user+...@googlegroups.com.
> Visit this group at http://groups.google.com/group/spray-user.
> To view this discussion on the web visit https://groups.google.com/d/msgid/spray-user/26a66a26-f7bd-4000-97eb-06a3e2d3cbd8%40googlegroups.com.

Marios Papasofokli

unread,
Jun 26, 2015, 3:30:14 AM6/26/15
to spray...@googlegroups.com
Hello Mathias,

Since spray will not be supported after two years, should we expect spray-cache to be moved in Akka as well at some point?

Thanks in advance,

Marios Papasofokλi
Reply all
Reply to author
Forward
0 new messages