Hi Reid, Thanks for sharing. I'll take the same approach, since I also don't expect much incompatibility.
Cheers, Richard On Tuesday, 27 January 2015 07:57:04 UTC+10, Reid Spencer wrote: > > Hi Richard, > > I faced exactly the dilemma you describe in my project. After reviewing > the plans (and code) for akka-http and spray.io, I concluded that there > would be "enough" similarity for my project to move forward with spray.io > and convert to akka-http when it is ready. As my project is new, I'm not as > production leery as some, but it is still very important to me to not be > breaking my project's clients. I think that as Roland suggested starting > with Spray and migrating to akka-http when you're comfortable that it is > good enough ought to be the way to go. In particular, I have already > compiled the routing DSL part of my code to use akka-http and other than > the import statements, it was all compatible. I guess I don't use the > unsupported directives. :) > > Reid. > > On Thursday, January 22, 2015 at 12:14:12 AM UTC-5, [email protected] > wrote: >> >> 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 >> >> 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? >> >> 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? How stable is the milestone 2? How painful >> will be the migration from software based on current spray.io to the new >> aka-http? >> >> So, what have you guys been doing when confronted with these choices? Has >> anyone evaluated these 2 systems recently? >> >> Thanks for your thoughts on this. >> >> Cheers, Richard >> > -- >>>>>>>>>> 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.
