Hi Richard, > 22 jan 2015 kl. 06:14 skrev [email protected]: > > Hi all, > > It's an exciting time for Akka with the imminent release of akka-http (as > announced in 2013 in this thread > <https://groups.google.com/forum/#!searchin/akka-user/Akka-HTTP/akka-user/sMB8tjYPOLA/ywU2G9baqwgJ> > and more recently reaffirmed in this other thread > <https://groups.google.com/forum/#!searchin/akka-user/Akka-HTTP/akka-user/bIdV9HlUHkg/R_zeAOZFdI4J>)! > If I'm not mistaken, that would be the latest milestone: > > https://github.com/akka/akka/tree/releasing-akka-stream-and-http-experimental-1.0-M2 > > <https://github.com/akka/akka/tree/releasing-akka-stream-and-http-experimental-1.0-M2> > > That's awesome news... but this kind of transition always pose a challenge on > new projects: should one use the new (experimental) milestone release or > stick to the original components for a few months and then have to go through > a migration (that can potentially impact system design) on a "newborn"? Or go > the other way around and risk using something that's not stable?
Since Akka HTTP is not yet production ready my recommendation is to use spray.io at this point. This will eventually change, and we will announce that when a sufficiently stable Akka HTTP release is made. > I realise there's no easy answer besides the standard "only use stable > releases for production". But on the other hand, how far are we from a > production release of akka-http? That will be a few months, still. > How stable is the milestone 2? Many things work already, but a few essential features are still missing (client, SSL, websockets). Some details of the API may still change, the most stable part is probably the Scala routing DSL (where several kinds of directive are also still missing). > How painful will be the migration from software based on current spray.io to > the new aka-http? We intend to make this as painless as we can, but there are a few improvements being done in the transition that break source compatibility. > So, what have you guys been doing when confronted with these choices? Has > anyone evaluated these 2 systems recently? It would be great to hear stories (of successes or problems) from people who tried to migrate already, but I appreciate that it might be a little early still. Regards, Roland > > Thanks for your thoughts on this. > > Cheers, Richard > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ <http://akka.io/docs/> > >>>>>>>>>> Check the FAQ: > >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html > >>>>>>>>>> <http://doc.akka.io/docs/akka/current/additional/faq.html> > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > >>>>>>>>>> <https://groups.google.com/group/akka-user> > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/akka-user > <http://groups.google.com/group/akka-user>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. Dr. Roland Kuhn Akka Tech Lead Typesafe <http://typesafe.com/> – Reactive apps on the JVM. twitter: @rolandkuhn <http://twitter.com/#!/rolandkuhn> -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
