Using environment variables instead of configuration files is pretty standard practice for the modern application development process. It’s just convenient to run application deployment only with docker-compose/helm/whatever YAML-files and not caring about additional configuration files. But sometimes it’s necessary to about application dependencies which are configured via static configuration files. For such cases, I wrote a brief practical guide based on my experience. I’ll try to show how to ease such deployments with Bash templating scripts.
Why Bash? Well, because in many cases you can find Bash inside almost any Linux distro, like Debian/Ubuntu and CentOS/RHEL-like. …
When we are talking about NoSQL databases, we expect high availability and linear scalability to work out of the box. We also assume that the database writes scaling shouldn’t be the problem for the NoSQL database clusters. However, not all that we expect works well, or sometimes just works terrible and takes too much time to carry out routine tasks.
Riak is a distributed NoSQL key-value data store that offers high availability, fault tolerance, operational simplicity, and scalability. Wiki
All of the above is entirely true.
There is plenty of information about the use cases and successful implementation of Riak…
Basho Riak is a key-value database server - distribute, reliable, fault-tolerant. Free alternative to DynamoDB.
After the earlier misfortunes, the product seems alive again and driven by the Open Source community.
Release 2.9.0 looks very promising and moreover, 3.0 should be ready next year with more improvements.
Just check Riak storage backends testing results here.
As my company uses Riak as the default database I decided to refresh the Riak Docker-image, and check the new version by myself.
You also can check it here, or just run the Docker-image:
docker run -d kefirgames/riak:2.9.0p3
That’s all for now, in the next story I would like to tell my experience in operating Riak.
Experienced problem solver.