delta-elixir
proposals
delta-elixir | proposals | |
---|---|---|
8 | 60 | |
336 | 63 | |
1.8% | - | |
5.8 | 4.2 | |
16 days ago | 8 days ago | |
Elixir | ||
GNU General Public License v3.0 or later | MIT License |
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.
delta-elixir
-
Is Go the best language to build a web page with a collaborative text field?
I'm exploring web stacks to build a multiplayer text editor. Elixir's Delta has been recommended to me.
-
Would you use Phoenix LiveView to build a collaborative text field?
Definitely checkout Slabâs Operational Transform library Delta as well. I think conventional wisdom is that CRDTs can be really helpful when there is no single source of truth (i.e. a server), but OT can simplify things when there is.
-
Is there an equivalent to Yjs in Elixir's Phoenix?
For the particular goal of text collaboration, there are also operational transforms. There is a library maintained by the folks at Slab: https://slab.com/blog/announcing-delta-for-elixir/
-
Ask HN: What tech stack would you use to build a new web app today?
Yeah offline or complex client side state management is a good use case for Javascript. There are Hooks and Push Events with Liveview for real time integrations with Liveview in those scenarios. In my experience offline requirements are rare and often in mobile scenarios where a native or Flutter-like approach is a good option.
Complex client side state or collaborative features might use something like https://github.com/slab/delta-elixir or https://www.inkandswitch.com/local-first/ which is where I'd want JS.
- Delta (OT) for Elixir
- Delta: Operational Transforms for Elixir
-
Track content and changes with Delta in Elixir
Here's a little context on Delta (https://github.com/slab/delta-elixir) and the linked blog post:
Delta is a format to describe documents' contents and how it changes over time. This is a core piece of technology at Slab, that powers our real-time collaboration engine, thanks to the built-in support for Operational Transform (think multiple users working together in Google docs).
Though we've been using it internally for almost 4 years now, we're finally open-sourcing it to the wider Elixir community.
Would love your feedback!
-
Announcing Delta â Operational Transform in Elixir
Here's a little context on Delta and the linked blog post:
proposals
-
Is there an alternative for Airflow for running thousands of dynamic tasks?
Check out temporal.io open source project. It was built at Uber for large scale business-level processes. So any data pipelines are low-rate use cases by definition.
-
KuFlow as a Temporal.io-based Workflow Orchestrator
With KuFlow it is also possible to work with serverless workflows apart from Temporal.io, we explain it in this blog entry, but in summary, almost as a no-code tool, the correct use It would be a rather low-code tool; in just a matter of minutes with our drag-and-drop tool, you can have a workflow that interacts with one or more users of the organization.
-
How to handle background jobs in Rust?
Otherwise you may want to look into Kafka or Fluvio to ensure that task runs at least once. If you're doing something like batch operations as a background task, Temporal is another great option.
-
No-code or Workflow as code? Better both
The runtime is developed using Temporal, which is one of the main tools that we are currently using at KuFlow. Thanks to, all the workflow executions are robust: your application will be durable, reliable, and scalable.
-
Temporal Programming, a new name for an old paradigm
Hmmm I got confused by the name. I thought it's related to https://temporal.io/
-
Possible innovations in Event Sourcing frameworks.
Have you looked at temporal.io open source platform? It uses event sourcing as an implementation detail. But it greatly simplifies the user experience compared to "raw event sourcing."
-
After Airflow. Where next for DE?
Rewrite Airflow on top of temporal.io. This way, you get unlimited scalability and very high reliability out of the box and would be able to innovate on the features that matter for DE.
-
Show HN: Retool Workflows â Cronjobs, but better
Hi all, founder @ Retool here. Over the past year, weâve been working on Retool Workflows; a fast way for engineers to automate tasks with code. We started building the product because we ourselves (as developers) were looking for something in-between writing cron jobs (which involves a lot of boilerplate) and Zapier (which oftentimes isnât customizable enough, since it doesnât _really_ support writing code).
Workflows is a code-first automation tool: youâre _expected_ to write code, but we handle all the boilerplate for you. For example: out-of-the-box integration with 80+ resources (you probably donât want to be trying to figure out OAuth 2.0 with Salesforce!), monitoring and observability (so you can see the output of every run in the past, and immediately be notified if something goes wrong), and permissions (e.g. some Okta groups can see the outputs of Workflows, but canât change the code itself).
Right now, the product is cloud-only, but weâre hard at work at an on-prem, self-hosted version (in a Docker image). If youâre interested in that version, feel free to email us at [email protected]. We aim to get it out in the next few weeks. Self-hosted Retool is responsible for a large portion of our usage today, and weâre excited to be supporting Workflows too.
All Retool plans now include 1GB of Workflows throughput, which we think is quite generous (80% of active Workflows users are below 1GB). We donât bill by run at all, so youâre welcome to run as many workflows as you want.
We use a bunch of interesting technology for Workflows; we are, for example, using Temporal (https://temporal.io/) under the hood. Thatâs something weâre going to be writing a blog post about later. (Weâve been hard at work on the launch, hah.)
-
How KuFlow supports Temporal as a worfkows engine for our processes?
In such a diverse world, it would be boring to have a single way of doing things. That's why at KuFlow we support different ways to implement the logic of our processes and tasks. And in this post, we will talk about one of them, the orchestration through Temporal, which gives us a powerful way to manage our workflows.
- Library for manage tasks when make a workflow automation.
What are some alternatives?
htmx - </> htmx - high power tools for HTML
conductor - Conductor is a microservices orchestration engine.
nexus-prisma - Prisma plugin for Nexus
temporalite-archived - An experimental distribution of Temporal that runs as a single process
Plausible Analytics - Simple, open source, lightweight (< 1 KB) and privacy-friendly web analytics alternative to Google Analytics.
zenml - ZenML đ: Build portable, production-ready MLOps pipelines. https://zenml.io.
delta_crdt_ex - Use DeltaCrdt to build distributed applications in Elixir
seldon-core - An MLOps framework to package, deploy, monitor and manage thousands of production machine learning models
memento - Simple + Powerful interface to the Mnesia Distributed Database đž
kubemq-community - KubeMQ is a Kubernetes native message queue broker
cachex - A powerful caching library for Elixir with support for transactions, fallbacks and expirations
nextjs-cron - Cron jobs with Github Actions for Next.js apps on Vercelâ˛