In this talk, Alain is going to introduce a simple method to make our presentation components not so dumb anymore. Using content projection, we will see how we can build components that can be used in multiple different contexts, offer a lot of customization options, and have an easy to understand API.

Architecting an application can be challenging. What do you do to keep your application flexible to ever-constant requirement changes? How do you handle landscape changes (cloud, on-premises, databases)? How do you avoid over-engineering the application? How do I make sure my application plays well with other applications?

In this session, we’ll take a look at some well-understood and practiced Software Architecture patterns. We’ll cover these patterns at a high level to understand how to use these patterns in different scenarios.

You’ll walk away with some knowledge, tips, and tricks that you’ll be able to use for new and existing applications.

Not all aspects of software architecture are glamorous, some are downright stressful and often lead to anxiety and stress. One of such roles is the selection of technology stacks and the decision making that goes into which solution should be utilized.

Even within the Microsoft space in 2022 we have so many different models of development that it is becoming increasily more difficult to make seemingly simple decisions such as which technology stack should be used and why. We are presented with so many options, how do we best analyze and select a platform? This session strives to dive into the decision making process, not necessarily any technology specific solutions. Looking at elements such as:

• Developer experience
• Training ability
• Future growth/patching tolerance
• Performance & Scale requirements
• Environmental requirements
• Time to delivery
• Deployment/update scenarios

All of these, and more, should be considered with each and every technology selection. it is very easy to back yourself into a corner without a proper approach to th decision making process.

At the end of this session attendees will have a framework of understanding with regards to technology stack evaluation and how best to pick a future solution while considering all of the risks/rewards.

A well-architected system is foundational for organizations needing to meet their business goals. How development teams approach building and maintaining these systems makes all the difference.

Software architecture and systems engineering are complex topics. No StackOverflow post will tell you everything you need to know.

This talk will break down some of the key concepts you must understand to become a successful software architect. We will talk about decomposing systems into modules, orchestration, logical vs. physical architecture, and managing all the critical - ilities (scalability, extensibility, stability, and so on). Looking at some existing industry ideas like volatility-based or DDD (domain-driven design) will help clarify these abstract ideas.

Concepts covered here will benefit both existing and aspiring architects.