Data Center Users: Majors vs Miners

Majors versus minors are enterprise data centers versus blockchain, bitcoin and distributed ledger data centers. We dive into the differences in processing and environmental requirements for those two different use cases.

While the idea of blockchain and distributed ledgers generate very different computational profiles, what we’re building keeps coming back to the design of a data center is design of a data center. The exception is proof of work like Bitcoin. In those cases, it’s really just how many CPUs you can run.

For this episode, we focus on proof of stake data center infrastructure. This podcast is helpful to understand the difference between proof of work and proof of state. There’s clear consensus on the call that that proof of work is not environmentally sustainable. So proof of stake is much more interesting.

Transcript: otter.ai/u/uuPJSF_nWeDLF64lZlsGLOY8JWw
Image: www.pexels.com/photo/man-holding-shovel-3285094/

Expanding GitOps Beyond K8s

GitOps is a really important way of collaborating and communicating about infrastructure.

But can GitOps escape from Kubernetes? While we did talk about Kubernetes too, we mainly talked about what it takes to implement GitOps outside of Kubernetes. We considered building a GitOps architecture and then having people understand and use it. We also cover the fundamental parts of GitOps like having a reconciler and a bunch of tools that drive clusters.

Transcript: otter.ai/u/oq4D06Sd_rtUvXBVXC0Wx3KA2sQ
Image: www.pexels.com/photo/people-with…popcorns-7234318/

Resourcing the Metaverse (+ Feedback aaS)

What resources does the Metaverse require? In this episode, we think of the metaverse as a distributed environment and ask if it could be owned by the people who are hosting the environments instead of centralized.

One of the complicating factors is figuring out if the Metaverse is AR, VR, augmented or virtual systems. Consensus was that the augmented reality (AR) version of the Metaverse is probably the most valuable and the most accessible for building these systems out. But we kept mixing physical assets and intellectual property assets: the virtual furniture, environments, decorations and things that you would actually put in the virtual environment. While the infrastructure and software that will run the Metaverse is more necessary, the real estate is also interesting.

Stay tuned for a bonus at 48 minutes where we had a good discussion about testing products and giving product feedback as a service

Transcript: otter.ai/u/OhEqaGrH4S2Y9ywpTKVgrhhAn0Y
Image: www.pexels.com/photo/room-chair-lot-356065/

Is Complexity Real?

Today’s episode is about measuring complexity. Complexity is a topic that we cover a lot. And in this case, we really went past the idea that we could measure complexity, and into looking at the causes and costs of complexity.

We had a remarkable conversation about what it means to say something’s too complex? What are the consequences of complexity? And what should we do about them? Ultimately, it’s about how how we measure the cost or the risk of complexity?

In the end, we are reframing complexity in business terms and human terms. That is the important approach to looking at complexity.

Transcript: otter.ai/u/qOBFHwMfUd0ELCnnD63AXcTLe9I
Photo: www.pexels.com/photo/colorful-th…on-floor-5723513/

Is Web3 Legit?

Today’s episode is about Web3. By now hopefully you’ve heard of Web3, but… what is Web3 really!?!

That’s exactly what this conversation is about! We really talked about how Web3 is more than tech bros marketing Bitcoin. There actually are real legitimate business interests around Web3. Uses like breaking transaction log jams when a small number of providers are actually controlling and running the internet. Or looking at ways to decentralize infrastructure and remove bottlenecks within transactions flows.

You will be surprised at how much of the evolution of the Internet is captured in what Web3 could be.

Transcript: otter.ai/u/j9LW8BlgtDoCMw5JyweGiyGIS5o
Photo: www.pexels.com/photo/three-gray-…ntroller-2106215/

Scaling Continuous Delivery

We went beyond what the Continuous Delivery Foundation is doing to talk about how to scale Continuous Delivery. Especially around the continuous reconciler pattern.

So what does CD take beyond committing something in git? To make scalable continuous delivery systems and cross team continuous delivery systems means building things beyond GitOps that really scale and work for enterprise teams. The use cases are not just cloud native technologies, but really useful for established enterprise tech too.

Transcript: otter.ai/u/JkTWNWtaaUEOHrd-bdHIP3rsmO8
Photo: www.pexels.com/photo/man-wearing…rmal-bag-4393667/

The Real Augmentation Leading AR/VR

This discussion is about the infrastructure behind augmented reality. We really dive into how augmented reality will take place in our environment. And the spoiler is it AR is already here!

We are actually building augmented reality systems everywhere and they’re showing up in our daily lives. The group believes very strongly that the automotive space is already leading AR for a whole bunch of reasons, including ease, progress so far, and profit motives.

We also talked about why it’s so hard to build the networks of infrastructure that need to be consumed or make augmented reality so much easier.

Transcript: otter.ai/u/1k7WpYtdpzpNVlf6FDzU_u7nIy8
Image: www.pexels.com/photo/woman-playi…ity-game-6498965/

Migrating Long Term Applications

How should we think about migrating legacy workloads to new infrastructure and modernize them?

The group addresses this question methodically incuding how databases get linked, how they get used, how they get migrated, how important it is to maintain languages and what it would take to migrate in language. In the end, we look back on that conversation apply lessons learned to what we are building today,

This is absolutely essential because new designs will become tomorrow’s legacy! We’ll be struggling to migrate those in 10 or 15 years too. So everything we can learn helps prevent that cycle.

Transcript: otter.ai/u/sHB8507KjZlZPBMToBUCEKjPVQY
Photo: www.pexels.com/photo/man-and-wom…tainside-8968077/

Can We Measure Complexity?

We seem to be very worried about complexity in technology, but how bad is it really? Do we have a way of measuring complexity? Figuring out how to actually quantify it could help eliminate and manage it.

We started by discussing mathematical concepts to capture the systemic nature of complexity. That turns out to be really hard, so we got into some really interesting thoughts about what it takes to manage and understand complexity. Is it even possible to measure complexity? The group is mixed.

Transcript: otter.ai/u/qWkkgyKCXX89jcirBdni9ExkOq8
Photo: www.pexels.com/photo/random-obje…-balance-9304725/

Can Machines Update Themselves?

We know that humans have trouble keeping systems updated, but… how can we address the challenge of knowing which updates are required and, critically, if the updates with break other systems? Even knowing if they worked is a really thorny problem!

In this episode, we focus on actions about what’s going on and why this problem has persisted in industry for so long. Starting from the news of the day about CentOS 8 mirrors being taken down. That’s exactly the type of challenge we are facing when we think about where updates and repos are coming from.

Transcript: otter.ai/u/rRMIT6kkTTtyWrzdBnuq63nvKuE
Photo: www.pexels.com/photo/a-man-using…quipment-5996696/