The problem is when using sbt:assembly the default merge strategy excludes all the reference.conf files as per If multiple files share the same relative path (e.g. a resource named application.conf in multiple dependency JARs), the default strategy is to verify that all candidates have the same contents and error out otherwise. The solution is to … Read more
The optimal number of threads to use depends on several factors, but mostly the number of available processors and how cpu-intensive your tasks are. Java Concurrency in Practice proposes the following formal formula to estimate the optimal number of threads: N_threads = N_cpu * U_cpu * (1 + W / C) Where: N_threads is the … Read more
You can use scala.collection.JavaConversions.asScalaBuffer to convert the Java List to a Scala Buffer, which has a toList method, and a Scala List is a collection.immutable.Seq.
val result: Future[(Class1, Class2, Class3)] = for { _ <- Future.unit val f1 = process1 val f2 = process2 val f3 = process3 v1 <- f1 v2 <- f2 v3 <- f3 } yield (v1, v2, v3)
As of version 2.x you achieve this with the following code: import akka.stream.scaladsl.StreamConverters … val inputStream: InputStream = entity.dataBytes .runWith( StreamConverters.asInputStream(FiniteDuration(3, TimeUnit.SECONDS)) ) See: http://doc.akka.io/docs/akka-stream-and-http-experimental/2.0.1/scala/migration-guide-1.0-2.x-scala.html Note: was broken in version 2.0.2 and fixed in 2.4.2
By default the dispatcher provided by Akka is one with a fork-join-executor, and the default parallelism values are these: parallelism-min: 8 parallelism-factor: 3.0 parallelism-max: 64 You can see all of this in the documentation. There is a section named: Listing of the Reference Configuration Here is the relevant part of the configuration file (I only … Read more
as you said, To make sure this wasn’t the API’s server issue, I replicate the same query using Node.js (Express and Request libs) and it works every time. It makes me almost sure is a spray bug. your code in scala send requests with HTTP pipelining feature, do you send the requests with HTTP pipelining … Read more
The Microservices architectural style tries to allow organizations to have small teams own services independent in development and at runtime. See this read. And the hardest part is to define the service boundaries in a useful way. When you discover that the way you split up your application results in requirements impacting multiple services frequently … Read more
I’m working on RxJava and I did some evaluations on Akka-Streams and Reactor recently. As far as I can tell with all the libraries, they converge to a single concept called Reactive-Streams so you can go back and forth between the implementations. I believe RxJava is the most generic of all, has zero dependencies on … Read more
One of the solution I’ve found is to use a: import akka.http.scaladsl.server.directives.DebuggingDirectives val clientRouteLogged = DebuggingDirectives.logRequestResult(“Client ReST”, Logging.InfoLevel)(clientRoute) Http().bindAndHandle(clientRouteLogged, interface, port) Which can easily log the request and result in raw(bytes) format. The problem is that those logs are completely unreadable. And here is place where it became complicated. Here is my example that encode … Read more