Alternatives to Orleans logo

Alternatives to Orleans

Akka, Dapr, Lens, Erlang, and RxJS are the most popular alternatives and competitors to Orleans.
56
114
+ 1
39

What is Orleans and what are its top alternatives?

Orleans is a framework that provides a straightforward approach to building distributed high-scale computing applications, without the need to learn and apply complex concurrency or other scaling patterns. It was created by Microsoft Research and designed for use in the cloud.
Orleans is a tool in the Concurrency Frameworks category of a tech stack.
Orleans is an open source tool with 9K GitHub stars and 1.9K GitHub forks. Here’s a link to Orleans's open source repository on GitHub

Top Alternatives to Orleans

  • Akka
    Akka

    Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM. ...

  • Dapr
    Dapr

    It is a portable, event-driven runtime that makes it easy for developers to build resilient, stateless and stateful microservices that run on the cloud and edge and embraces the diversity of languages and developer frameworks. ...

  • Lens
    Lens

    It is the only IDE you’ll ever need to take control of your Kubernetes clusters. It is a standalone application for MacOS, Windows and Linux operating systems. It is open source and free. ...

  • Erlang
    Erlang

    Some of Erlang's uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance. OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems. ...

  • RxJS
    RxJS

    RxJS is a library for reactive programming using Observables, to make it easier to compose asynchronous or callback-based code. This project is a rewrite of Reactive-Extensions/RxJS with better performance, better modularity, better debuggable call stacks, while staying mostly backwards compatible, with some breaking changes that reduce the API surface. ...

  • Netty
    Netty

    Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server. ...

  • Finagle
    Finagle

    Finagle is an extensible RPC system for the JVM, used to construct high-concurrency servers. Finagle implements uniform client and server APIs for several protocols, and is designed for high performance and concurrency. ...

  • Redux Observable
    Redux Observable

    It allows developers to dispatch a function that returns an observable, promise or iterable of action(s). Compose and cancel async actions to create side effects and more. ...

Orleans alternatives & related posts

Akka logo

Akka

860
942
88
Build powerful concurrent & distributed applications more easily
860
942
+ 1
88
PROS OF AKKA
  • 32
    Great concurrency model
  • 17
    Fast
  • 12
    Actor Library
  • 10
    Open source
  • 7
    Resilient
  • 5
    Scalable
  • 5
    Message driven
CONS OF AKKA
  • 3
    Mixing futures with Akka tell is difficult
  • 2
    Closing of futures
  • 2
    No type safety
  • 1
    Very difficult to refactor
  • 1
    Typed actors still not stable

related Akka posts

To solve the problem of scheduling and executing arbitrary tasks in its distributed infrastructure, PagerDuty created an open-source tool called Scheduler. Scheduler is written in Scala and uses Cassandra for task persistence. It also adds Apache Kafka to handle task queuing and partitioning, with Akka to structure the library’s concurrency.

The service’s logic schedules a task by passing it to the Scheduler’s Scala API, which serializes the task metadata and enqueues it into Kafka. Scheduler then consumes the tasks, and posts them to Cassandra to prevent data loss.

See more
Shared insights
on
AkkaAkkaKafkaKafka

I decided to use Akka instead of Kafka streams because I have personal relationships at @Lightbend.

See more
Dapr logo

Dapr

80
282
9
An open-source project to make it easier to build microservices
80
282
+ 1
9
PROS OF DAPR
  • 3
    Manage inter-service state
  • 2
    MTLS "for free"
  • 2
    App dashboard for rapid log overview
  • 2
    Zipkin app tracing "for free"
CONS OF DAPR
    Be the first to leave a con

    related Dapr posts

    Shared insights
    on
    IstioIstioDaprDapr

    At my company, we are trying to move away from a monolith into microservices led architecture. We are now stuck with a problem to establish a communication mechanism between microservices. Since, we are planning to use service meshes and something like Dapr/Istio, we are not sure on how to split services between the two. Service meshes offer Traffic Routing or Splitting whereas, Dapr can offer state management and service-service invocation. At the same time both of them provide mLTS, Metrics, Resiliency and tracing. How to choose who should offer what?

    See more
    Lens logo

    Lens

    96
    135
    4
    Open-source IDE to control your Kubernetes clusters
    96
    135
    + 1
    4
    PROS OF LENS
    • 2
      Keep track of cluster changes
    • 1
      Open Source
    • 1
      Easy management of multiple clusters
    CONS OF LENS
      Be the first to leave a con

      related Lens posts

      Erlang logo

      Erlang

      761
      705
      327
      A programming language used to build massively scalable soft real-time systems with requirements on high availability
      761
      705
      + 1
      327
      PROS OF ERLANG
      • 60
        Concurrency Support
      • 60
        Real time, distributed applications
      • 56
        Fault tolerance
      • 35
        Soft real-time
      • 31
        Open source
      • 21
        Functional programming
      • 20
        Message passing
      • 15
        Immutable data
      • 13
        Works as expected
      • 5
        Facebook chat uses it at backend
      • 4
        Practical
      • 4
        Knowledgeable community
      • 3
        Bullets included
      CONS OF ERLANG
        Be the first to leave a con

        related Erlang posts

        Sebastian Gębski

        Another major decision was to adopt Elixir and Phoenix Framework - the DX (Developer eXperience) is pretty similar to what we know from RoR, but this tech is running on the top of rock-solid Erlang platform which is powering planet-scale telecom solutions for 20+ years. So we're getting pretty much the best from both worlds: minimum friction & smart conventions that eliminate the excessive boilerplate AND highly concurrent EVM (Erlang's Virtual Machine) that makes all the scalability problems vanish. The transition was very smooth - none of Ruby developers we had decided to leave because of Elixir. What is more, we kept recruiting Ruby developers w/o any requirement regarding Elixir proficiency & we still were able to educate them internally in almost no time. Obviously Elixir comes with some more tools in the stack: Credo , Hex , AppSignal (required to properly monitor BEAM apps).

        See more

        Hello everyone, I plan on building a platform that supports 100s of forums out of the box, it would give the user the ability to create forums, where other users can comment, post images, and videos (the size of videos would be limited). Each forum would have the ability to trend. I have been doing a lot of research and I have arrived at Golang and Erlang as the backend languages and PostgreSQL as the DB. Erlang would be used for the routing of chats and messages, while Go would be used to manage the forums. We would also be implementing a one on one chat system like WhatsApp chat, where users can add contacts.

        Please I would like to know if the languages picked are appropriate for this project. Suggestions would be appreciated.

        See more
        RxJS logo

        RxJS

        978
        592
        19
        The Reactive Extensions for JavaScript
        978
        592
        + 1
        19
        PROS OF RXJS
        • 5
          Easier async data chaining and combining
        • 3
          Steep learning curve, but offers predictable operations
        • 2
          Easier testing
        • 2
          Ability to build your own stream
        • 2
          Works great with any state management implementation
        • 1
          Lot of build-in operators
        • 1
          Simplifies state management
        • 1
          Observable subjects
        • 1
          Great for push based architecture
        • 1
          Documentation
        CONS OF RXJS
        • 3
          Steep learning curve

        related RxJS posts

        Netty logo

        Netty

        227
        366
        14
        Asynchronous event-driven network application framework
        227
        366
        + 1
        14
        PROS OF NETTY
        • 8
          High Performance
        • 3
          Easy to use
        • 3
          Just like it
        CONS OF NETTY
        • 2
          Limited resources to learn from

        related Netty posts

        Finagle logo

        Finagle

        67
        98
        10
        An extensible RPC system for the JVM
        67
        98
        + 1
        10
        PROS OF FINAGLE
        • 4
          Fast
        • 3
          HTTP-friendly
        • 3
          Open Source
        CONS OF FINAGLE
          Be the first to leave a con

          related Finagle posts

          Redux Observable logo

          Redux Observable

          53
          43
          0
          A powerful middleware for Redux using RxJS
          53
          43
          + 1
          0
          PROS OF REDUX OBSERVABLE
            Be the first to leave a pro
            CONS OF REDUX OBSERVABLE
              Be the first to leave a con

              related Redux Observable posts