Main Hall 02: Scaling a Monolith: What to expect if your product idea actually takes off

There are many aspects of software development that we don't often talk about and instead must be experienced. Once the product is viable, the growth stage poses new architectural challenges that we thought we saw coming but are often not properly prepared for.
We will dissect 3 common but different monolithic product architectures and the decisions that were made to take them to market, and discuss the reality that got in the way.
There are good reasons to avoid micro-services in startups, for those applying the more traditional approach I hope you will leave this session knowing what to expect and how to avoid the mistakes I made as you scale your applications.
---
Chris is the father of two teenagers, a Junior Basketball coach at three clubs, an OData Evangelist, and a crazy-mad Collingwood Fan. His preferences are Star Wars, dark mode, spaces and search-driven interfaces.
Chris has been a full-stack .Net developer since 2002, but long before that, he worked with robotics and automation systems to solve seemingly impractical and unnecessary tasks around the house. It took nearly 15 years to find a professional use for these skills in the realm of Industrial IoT, interfacing with PLCs, microcontrollers, and SoCs like Raspberry Pi, mostly from the comfort of C#. He brings his IoT experience in designing and managing distributed APIs and Micro-Service style solutions to each new project and designs the core APIs with extensibility, scalability and long-term maintenance as primary concerns.