How does a kitchen junk drawer become a junk drawer? One item at a time.
We can build the same kind of mess in our applications. Every new feature just gets added on without considering the overall architecture.
But we can stop this approach, and move to a layered, or decoupled architecture where each layer gets a specific responsibility and defined messaging (API) to that layer.
In this course, you will learn to analyze an existing monolithic architecture for weakness. Then you will use new business opportunities as a reason to refactor to a decoupled architecture. You will use model-view-controller as a guideline for separating the layers of your architecture.
And you'll also see varying approaches for data storage and inter-layer communication.
Ready to turn your messy application into a well-organized one? Join me in chapter one!
Meet Your Teacher: Glen Wolfram
Glen has worked in the trenches of software development for 30 years. He currently lives in the beautiful Pacific northwest of the United States.
He has applied object-oriented and agile techniques developing applications spanning a vast range, including embedded applications and video games, plus vehicle simulators and medical data systems. Additionally, he brings plenty of examples and understandable analogies to the learning experience. Take it from one student's comment over the years: "I never nodded off in his classroom."
Learning outcomes
Contributors
Instructor
Created by
