Blue/Green deployments are a method of deploying with zero downtime. This is possible on Pivotal’s CloudFoundry using either the CLI, Maven, or Gradle. Matt Stine wrote earlier on this topic how to do blue/green deployments using the CLI.
Redis provides a neat command to iterate over all keys on a node. It’s the
SCAN command that is used to scan over keys and to return a cursor to resume then the scanning from the cursor position. Complexity comes in when using Redis Cluster. In the previous scenario, all keys are located on one Redis node. With Redis Cluster keys are spread over some nodes.
Redis transactions allow to group multiple commands and to execute them sequentially. The whole transactional state is isolated from other users and becomes visible once a transaction is committed.
A Redis transaction is different from transactions in, let’s say, relational databases. A Redis transaction feels more like a queue/stack of commands because commands are queued and the execution is deferred. This is true for reads and writes. The real surprise is the read commands because any return value is returned only upon transaction execution.
I consider myself very lucky for contributing to the open source space. Open source is one of the main building blocks of our digital world. For me, contributing is sharing, and sharing is giving back. I started contributing in early 2011. Transparency, quality, and purpose are my main reasons for my open source involvements. That is how I got in touch with the Spring Data team.