June 11, 2022
Distributed systems evolution challenges
What are the challenges posed by evolving distributed systems architecture? In this short series of articles, we'll understand the critical factors we should be keeping an eye on and how to address them.
I'll be at UGIdotNET Small Talk, online. We'll talk about:
- Introduzione alla messaggistica con RabbitMQ e C#
Know your limits. Infinite scalability doesn't exist
There is this myth that we can design today for tomorrow's unknown requirements. Somehow we believe that we can put in place a robust architecture that will scale forever, no matter what. I'm sorry, that's impossible.
Do we need to debug distributed systems?
We're humans. We are designed to apply previous experience and knowledge to new problems. When faced with distributed systems, we want to debug them. Do we need that? And, can we debug distributed systems?
.NET development on Apple Silicon
I bought a MacStudio, I've been a long-time Windows user, and I'm a .NET developer. What could go wrong? Let's find out how my experience goes in this live-blogging session.
We need insights, not data
Gauges and graphs attract software engineers like honey for bees. We spend hours implementing distributed logging solutions or monitoring systems, and still we have a hard time understanding what's going on.
They'll probably make it anyway: bulk editing Garmin data
Users have needs. They want to get things done when using software. If what they have is not satisfactory, they'll get creative.
Where we're going, we don't need service discovery
Too many times technology is used to solve problems that, to begin with, should not be considered problems. Service discovery, on many occasions, is a solution in search of a problem.