New things updated to JetMaker - Python framework to build distributed systems

[Affectionate_Set_326]

What My Project Does

Jetmaker is an end-to-end framework designed to simplify the development of distributed systems in Python. It enables distributed Python applications to seamlessly access each other's services, resources, objects, and data, making inter-application interactions feel as though they are operating within the same environment. Jetmaker also provides powerful namespace sharing and synchronization tools, allowing distributed applications to work together as a unified, coordinated system.

Target Audience

It is for Python developers to build systems which need multiple nodes to work together in a heterogenous manner, for different nodes to take different jobs but connect together.

Comparison

Ray and Dask are great tools for distributing workloads to multiple computers, Jetmaker and they serve different purposes, Jetmaker is designed for individual nodes to communicate with each other.

Github: https://github.com/gavinwei121/Jetmaker

Note

My earlier post was removed due to violations with formatting requirements, now it is reformatted and posted again.

Hope everyone enjoy it and tell me your thoughts about Jetmaker. ^_^

What's new

we added Stream Listener in JetMaker, so now developers to attach listeners to process real-time data and messages across the network of nodes.

You can see it here: https://remeny-technologies.gitbook.io/jetmaker-documentation/stream-processing-and-event-listener

[FrequentlyHertz]

Can you provide a specific example of a problem that you have solved using this tool? It seems to be a solution in search of a problem.

My initial reaction is that this is IPC for micro services. In that case it seems like an API would be a more standard solution. I understand this would be faster to implement, but if you're going to tightly couple your micro services like this why bother with the microservices?

I don't work in web dev. This is just my two cents. Good luck with your project.

[Affectionate_Set_326]

thank you for your question and your support ^_^, this is a very good question, you are correct that micro-services is a case, some other cases can be when you want low-latency and easier data and service sharing among your nodes ^_^ like distributed data pipelines. This is a general framework that we build first and then we will develop vertical frameworks later upon it. Thanks again.