Things which probably will be addressed soon:
- Improved reliability especially for edge cases like proper string escapes in the protocol
- Introduction of a test suite (will probably be limited to some sanity tests to begin with)
- A more specific plan for moving away from legacy Java dependencies
- More detailed & thought-through protocol documentation
- Perhaps some work on applications or on the client layer
Things which probably won’t be addressed soon:
- Scalability to datasets of extreme size, I have some hardware for testing “big data” workloads but I don’t want to make any promises I can’t deliver on at this stage – instead I’ll focus on moving towards “real world” use cases first then worry about massive scalability as the core system stabilises
- Complete independence from the Java platform, this is planned but will take some time and I don’t want to rush it too much
- Support for in-house platforms like running on the SecureLang® RD operating system (see above point)
- Support for every other possible feature such as the latest SQL standards or adding every optimisation present in other databases
A possible strategy I might look into is “developed by mankind, tested by machine” – putting the AIs in charge of coming up with test cases or maybe even round-the-clock AI-based testing to find bugs. This could possibly be a good project to try out those kinds of ideas in.
Leave a Reply