Viewing profile — mikaelronstrom

Dydra using RonDB as backend scales to many billions of items in a graph database with revisioned history.

Not sure how it is today, but in the 90s and early 00s when I worked at Ericsson Mnesia had a number of systems that it was used in. There was interestingly 4 DBMSs developed at Er…

This provides the How-To explanation of challenges one can meet when building highly scalable Key-value stores using a REST server and Python clients.

The reliability of OVH has so far not been a problem. Performance is mostly a factor of the VM instances that you use, AWS has much more instances to choose from, but obviously at …

There are lots of alternatives for database solutions with Kubernetes, in Hopsworks we use RonDB which is highly available and has a MySQL interface but also supports a REST API an…

One obvious benefit of OVH compared to Hetzner is the S3 storage, the Kubernetes framework and a number of other services provided by OVH, don't think Hetzner would provide those s…

Hopsworks has a platform with a high-availability database (RonDB), a highly available distributed file system (HopsFS) and the services are also redundant. Hopsworks even supports…

Intriguingly simple implementation of fibers in Linux and Mac OS X can be used to experiment on the use of fibers in the RonDB database engine.

New VM types using Intel/AMD VMs of the 4th generation in GCP is compared to 2nd generation VMs. Benchmark is Sysbench and database is RonDB (www.rondb.com).

Some playing with numbers for vacations.

RonDB is a KV store with SQL capabilities (the MySQL storage engine NDB is maintained by Oracle as part of MySQL NDB Cluster). Hopsworks is on top of this adding a new REST API (RE…