Welcome to the Sioux Falls Developer's Group!

In the previous article, we looked at how to build a custom Layer that we can use to log events. But we missed a huge part of the tracing ecosystem: spans. To record the flow of execution through a program, tracing introduces the concept of spans. Unlike a log line that represents a moment in time, a span represents a period of time with a beginning and an end.

When it comes to logging and analysis in Rust, I get the gut feeling that tracing is the way of the future. The rust compiler uses tracing. Tokio is doing cool things with it. Even the GraphQL library we use has integrations with tracing. Because that seems like where the ecosystem is heading, I wanted to replace the log-based logger we use at Zenlist with one built on tracing. But for whatever reason, tracing’s JSON logger just never really felt quite right.

I recently earned my Azure Fundaments Microsoft certification. As a software developer who is just getting started with cloud computing, I found that all the concepts that the certification covered were very helpful in getting my feet wet with Azure and the cloud in general. If you’re new to Azure and want to use it for your IT workloads, then I highly recommend considering getting the Azure Fundamentals Microsoft Certification.

Improving Organizations - Moving to a Consistent Flow of work I’m working with an organization that has many clients with on-premise installations. This has been difficult to deal with as the various clients have different upgrade thinking. There are many different versions out there. The current upgrade process takes a lot of time and has a lot of risk. That pushes the organization to have less frequent, big bang deployments and “drops”.