Replies: 2 comments 1 reply
-
This would be very cool to see. Marmot already does similar, but feels very much like a hobby project whereas rqlite is very mature and active. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks @nickchomey -- can you outline how auto-clustering would actually work? What would the operator's experience be? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@otoolep
Its great that rqlite now has protection from SQL injection attacks using parameterised queries.
In relation to management and discovery consider using nats . https://nats.io/about/
Nats server can be embedded into rqlite. Its a very common approach. Nats has leaf nodes so you can have rqlite databases at edge and in cloud and they will all find it other. NATS is self HA and fault tolerant - it does not need anything else.
Its a replacement for consul basically, but provides much more IMHO.
Its quite common to layer other systems with nats, but use nats as a way to discover them and if you want also to interop with them.
When joining a node you do not need to know the other nodes. Nats does all that for you.
Security with NATS is easy using a basic config, and you can have hierarchies of security.
It also has a KV with TLS and so can act as a CDN , KV, but thats not really something you need yet.
Example of embedding NATS Server with an embedded DB: https://github.com/simpleiot/simpleiot/blob/master/natsserver/nats-server.go. simpleiot uses genji ( an embedded golang db ) , not SQLite.
Beta Was this translation helpful? Give feedback.
All reactions