mria
pg_net
mria | pg_net | |
---|---|---|
4 | 4 | |
106 | 171 | |
4.7% | 6.4% | |
7.2 | 7.2 | |
25 days ago | about 2 months ago | |
Erlang | PLpgSQL | |
Apache License 2.0 | 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.
mria
-
How EMQX Under the New Architecture of Mria + RLOG Achieves 100M MQTT Connections
Mria is an open source extension to Mnesia that adds eventual consistency to clusters. Most of the features described earlier still apply to it, the difference is how data is replicated between nodes. Mria switched from a full mesh topology to a mesh+star topology. Each node assumes one of two roles: core node or replicant node.
-
Reaching 100M MQTT Connections with EMQX 5.0
In EMQX 5.0, we attempted to mitigate this issue in a new DB backend type called RLOG (as in replication log), which is implemented in Mria. Mria is an extension to the Mnesia database that helps it scale horizontally by defining two types of nodes: i) core nodes, which behave as usual Mnesia nodes and participate in write transactions; ii) replicant nodes, which do not take part in transactions and delegate those to core nodes, while keeping a read-only replica of the data locally. This helps to reduce the risk of split-brain scenarios and lessens the coordination needed for transactions, since fewer nodes participate in it, while keeping read-only data access fast, since data is available locally for reading in all nodes.
-
Challenges and Solutions of EMQX Horizontal Scalability - MQTT Broker Clustering Part 3
Mria is an open-source extension to Mnesia that adds eventual consistency to the cluster.
-
Show HN: Multiplayer Demo Built with Elixir
> write-up soon as a guide for Python developers moving to Elixir
Awesome initiative!
> ETS as a KV/document store to hold user and application state and then reacting to changes in to that the way you are here
This is actually pretty interesting. I can't speak to ETS but Mnesia has replication and you can expose the replication log using something like https://github.com/emqx/mria. I've only had a cursory look at this so I could be wrong about its capabilities but it would be an awesome extension to the new Realtime if possible.
pg_net
- PostgreSQL Is Enough
-
Supabase Wrappers: A Framework for Building Postgres Foreign Data Wrappers
> speaks a particular API over the network
it's a interesting idea, and one of the things that we were toying with in our pg_net extension (https://github.com/supabase/pg_net). This is a "generic" async network extension, so you can fetch/put/post. It works well for APIs.
I think the generic approach works for some things where the data is less "fixed" - for example, an OpenAI API endpoint.
But for "fixed" data (data warehouses), the wrapper usually needs some custom work for security, protocols, and "push down". I'll be interested to get HN's take on this - they might have some suggestions for us for this framework
-
Show HN: Multiplayer Demo Built with Elixir
> finding the building blocks of modern applications (database, auth, functions, presence, realtime subscriptions), making them easy to use, and then sharing the source code.
Great observation!
> I’ve learned a ton just from cruising around supabase GitHub.
Glad to hear it!
> Can you say which of these new components will be open sourced?
All of these components are open source and licensed under Apache License v2.0.
> There are some other features (e.g. function hooks) that are also closed-source at the moment.
I actually worked on the initial implementation of function hooks. We've actually already open sourced both the client (see: https://github.com/supabase/supabase/tree/88bcef911669595428...) and the pg_net extension it requires (see: https://github.com/supabase/pg_net).
> Is Supabase heading for an “open core” model?
I don't think so. We want to continue to open source our projects under either MIT (client libs) and Apache License v2.0 (server libs).
-
Supabase Edge Functions
> The dream would be to have a great DX experience around using insert/update triggers to call Supabase functions to run background tasks
We have something for this: Function Hooks (soon to be renamed "Async Triggers")[0]. They are still in alpha, but the extension [1] is getting close. It was important to build something which works with PG background workers so that it's non-blocking. We'll make quick progress on this now that we've released Edge Functions.
> sending notifications or updating related rows
Tune in for tomorrow's announcement - it's related.
[0] Function Hooks / Async Triggers: https://supabase.com/blog/2021/07/30/supabase-functions-upda...
[1] https://github.com/supabase/pg_net
What are some alternatives?
walrus - Applying RLS to PostgreSQL WAL
pgsentinel - postgresql extension providing Active session history
wal2json - JSON output plugin for changeset extraction
pg_hexedit - Open PostgreSQL relation files in a hex editor with tags and annotations
emqx - The most scalable open-source MQTT broker for IoT, IIoT, and connected vehicles
Multicorn - Data Access Library
supabase - The open source Firebase alternative.
pgsql-http - HTTP client for PostgreSQL, retrieve a web page from inside the database.
emqtt-bench - Lightweight MQTT benchmark tool written in Erlang
otp - Erlang/OTP