Distributed processes fall into two categories: open and closed. Open processes are started in one service and will finish in another after passing through any number of services in between. Closed processes are driven by one particular service from start to finish, and while other services may be involved, the originating service is in overall … Continue reading Open vs Closed Distributed Processes
I've been building microservices for several years. I've mostly used DotNet, DotNet Core, and Ruby on Rails to build them, and I've generally deployed them either into AWS EC2, or Azure Service Fabric. I've found most enterprises aren't ready for managing microservices in containers, either in the cloud or their own data centres. Keeping things … Continue reading Microservices with AWS Lambda
When implemented correctly, DevOps reaches beyond the Development teams and becomes a unifying strategy for the entire enterprise.
Does Conway's Law have a dark side?
Let Coding Daddy answer your remote team management woes...
Some of the benefits of remote working.
A dive into the many different ways developers can and should test.
https://www.thoughtworks.com/insights/blog/fitness-function-driven-development?utm_source=linkedin&utm_medium=social&utm_campaign=tech A great post from someone who really understands the problem. Worth a read!
At the time of writing this post, I am 41 years old, I've been in the business of writing software for over 20 years, and I have never ever experienced a release weekend. Until now. It's now nearly 1 pm. I've been here since 7 am. There are a dozen or so different applications which … Continue reading My First Release Weekend
I've heard a lot of people say something like "but we don't need huge scalability" when pushed for reason why their architecture is straight out of the 90's. "We're not big enough for devops" is another regular excuse. But while it's certainly true that many enterprises don't need to worry so much about high loads … Continue reading Scale or Fail
