Recently I’ve spent some time learning about JuliaDB and I’m very excited about the theoretical possibility of having a high-performance web stack written fully in Julia – that is, by replacing the various traditional RDBMS backends with JuliaDB.
I was wondering if anybody experimented with JuliaDB in a high traffic scenario (large volume of small reads and writes). And if there’s any prospect of using it as a viable CRUD (Create Read Update Delete) backend.
I’m thinking for example about SQLite which is 35% faster than writing directly to the filesystem, due to some optimizations in opening and writing files. Where does JuliaDB stand in this regard?
Or, on the data read spectrum – MySQL employs strategies like SQL query result caching. A useful approach, given that web traffic will result in multiple requests against the same data (web apps are basically lists of things).
Using JuliaDB for the web would provide another solution for the two language problem, at database level. The traditional approach is to use some SQL frontend (Postgres or MySQL usually) for powering the web app. And then through an ETL process, move the data into a data warehouse or some other system for analytics. As far as I can tell only Cassandra had some success as a real-time + analytics backend, but it hasn’t seen widespread adoption. But a 100% Julia solution would have additional benefits, from setup and maintenance, to using just one language across the board.