Rip City Flow - Where to begin?

By Chris Maki | August 4, 2018

How do you transform your organization? When investigating microservice architectures, organizational transformation and continuous delivery you will likely come across Conways Law:

organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.[1]

More simply put:

Your software is a reflection of your organizational structure

This is important because in order to change your software, you will need to change your organizational structure. Have you ever noticed that when you try to adopt a new process, procedure or architecture design the end result isn’t that different than what you started with? This is most likely because you didn’t also change your organization.

Depending on the size of your organization, this can be a simple or extremely complex process. Smaller, newer organizations tend to have greater success at adopting new technologies, in part because they have a flexible organizational structure. Older, more established companies tend to adapt much slower because initial attempts at adopting the “new way” do not include org change. The inverse is also true, if your have an organizational change but do not change how your software is structured, you most likely won’t see any software/system improvements.

This is what makes moving from a monolith to a microservice so complex, you need to approach the problem from both ends. You need to transform your software teams and your business teams.

At Rip City Software have more than 20 years of combined experience helping organizations make these transformations. Let us help you navigate your way from a Monolithic to Micorservice architecture while maintaining your current business objectives and targets.

Updates

  1. 2/05/19 - move from WordPress to Hugo

  2. 2/15/19 - updated all formatting with move to full hugo site

comments powered by Disqus