Akka Reviews and details

Social recommendations and mentions

• Modern Async Primitives on iOS, Android, and the Web

  Kotlin also has a construct for asynchronous collections/streams. Kotlin's version of AsyncSequence is called a Flow. Just as Swift's AsyncSequence builds upon prior experience with RxSwift and Combine, Kotlin's Flow APIs build upon earlier stream/collection APIs in the JVM ecosystem: Java's RxJava, Java8 Streams, Project Reactor, and Scala's Akka. - Source: dev.to / 5 months ago

• What are the current hot topics in type theory and static analysis?

  First-class distributed and multicore computing. Swift has first-class “actors” and “distributed” methods. Unison, Erlang, and Elixir are built with distributed being one of the #1 concerns. Though first-class is not super common and I don't really expect it to be because usually libraries are enough (e.g. Scala has Akka and is used WIDELY for distributed); whereas something like linear types and typed effects,... Source: 12 months ago

• Anything close beam/otp for other languages?

  Akka is a library that implements the actor model for JVM languages. Mainly in Scala, but you can use it in Java too, and maybe others. It doesn't feel as ergonomic as Elixir, but if Elixir is too "out there" for the decision makers in your case, this might be a friendlier alternative. Source: about 1 year ago

• Kalix: Move to the Cloud. Extend to the Edge. Go Beyond.

  Kalix builds on the lessons we have learned from more than a decade of building Akka (leveraging the actor model) and our experience helping large (and small) enterprises move to the cloud and use it in the most time, cost, and resource-efficient way possible. - Source: dev.to / about 1 year ago

• About Elixir and the microservices architecture

  Note Akka, the Java & friends framework, is working with the actor model and have as main inspiration Erlang to mimic some features of the BEAM on top of the JVM. - Source: dev.to / over 1 year ago

• Akka will no longer be Open Source

  If I hear about Actor model, the first thing that comes to my mind is the popular Open Source library Akka. - Source: dev.to / over 1 year ago

• We Are Changing the License for Akka

  I don't think that the Akka change is aimed at cloud providers. Akka is a toolkit for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala [1]. It's not possible for AWS to offer their own "Akka service" the way they offered Redis through ElastiCache. This change affects companies that build software using Akka, many of which may not be software-focused. For... - Source: Hacker News / over 1 year ago

• I need to create an API, but I don't know what framework to use. What would you choose, of you were me, and scalability is a quite important factor?

  However, if you really expect a lot of users (especially concurrent ones) to use your API, you should delve into the world of reactive programming. Use tools like RxJS (JS/TS) or Project Reactor (Java) in such a case, preferably in combination with a broker like Kafka or RabbitMQ. R2DBC is also great for a data store. Then of course if you want to go one step further, there also exists the less popular but very... Source: over 1 year ago

• What are Project Loom's Virtual Thread main advantages over platform threads

  What you are describing is more or less the actor programming model. (If you’ve heard of Akka, then you’ve heard of the actor model.) Loom is an enabling technology for implementing the actor model on the (vanilla) JVM, and a lot of people are looking forward to that, including me! So that’s a perfectly valid approach. Source: almost 2 years ago

• Features of a dream programming language: 2nd draft.

  Reactive. Inspired by Functional Reactive Programming, and Elm, and The Reactive Manifesto. Though the latter is geared at distributed systems, it could also be a model for local computation (rf. Actor model, and Akka). The programming language should make default and implicit the features of reactivity and streaming, as opposed to preloading and batch processing. (Reactive Streaming Data: Asynchronous... - Source: dev.to / about 2 years ago

• Scala 3 Reflection

  I want to create a framework for developers to deploy Akka based applications https://akka.io. Source: about 2 years ago

• Apache Cassandra: Best use practices in the search for performance ?!

  Akka, extremely resilient Scala framework for “message-driven”;. - Source: dev.to / over 2 years ago

• Don’t start with microservices – monoliths are your friend

  But there's more to the topic of microservices. Seems like all the conversation focuses on deployment pain. You can build a service with something like Akka or Moleculer where the modules act independently and have some message passing and resilience from each other, but they can still all live in one codebase, one process, and deployed as one unit. It works fine and isn't painful at all. And maybe down the line... Source: over 2 years ago

• About Halo game's backend

  If you're interested in the actor model, there's also a JVM implementation called Akka and a .NET port called Akka.NET. Source: over 2 years ago

• Delphi 11 Alexandria Has Been Released

  Please show me something like this: https://akka.io/ Or this: https://zio.dev/ Or this: https://github.com/milessabin/shapeless. Source: over 2 years ago

• Scala or Go: Who Wore It Better?

  Scala became really popular with the advent of "Big Data" because functional programming lends itself so naturally to analytics, and the learning curve for Modern LISPs like Haskell and Clojure is too high for too many. Apache Spark is built in Scala, and when it got big, Scala got big. Since then Scala has also become a popular language for other domains including reactive web applications and microservices... - Source: dev.to / over 2 years ago

• Advice on Multithreading Approach

  You might want to consider a lightweight reactive library like Akka or Vert.x which will make more efficient use of threads, and takes the work away of having to write a concurrent, distributed application, so you can just focus on writing your poker app. Source: over 2 years ago

• Language-assisted Flattening

  I'd say your friend got it basically right for actors (guaranteed deadlock free resilient massive distributed concurrent computation -- note: not parallelism) ala Akka. This is apparently what Alan Kay intended to happen for Smalltalk before he essentially lost control of its evolution. In the actor model, messages are not function calls, because you don't get a value back in the normal sense of a function having... Source: almost 3 years ago

• jLovely Lightbend

  We came across Lightbend quite a while ago. If you don't know Lightbend, they are the company behind the Akka toolkit (as well as Scala, Play Framework, Lagom, and others). Hundreds of thousands of Java and Scala developers around the world use these products. Our first collaboration was at the Scala Love podcast, where Lukas Ritz and Seth Tisue talked about Scala and its compiler's internals. The episode is full... - Source: dev.to / almost 3 years ago

• There are a *lot* of actor framework projects on Cargo.

  Speaking as someone who has used Erlang longer than most, who created a pre-Elixir-like language for Erlang's BEAM VM, and who routinely listens to Carl Hewitt's rants about why Erlang actors are bad, and who tried to make a Ruby actor library after using innumerable other library-level actor solutions... Source: almost 3 years ago

• Errors as Values: Free Yourself From Unexpected Runtime Exceptions

  First used (from my limited knowledge) in the Apollo Guidance Computer, and later popularized by Erlang, rather than avoid crashes with lots of work and still missing them, many developers today are just accepting crashes can happen. In Erlang/Elixir and the Akka framework, it’s common to create a lightweight process that’s sole job is to watch child process. The child process is what runs the actual code. If the... - Source: dev.to / about 3 years ago