The role of the architect in the software development organization? What is it really, and on which level? Is there a standard? Can we establish best practices for the organizational placement of the architects? Yes, probably to every point apart from the one about standard, but I do not want to come to any of these conclusions, maybe some other time.
More …More …Building scalable dynamic configuration control and circuit breaker system for microservices deployed to Kubernetes.
More …Of course that having almost no automation, monitoring only 2-3 crucial http calls, having no real way to save yourself quickly if something goes terribly wrong, and releasing every 3 weeks while yelling “Leeroy Jeeenkins” (to name few of my top favorites) has to stop some time.
The software delivery process and technology, popularly known as CICD (Continuous Integration + Continuous Delivery), is a structure supporting your software (development) lifecycle.
More …In this article, I am working through blueprinting the security aspects of cloud-native software solutions and some general security recommendations. The touchiest, often disliked by the engineering teams (more because of the process and way enterprises do it than for any really meaningful reason), counter-intuitive in places, and ever-haunting. Love it or hate it, if you are delivering any kind of software, it is part of your life.
More …