
Assessment of your team’s migration toward cloud native, Kubernetes, and distributed architectures. Let’s look at your maturity model and uncover strategies to increase your delivery.
Workshops that range from hours to days. Together we create a workshop agenda to help your team move forward.
Organizing a conference, meetup, or company event? Choose from my portfolio of topics or let’s create a new topic for your audience.
For 30 years I have been designing useful software to move businesses forward. My career began creating laboratory instrument software and throughout the years, my focus has been moving with industry advances benefitting from Moore’s Law. I was enticed by the advent of object-oriented design and applied it to financial software. As banking moved to the internet, enterprise applications took off and Java exploded onto the scene. Since then, I have inhabited that ecosystem. After a few years, I returned to laboratory software and leveraged Java-based state machines and enterprise services to manage the terabytes of data flowing out of DNA sequencing instruments. As a hands-on architect, I applied the advantages of microservices, containers, and Kubernetes with a laboratory management platform.
Today I enjoy sharing my experience with peers. I provide my perspective on ways to modernize application architectures while adhering to the fundamentals of modularity - high cohesion and low coupling.
‘Learn to Live, Live to Learn’
Let’s face it, learning how to effectively deliver applications to a distributed data center can be daunting to most teams. Perhaps you are feeling some growing pains.
Systems like Kubernetes want to make it boring, however, it’s just the tools and procedures that will improve. The architecture for distributed computing will remain a challenge. Delivering a coordinated set of applications that scale to efficiently leverage large pools of CPUs, memory, and I/O resources can be done, but how do you reduce the mistakes and pitfalls along the way?
Everything in software architecture is a tradeoff. Sometimes adopting delivery of your architecture to cloud native Kubernetes is a great investment, which may also inflict damage to the business. It depends. (Richards/Ford) . I continuously study and listen to my peers like you. I understand the optimism and power of cloud native computing but also appreciate it’s not the best hammer for all of your customer needs.
Let’s investigate your business needs, this architecture, and assess what your team may be missing to smoothen what can be a bumpy ride.