mats3
lunatic
mats3 | lunatic | |
---|---|---|
20 | 86 | |
59 | 4,533 | |
- | 0.4% | |
8.7 | 5.7 | |
7 days ago | about 2 months ago | |
Java | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mats3
-
Flawless – Durable execution engine for Rust
The “restart from where it failed”-aspect was a big reason for why I made Mats3. It is message-based, async, transactional, staged stateless services, or message-oriented asynchronous RPC. Due to the transactionality, and the “state lives on the wire”, if a flow fails, it can be restarted from where it left off.
https://mats3.io
-
A Modern High-Performance Open Source Message Queuing System
I am truly finding it hard to explain it. I have tried along a dozen angles. I actually think it is a completely new concept - and that might be the problem.
There is an illustration on the front-page: https://mats3.io/
Here's a set of small answers to "What is Mats?": https://github.com/centiservice/mats3/blob/main/README.md#wh...
Here's a way to code up Mats3 endpoints using JBang and a small toolkit which makes it extremely simple to explore the ideas: https://github.com/centiservice/mats3/blob/main/README.md#wh...
If you read these and then get it, I would be extremely happy if you gave me a sentence or paragraph that would have led you to understanding faster!
The use of JMS is just a transport. I could really have used anything, incl. any MQ, or ZeroMQ, or plain TCP - or just a shared table in a database.
Wrt. WebSockets, that is a transport typically between a server, and a end-user client, e.g. an iOS App. Actually, there's also a "sister project", MatsSockets, that bring the utter async-ness of Mats3 all the way out to the client, e.g. a webpage or an app. https://matssocket.io/
NATS is just a message queue, with some ability to orchestrate. I do not like this concept of orchestration as an external service, that is one of the founding ideas of Mats3: Do the orchestration within each service, as you would do if you employed REST as the ISC mechanism.
-
JBang + Spring + Mats3: Setting up a multi-stage Async Messaging-based Endpoint in very few lines
Read more about mats3 here: https://mats3.io/
-
Where is the "router"? on the client or MOM side?
I've made a Java library to facilitate the latter. https://mats3.io/ - you can start reading here: https://mats3.io/docs/message-oriented-rpc/, or test out some code right away, using JBang, here: https://mats3.io/explore/jbang-mats/
- Messaging with a call stack: Async inter-service "RPC" with arbitrary call depth featuring "local variables" on a stack.
- A detailed comparison of REST and gRPC | Kreya
-
Mats3 with JBang: An exploration of Message-Oriented Async RPC with self-contained java programs
I have explained about this on the frontpage of Mats3: https://mats3.io/, and more in-depth in the first step of the "Walkthrough": https://mats3.io/docs/message-oriented-rpc/ - and even more into it at "Rationale for Mats", here: https://mats3.io/background/rationale-for-mats/
-
JBang and Mats3: Explore Mats3 Message-Oriented Async RPC with JBang “Java Exec”
JBang’s tagline: “Lets Students, Educators and Professional Developers create, edit and run self-contained source-only Java programs with unprecedented ease.”
Mats3’s tagline: “Message-Oriented Async RPC. Message-based Interservice Communication made easy! Naturally resilient and highly available microservices, with great DevX and OpsX.”
JBang is a cool "execute single Java source file with dependencies" solution, which offers a simple way to test new libraries. The article tries to showcase Mats3's core concepts through a series of JBang scripts.
To streamline the process, a small library called 'MatsJbangKit' has been developed, which not only takes care of pulling up the Mats infrastructure but also depends on all the necessary dependencies. This means users only need to reference this single library in their JBang scripts. The aim is to pique curiosity and inspire further exploration of Mats3 and its potential.
If you like it, a star on Github would be much appreciated: https://github.com/centiservice/mats3
-
Why messaging is much better than REST for inter-microservice communications
This is a "tack on"-tool to the otherwise fully async nature of Mats/messaging.
> For this to really work well, the message passing has to be integrated with the CPU dispatcher
It sounds like you are 100% set on speed. This is not really what Mats is after - it is meant as a inter-service communcation system, and IO will be your limiting factor at any rate. Mats sacrifices a bit of speed for developer ergonomics - the idea is that by easily enabling fully async development of ISC in a complex microservice system, you gain back that potential loss from a) actually being able to use fully async processing (!), and b) the inherent speed of messaging (it is at least as fast as HTTP, and you avoid the overhead of HTTP headers etc.
It is mentioned here, "What Mats is not": https://github.com/centiservice/mats3#what-mats-is-not
- Mats3: Message-Oriented Async Remote Procedure Calls
lunatic
-
Spinkube: Running WASM in Kubernetes
This reminds me of Lunatic [1], an Erlang-inspired runtime for WebAssembly. Unfortunately it seems like development stalled some months ago.
[1] https://lunatic.solutions/
-
Spin 2.0 – open-source tool for building and running WASM apps
you can check out https://github.com/lunatic-solutions/lunatic for that
-
Flawless – Durable execution engine for Rust
Very cool, and the approach demonstrated might be of interest to a similar problem we have in Ambient (our WASM game runtime that has competing processes that may need to retry interactions.)
That being said - what’s the relation to Lunatic [0]? Are you still working on Lunatic? Is this a side project? Or is it something completely separate?
[0]: https://lunatic.solutions/
-
Async Rust Is A Bad Language
Curious too. I follow Lunatic [0] as a candidate for future use, and also wasmCloud [1].
[0] https://lunatic.solutions/
[1] https://wasmcloud.com
- Write Elixir NIFs in Rust
- A WASI VM?
- how can I add dynamic loading to do "plugins" for my Rust app?
-
Wasix, the Superset of WASI Supporting Threads, Processes and Sockets
Check out Lunatic https://lunatic.solutions/
-
Elixir and Rust is a good mix
There's a couple of Rust libs and frameworks inspired on Erlang in 'best of both worlds' attempts, such as https://lunatic.solutions
I found others like Lunatic before, but cannot remember right now.
-
Anything close beam/otp for other languages?
There is a really good initiative called Lunatic : https://lunatic.solutions/
What are some alternatives?
blazingmq - A modern high-performance open source message queuing system
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
OpenMAMA - OpenMAMA is an open source project that provides a high performance middleware agnostic messaging API that interfaces with a variety of proprietary and open source message oriented middleware systems.
hyperscan - High-performance regular expression matching library
cadence - Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
actix - Actor framework for Rust.
ntf-core - Sockets, timers, resolvers, events, reactors, proactors, and thread pools for asynchronous network programming
wit-bindgen - A language binding generator for WebAssembly interface types
mosquitto - Eclipse Mosquitto - An open source MQTT broker
wasmCloud - wasmCloud allows for simple, secure, distributed application development using WebAssembly components and capability providers.
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
bastion - Highly-available Distributed Fault-tolerant Runtime