Category: Editorial

  • Kubernetes is Cool, But …

    Kubernetes is cool, and I think it’s really useful in helping us scale and manage multiple systems easily in a fault-tolerant way. Actually, I don’t think Kubernetes per se is important itself; more it seems that the idea of some orchestration engine to manage containers and systems is what really matters. As a side note, there are other orchestrators such as Mesos, OpenShift, and Nomad.

    However, do we need to know Kubernetes to use it for databases? This is a data platform newsletter, and most of us work with databases in some way. I do see more databases moving to the cloud, and a few moving to containers. I was thinking about this when I saw a Simple Talk article on Kubernetes for Complete Beginners. It’s a basic article that looks at what the platform consists of, how it works, and how to set up a mini Kubernetes platform on your system. It’s well written and interesting, but …

    Do we need to know anything about it? Are we running databases in containers, or will we? I think it’s possible that we might run any of our databases in containers. They are like lightweight VMs and there isn’t a reason why we wouldn’t run a database in a container. With external storage, of course, which gives you a cluster-like environment where your storage moves to a new node if the first one fails. That’s a good use case. Deploying consistent environments quickly is a good use case. Using Kubernetes to manage the containers is great, but …

    I don’t think we need to know much about Kubernetes. I don’t think most of us should run it and should outsource any container orchestration to the cloud if we decide to implement database containers. These orchestration engines are quite complex today, and there is a lot of expertise needed to manage them. I don’t know that expertise is worth trying to find, train, and retain for most organizations. We should just outsource the container management to someone else.

    We might need to know how we change the configuration of some resources, but that’s minor knowledge, and really, I suspect that outsourced K8S (shorthand for Kubernetes) will have GUI tools that let you easily pick and choose the CPUs, memory, etc. and then an export of the JSON or YAML or whatever is needed for the config. Most of us likely need the skills to export, save (in a VCS) the files, and then submit them to the cluster.

    A few years ago I went through a bunch of courses and reading material on Kubernetes. I set up some small clusters, I experimented with pods, I even was excited to think about managing containers for various services. What I discovered is that Kubernetes is complex, hard, and something I want someone else to run. Once I set up a cluster in Azure I thought I’d never want to do this on-premises again.

    Much like email. I have run email servers, but …

    I’d like to never run one again, which is how I feel about Kubernetes.

    I think containers have proven more complex and harder to work with than many people thought. I know there are plenty of people using them, but it’s a minority. I see many more organizations still building monoliths, or microservices that run as processes, or client-server apps. Not that many people are excited and using containers. That may change, and if you go to the cloud, containers give you portability that many other solutions don’t, so I’d recommend them there. However, they are still a bit immature, and hard to manage. I think it will be a while before we see lots of databases on containers.

    Even if we do, I’m not sure we need to learn Kubernetes as database people.

    Steve Jones

    Listen to the podcast at Libsyn, Spotify, or iTunes.

  • Republish: Learning from Exercise

    I’m off today, in New York helping my daughter get ready for her college graduation and likely trying to pack up an apartment.

    While I lightly work, you get to re-read Learning from Exercise.

    Hopefully I find some time today to get some.

  • Multiple Display Productivity

    It seems that when I travel to offices these days, it’s standard for most desk setups to have two monitors. I think all the desks at Redgate have a docking station and two monitors for people to use. They also convert to standing desks, which is handy. I have a standing desk that I use regularly, and it’s nice to have that option when I visit an office. At a number of customer sites, I’ve seen similar setups, sometimes with laptop/monitor lifts instead of desks that rise.

    Recently I saw a docking station announced that can support four monitors. I wonder how many of you want, need, or use more than two monitors. While there is often a standard in offices, since many of us work part or full-time at home, perhaps you have a different setup. Maybe you have one or two large monitors instead of 3 or 4 smaller ones. I’d certainly be interested to know if any of you have more than 4 monitors.

    I run three 24″ monitors on my desk. When I go to an office and use a docking station, I can use my laptop as a third, though the resolution gets a little funny. If I were there for any length of time, I might try to reconfigure the laptop to work with the lid closed. Maybe that’s a chore for the next trip. At home, however, I usually have SQL Server Central and writing tools on one monitor, Chrome with lots of tabs as my main workspace for research and general work, and Outlook/Spotify on a third monitor. That lets me focus on one monitor most of the time glancing at another one for reference or copy/paste work.

    I tried four monitors in a 2×2 configuration at one point, but I didn’t like looking up and down. Even now, I often really use two monitors, with side glances at a third one at times. I have been tempted to get 2 larger monitors (27-30″ range), but I’m not sure I would be more productive and not sure it’s worth spending the money for no real benefit I can perceive.

    I’ve seen some neat setups in people’s offices. I see some developers using vertical monitors, though I haven’t found that to be ergonomic for me. I seem to have too many long lines of code or text. I see some people using a laptop with one monitor, and I’ve seen some friends who are creative with videos/live streaming that use more than four monitors.

    I don’t know I have met anyone that has a gaming chair/monitor setup, but I’m sure someone out there has bought or built something like that. If you have, or you think you’ve got a cool setup, let me know.

    Steve Jones

    Listen to the podcast at Libsyn, Spotify, or iTunes.

  • Are IT Certifications Still Relevant?

    I’ve got a few certifications and quite a few more that have expired or aren’t relevant. Does anyone think Windows NT 4.0 or SQL Server 6.5 matter? If you need help in those areas, ask someone else. Unless you have a crazy budget with a willingness to pay a ridiculous hourly rate.

    Kamil Nowinski had a recent video discussing why IT certifications are still relevant. He had ten reasons, and if you want to watch the entire show, you’ll hear his reasons and some rationale why he thinks they matter. It’s a good set of reasons: keeping up with tech, practicing learning, demonstrating a commitment to some technology, finding a community of certified colleagues, and more.

    In some sense, many of these are tightly coupled, but still worth pointing out. I think for smart, driven, ambitious people, certification is something that you can take advantage of to add to the learning you’re likely already doing: sharpening your saw. That’s an analogy to the craftsman that keeps his/her/their tools ready to go. For us in technology, this is usually our mental acuity with software (or perhaps typing).

    For those who aren’t motivated, getting a certification just to add letters after your name devalues the certification for sure. We saw a lot of paper-CNEs (Novell), paper-MCSEs (Microsoft), and paper-CNAs (Cisco) in the 90s. Poor interviewing techniques combined with a glut of certified-but-not capable staffers soured many people on certifications. For good reasons.

    However, when you interview someone with a certification, or if you want to get one, pursuing a certification using Kamil’s list means you are driving your knowledge forward in a focused, organized fashion. The certification isn’t the goal, but a step on the way to becoming a more capable technical professional.

    I got a couple of certifications in the last few years, and I felt they helped me grow and learn. I didn’t always use all the skills directly, but I learned things that have helped me in my job and I didn’t regret the time spent. I might work on another one in 2024, but time is always in short supply, and I’ve got other things to learn.

    Even if I’m not trying to get certified, I continue to learn for many of Kamil’s reasons, just without an examination during my journey.

    Steve Jones

    Listen to the podcast at Libsyn, Spotify, or iTunes.