Collaborative Software Architecture

As a dedicated advocate of collaborative, incremental software architecture design, I value the importance of having a strategic design starting point by an Architect and then sharing that strategic design with the development team. 

Both to scrutinize the ideas and requirements and to start redesigning as a collaborative effort using something non-permanent like a whiteboard. All to encourage incremental design without losing the strategic technical requirements.

I believe the mistake we Architects, Senior Devs, and Tech Leads make when sharing these starting-point designs is that we make them look permanent by using heavy-handed digital tools to produce them (cough Visio)! 

Here is a solution I've been working on, a dedicated sketchbook for your architecture design and practice that doesn't make your designs look formal, permanent, or even rushed. A perfect way of transferring your design to a whiteboard to share with a team:

https://lnkd.in/dMS_JYFe

A sketchbook specifically designed to help with drawing microservices architecture designs. A key throughout the sketchbook provides examples of commonly used microservices architecture components, and the dotted pages are specifically designed to help with sketching these components.

Please note: This is a sketchbook for drawing designs and does not teach you microservices architecture theory. For sketching, you can use pencils, pens, and markers. However, if using markers, be careful as these might bleed through the next page.

#software #architecture #microservices #sketchbook