How far to be production ready?

[MirjamElad]

Hello and thank you for this interesting project. It's all in the title. I really like the paradigms of LinkedQL and FlashQL and I am tempted to use it in a coming project.
As stated in the README, the project is not ready for production yet. Can you give some estimate on when it will be ready for production apps.
If possible, please provide a timeline to let early adopters check when the features they care most about will be ready (and plan accordingly).
Thanks again and good luck with this promising project.

[ox-harris]

Oh yes — that’s exactly the next question, and a positive one for me.
Also, thanks for the encouraging tone. That kind of energy really helps.

One thing I should probably clarify first is: when the README says “not production-ready,” it’s less about a strict checklist and more about a social milestone driven by usage. That’s just the reality with new projects like this. They don’t mature in isolation — they mature by being used, stressed, misused, questioned, and pushed into corners you couldn’t have predicted upfront.

So the biggest difference between “current status” and “production-ready” isn’t really missing features. It’s simply not enough real-world usage yet to guarantee production status. But that changes quickly as discovery improves. (I’ve been circling around a proper launch post for LinkedQL to help kickstart that process. The sooner LinkedQL is widely seen and tried, the sooner it gets battle-tested — and the sooner the README can honestly say: yes, people are running this in production.)

That said, there are a few concrete areas where there’s an actual checklist. Here’s a quick snapshot of what’s actively in flight:

Test coverage
LinkedQL already has 500+ test cases, but more coverage always means stronger guarantees. This is ongoing and benefits directly from real usage and reported edge cases.

Core implementation

• FlashQL (the in-memory runtime)
  Persistent storage isn’t wired in yet, but that work is already happening via a separate reusable project, Keyval:
  https://github.com/webqit/keyval
  I’m hoping to integrate Keyval into LinkedQL within days, which unlocks persistence without bloating the core.
• Federation & sync
  These are currently alpha. They work, but they’re still being validated and should move toward beta as usage increases.

Database adapters

• PostgreSQL is currently the most complete backend.
• MySQL/MariaDB isn’t on parity yet — most notably, live queries are still incomplete there.

Overall, if you’re planning a project, it’s mostly game-on from my side. You should feel free to move forward and circle back as you go — I’m more than happy to walk the journey with you and learn in the process. Early adopters genuinely help accelerate the “production” timeline, because “production” here isn’t a single release switch.