Breaking down a monolith into small components and modernizing the architecture has a beneficial side effect. The approach I've taken has introduced event publishing for one feature. I can build on that to add new features, again taking a container-first approach.
In NerdDinner there is a single data store, a transactional database stored in SQL Server. That's fine for servicing the website, but it's limited when it comes to user-facing features, such as reporting. There's no user-friendly way to search the data, build dashboards, or enable self-service reporting.
An ideal solution to this would be to add a secondary data store, a reporting database, using a technology that does provide self-service analytics. Without Docker, that would be a major project, needing a redesign or additional infrastructure or both. With Docker...