How to Think Like an Architect - Mark Richards

Thinking like a software architect is seeing things with a “software architect’s eye”, similar to how meteorologists, artists, and mariners see clouds with a different point of view and with a different meaning. Architectural thinking isn’t just for architects - senior developers and tech leads can apply architectural thinking to their daily activities as well to better understand the architectural implications of decisions they make. In this session, you’ll learn what architectural thinking is and how to apply this kind of thinking to your daily work and activities, regardless of your role or title. In this keynote, you’ll learn how to think like an architect, increase your technical breadth, and how to analyze trade-offs.

[balajichesetti]

Best video ever watched on architectural thinking...👏

[ramazan-gr]

One of the best speeches I have listened. Delivers what is promised.
Edit: "Layered" means "Monolith" here at 18:55. Because Layered is logical design of software, ms can be coded using Layered design

[Muktakeshable]

It's call building psychology of Archict.👏👏👏👏👏

[AdityaChaudhari]

Excellant Mark. You have put the complex piece so simple much appreciate

[Muktakeshable]

at frame 14.51 why the Airtel logo is shown as Cloud in the left upper corner? Whoever watching this video are you guys all enterprise architect or will to become one?

[artemlyubchuk]

His excitement and way of speaking doesn't sound like all architects are grumpy ). So focus on trade-offs first, thanks!

[danielolajumoke]

I'll advise that anyone watching this video get those books.

[Rcls]

You can definitely version services. On a web service you can send in the version in a header, in the payload or include it in the path. The service determines how to use that information. And what do you mean you can't scale a service? It's an individual service! Of course you can scale it!

[kayakMike]

Well... You can skip security if you can garauntee no nefarious people are going to hack into it.
You can skip scalibility if its a one-off design. You can skip availiability if its not an online application.... There are different things to consider...

[Dave]

Please stop switch in the video. All we want to see are the slides. Keep the 3/4 view with the speaker on one side. We are not here to be entertained by the view switching.

[kayakMike]

"Lets start with a monolith and see if that works". Uh.... No thankyou. I don't even thing kernels should be monolithic.