From the course: Software Architecture: Patterns for Developers
Best practices and blueprints
From the course: Software Architecture: Patterns for Developers
Best practices and blueprints
- [Peter] Software comes in many flavors. And if all goes well, the application does what the user expects it to do. But modern software can be complex, which can lead to complex code. And complex code is difficult to work with. What if we could make software more easy to work with? What if we could translate complex architectural problems to recognizable patterns? Just like an automotive engineer will recognize many of the parts that make a car, we software engineers can build software using tried and tested patterns. Knowing and applying the patterns allows us to reduce the complexity and work more efficiently. We'll be covering different software architecture patterns ranging from user interface patterns like MVC to patterns that involve multiple applications like microservices. Along the way, we'll talk about some pros and cons of using these different patterns. That'll give you some insights into making the best decisions for you and your organization. I'm Peter Morlion and I've been working in software engineering since 2007. I've led a range of different projects and helped design and implement architectural patterns for lots of organizations. Knowing different patterns has helped me create applications faster, more reliably, and just better. So join me in this LinkedIn Learning course as I go through the various software architecture patterns that will help you transition from software developer to software architect.
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.