Random reminder that I have a YouTube channel where I post videos about software architecture and design. Usually in the 10 min range trying be concise as possible. If you enjoy please share. Have suggestions? Please let me know.
This weekend I'm going to work on my next video about how Microservices (or any size service) have absolutely nothing to do with Container/Docker/K8s. I can't deal with reading these articles anymore. Next to nobody mentions it's about logical separation and not physical.
I'm creating a series of videos that will take an existing sample app and move a portion of it to be event sourced. Along the way, I'll be removing a bunch of layers and "services" which I think will give a better gist of Vertical Slices and how that plays with CQRS.
Blogged: When building Software as a Service (SaaS) youāll often need to use a Multi-tenant Architecture. There are many different ways that you can segregate and share compute and data storage in a multi-tenant architecture.
I really don't understand having the defined role of "Software Architect". The architecture will evolve by the team. Someone on the team can be leading that charge. Everyone on the team can have varying degrees of input but ultimately it should involve everyone.
I love code. I love writing code. I love creating software. The challenging part in the software I write isn't writing the actual code. It's understanding the domain, really understanding. Then translating that to code, evolving the design and architecture over time.
I'm really curious about the software industry's love for making language/framework/tools the top priority of knowledge and experience. Why isn't the type/domain of software you develop the most important thing? Ex, hiring C# developer vs. hiring a developer for insurance.
Recently crossed the 50k subscribers mark. It's been a long road over the past few years. I try not to concern myself with the subscriber count, but it's hard not to notice. These videos aren't for everyone, but I appreciate everyone watching, liking, and commenting.
Friendly reminder that I have a YouTube channel that has over 100 videos about Software Architecture and Design. New content every week. If you enjoy my channel, please share!
Blogged: Everyone creating HTTP APIs seems to implement error responses differently. Wouldn't it be great if HTTP API Errors had a standard? Well there is! It's called Problem Details.
I finally read the Amazon AWS Lambda thing that was all the rage last week. Most of the takes I read were head-scratchers or just clickbait, I guess... It didn't help that the post stated it was moving from Microservices to a Monolith. From the post, they kept the logical