Fluent Web Development

Chapter 2. Architecture

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 3rd chapter of the final book. Please note that the GitHub repo will be made active later on.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

Now that we know how to get our application started, it’s a good time to think about how we want to structure, organize, and model our application. Welcome to the wonderful—and often misunderstood—world of architecture.

People tend to have very mixed opinions when it comes to architecture in software products. For some, it’s a necessity, and they swear by it. Others start swearing the moment somebody mentions architecture. I’ve seen companies that proudly removed all software architects from their organizations because “it works better without them”, and companies that tried to do the same, accumulating so much technical debt in such a short time that they’ve put themselves into a corner.

Some developers see a prestigious role and want to do everything in their power to be an architect, while others see a nuisance who spends more time in PowerPoint than in the actual product.

As always, opinions stem from experience, and the truth is somewhere in between. In this chapter, ...