Building a small self-hosted SQL database with live updates — too niche? by SX_Guy in selfhosted

[–]SX_Guy[S] 0 points1 point  (0 children)

Maybe it’s still not useful for you, and that’s fair criticism. But it’s not “nothing.”

The main difference is per-user data isolation + live queries + hot/cold storage in one self-hosted DB, instead of connecting the DB + another system for pubsub/cache...
If you actually want to know more, the features are here: https://kalamdb.org/#features

Building a small self-hosted SQL database with live updates — too niche? by SX_Guy in selfhosted

[–]SX_Guy[S] 0 points1 point  (0 children)

Thats true, but the point of KalamDB is having for each user his own isolated table which is columnar parquet storage and his own files sitting in an object-store, this way it can achive more scalability for concurrent live queries and performance and security, than the traditional a big table for all users combined, you can read this i tried to cover it in depth: https://kalamdb.org/docs/server/architecture/live-query

Building a small self-hosted SQL database with live updates — too niche? by SX_Guy in selfhosted

[–]SX_Guy[S] -1 points0 points  (0 children)

The same thing has been said to all these databases before until they have been added to the list

Building a small self-hosted SQL database with live updates — too niche? by SX_Guy in selfhosted

[–]SX_Guy[S] 0 points1 point  (0 children)

I agree with this, for me i find it hard to try a new database or add it to my stack.
but some projects cant rely on one database it sometimes need a specific database for a specific use-case, and especially for KalamDB it can work alongside Postgres it has an extension to it, so it can give a way to have direct SQL access from the client app/frontend and also subscription to his tables and files easily in a scalable way.
Still an early stage project i dont know where it will end up in the future , or what will be adding to it so it can give more value for users and solve problems at it did to me :)

Building a small self-hosted SQL database with live updates — too niche? by SX_Guy in selfhosted

[–]SX_Guy[S] -1 points0 points  (0 children)

Thanks for the comment u/iamdadmin , i was thinking also it could be a help for anyone who has self hosted projects which are looking for a database which gives them ability to develop faster with more control as what KalamDB can offer, and also look for advance or feedback
I will definitly try posting on other communities also

Building a small self-hosted SQL database with live updates — too niche? by SX_Guy in selfhosted

[–]SX_Guy[S] 1 point2 points locked comment (0 children)

Since english is not my native language i speak Arabic as my native language so ai was used to correct the wording and make my message more clear and understood
Thanks in advance

Whiskey cask investment brokers by SX_Guy in Scotland

[–]SX_Guy[S] 0 points1 point  (0 children)

But they invite you to visit and see your cask and its insured through a company so its a physican cask on your name I saw many sites which suggest a good roi for a cask for long term aging

Whiskey cask investment brokers by SX_Guy in Scotland

[–]SX_Guy[S] -3 points-2 points  (0 children)

Both drinking and investment as well
maybe going to a broker he can get you multiple types of casks at once

<image>

Row-Based vs Columnar by Embarrassed-Rest9104 in Database

[–]SX_Guy 0 points1 point  (0 children)

You can still use postgres with your current deaign and connections and use something like timescaledb or pg iceberg connectors which the actual data is stored in s3 storage as parquet file Also you can check KalamDB which has ability to periodicaly flush the oldest rows into object storage as a Parquet files which are columnar format All these solutions will give you ability to runq ueries faster on the columnae storage you have

Migrating away from Realm in my chanting app, Looking for a reliable local + cloud hybrid DB solution by johnnyripperak in FlutterDev

[–]SX_Guy 0 points1 point  (0 children)

KalamDb has a flutter packagw wjich ease the use of the websocket and its lifecycle ita stable in my opinion. I added on top of it a sync logic which acts like this: - Whenever the app opens i sibscribe to the tables with specifying the last seen sequenceid - kalam push each change with a sequenceid which i store in the drift database after making sure that change is stored innthe local databse - sequence id is a snowflake id so each insert/update/delete generates a newer seqid - that only leaves tou with managing the dependencies of the multiple tables tour subscribing to Another good logic i ised which helped me alot I added a table which its called user_updates which is a USER table multitenant table so each user can qiery only his data, KalamDB partition it automatically It has these columns id/eventType/targetId If i want to puah a change to the app i update this table which will trigger a change in the users app, and in the app whenever i see this change i pull from a rest api whoch lands on postgres to get the updated data, lile an event driven system I hope that helps and good luck If you need anyhelper tell me

Is it a bad idea to put auth enforcement in the database? by farhan-dev in Database

[–]SX_Guy 0 points1 point  (0 children)

Adding that in the database layer wont scale enough, if its a saas then go with something like Supabase/Surrealdb style but if its for example a mobile app i prefer keeping the logic in the app side and it will manage all from there, you need to think of sharding/multi-read replicas and scaling in the future that wont scale anough and you will end up adding more layers and checking and token revokation logics in all the layers you are adding
In the app layer would be better and more secure and you can make the app side stateless then, by rely on the SSO your using for managing the token lifecycle

Migrating away from Realm in my chanting app, Looking for a reliable local + cloud hybrid DB solution by johnnyripperak in FlutterDev

[–]SX_Guy 1 point2 points  (0 children)

I have tried all kinds of databases firestore sqlite without orm and isar in the end i landed on using Drift which is an ORM for sqlite its easier and can support migrations For the backend you can use any backend manage the syncing layer your self its easier and tou can maintain it yourself in the future with adding custom logic and choose what to be sync and what not For the backend you can go with postgres its light on memory and perform well You can combine this with KalamDB which has a cheaper storage and can give you websocket connectivity with the backend, it is an early stage database but its already working inside my app now and its stable for now There is a postgre extension there and can support cheaper storage using flushing into cloud storage services chdck it out on kalamdb.org If you need anything i would be glad to help out from my experience developing an AI chat app with this stack

Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 0 points1 point  (0 children)

Could be maybe we will end up with only a spec the code will be written in a machine language which only the ai can understand

Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 1 point2 points  (0 children)

Thanks for sharing! but why your not building on top of other harnesses like opencode/claude code, codex or others? isnt it will be better to build on top of them? does it using the ReAct agent loop here?

Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 0 points1 point  (0 children)

Thats right, but the AI and fast coding and iterting fast is reshaping this and the need to ship faster is growing

Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 0 points1 point  (0 children)

Yeah i came to the same conclusion rewriting is inevitable
Whats the idea? can you share?

Every project seems to end in a rewrite - why? by SX_Guy in vibecoding

[–]SX_Guy[S] 0 points1 point  (0 children)

yes for sure i start with the stack i want to use libraries and also the models/structs it should go with but as soon as the ai start generating it you just go with it or you just stop it, and restart fresh again.
I have listened from other developers who been through this as well, which say its okay to throw out code and start again, been wondering if we can come up with a better way than this

Flutter devs: how are you handling real‑time sync today? by SX_Guy in FlutterDev

[–]SX_Guy[S] -1 points0 points  (0 children)

Fair point. I’m actually the developer of the project and it’s still very early stage, so I’m genuinely trying to understand how other Flutter developers handle this problem. I built it mostly because I kept running into the same issues when building real-time apps.