Christoph Engelbert is a developer by heart, with strong bonds to the open source world. As a seasoned speaker on international conferences, he loves to share his experience and ideas, especially in the areas of scalable system architectures and back-end technologies, as well as all things programming languages.
Running databases in containers has been the biggest anti-pattern of the last decade. The world, however, moves on and stateful container workloads become more common, and so do databases in Kubernetes. People love the additional convenience when it comes to deployment, scalability, and operation.
With PostgreSQL on its way to become the world’s most beloved database, there certainly are quite some things to keep in mind when running it on k8s. Let us evaluate the important Dos and especially the Don’ts.
For more than two decades, iSCSI was the go-to protocol standard for remote block storage over commodity network hardware, utilizing normal Ethernet networks, hence mitigating specialist hardware, saving cost, and providing a much lower entry barrier than Fibre Channel or Infiniband.
However, the underlying storage technologies made leaps during that time, and today iSCSI is often a bottleneck for high-performance storage deployments, backed by SSDs or NVMe. Therefore, the NVMe Express group defined the NVMe over Fabrics protocol family, with NVMe over TCP being at the forefront to replace iSCSI, while offering lower latency, higher throughput, and less protocol overhead.
Let’s dive into NVMe, NVMe over TCP, and how it’s superior to iSCSI, as well as the support landscape.
Searching for speaker images...