๐Ÿ’ƒ Are all architects created equally? ๐Ÿ•บ

Peep the differences between these key roles, Salesforce and beyond

Good morning, Salesforce Nerds! Anybody out there striving to become an architect?

That coveted title designated for the top tier technologist that knows everything about your landscape, is called upon by all levels in the org & can seemingly solve any problem. ๐Ÿ’ฏ 

I get it. ๐Ÿ‘๏ธ 

We all want to be in a position to help our clients with their problems.

And we all want that payday! ๐Ÿค‘ 

Just be aware that there are different types of architects. If youโ€™re aiming to reach this level youโ€™ll want to understand the differences โ€ฆ

just in case youโ€™re interested

TABLE OF CONTENTS

THE HIGH COUNCIL

Architect Overview

Generally speaking, an architect is a super-senior level engineer thatโ€™s responsible for high-level design choices related to the structure & behavior of an application or multiple applications. ๐Ÿ—๏ธ 

But, not all architects do the same stuff.

As technology evolves faster and faster these roles also evolve and organizations are honing in exactly the type of architect they need. โฉ๏ธ 

Smaller organizations with a smaller technology footprint can get by with a single person wearing many different architecture hats.

Larger organizations with scores or hundreds of applications/services are going to need to hire specialized talent to ensure reliability and scalability.

This is where itโ€™s handy to know about some of the differences in responsibilities for architects โ€ฆ ๐Ÿ‘‡๏ธ 

THE JEDI KNIGHT

Application Architect

An application architect focuses on the design and development of specific software applications. ๐Ÿง‘โ€๐Ÿ’ป 

They work closely with devs, PMโ€™s, and business stakeholders to create app-specific solutions that meet business requirements.

Their focus is on the technical details of the app like:

โœ… UI Design

โœ… Data modeling

โœ… Application design/implementation

In the world of Salesforce, this person will be tasked with coming up with the Object schema, deciding if a solution is no-code, low-code, or pro-code, & making sure the right users can see the right data. โ˜๏ธ 

A lot of times senior level devโ€™s will naturally transition into this role.

There can be some overlap in duties between an app architect and a senior/lead dev. Both will spend time designing, mentoring, and troubleshooting. ๐Ÿ’ฏ 

A big difference is that an app architect really wonโ€™t write too much code.

If you dig the design phase and setting standards for developers then this may be a fruitful path for you to follow. ๐Ÿ‡ 

THE JEDI MASTER

System Architect

A system architect focuses on the design and development of a system that consists of multiple components, such as hardware, software, and networking. ๐Ÿง‘โ€๐Ÿ’ป 

They are responsible for ensuring that all the components of the system work together seamlessly to meet business requirements.

Their focus is on the technical details of the system like:

โœ… Integration of hardware and software

โœ… Architecture of the overall system

โœ… System security

Think of a โ€œsystemโ€ as several separate applications, config files, documents, etc. that all operate together and need work as a whole. ๐Ÿค 

Meaning, this person is responsible for more than just a single application. He/She is in charge of multiple apps! Ensuring they all play nicely and accomplish the needs of the business.

This is something a lead dev or app architect can transition into rather comfortably so long as they understand more than just the app theyโ€™re working on. ๐Ÿง  

Youโ€™ll need to have an understanding of what each app/service within the system does, what itโ€™s dependencies are, and understand the role they play.

If you want to branch out and be responsible for more than just a Salesforce app then this may be a viable option.

THE MASTER OF THE ORDER

Enterprise Architect

An enterprise architect takes a broader perspective, focusing on the organization as a whole rather than specific applications or systems. ๐Ÿง‘โ€๐Ÿ’ผ 

They work closely with business stakeholders to understand business goals and objectives, and they design and develop solutions that align with these goals.

They are responsible for ensuring that all the components of the organization, such as business processes, technology, and people, work together seamlessly to meet business objectives. ๐Ÿ”ฅ 

Imagine being the one person responsible for EVERY application, EVERY database, EVERY service, EVERY config, EVERY piece of technical documentation in your organization.

Thatโ€™s what these folks do. ๐Ÿคฏ 

This not only requires deep knowledge of industry standard technologies, but also a deep knowledge of the entire business domain.

If you want to be THE ONE for an organization then this role might be right up your alley. ๐Ÿซต 

SOUL FOOD

Todayโ€™s Principle

"If you think good architecture is expensive, try bad architecture."

Brian Foote

and now....Salesforce Memes

for real tho โ€ฆ that poor guy probably canโ€™t sleep

if (you.wantToCode()) { you.shouldBeADev(); }

just my impression

What did you think about today's newsletter?

Login or Subscribe to participate in polls.