In this section, you will learn about the types of system architectures. You will understand the difference between the following three types of structures:

• Multi-tenant
• Single tenant
• Hybrid systems

You will get to know the challenges faced by landlords when establishing boundaries between one client and another and making updates. Most importantly (remember this is a book about Salesforce), you will find out why the leading CRM uses a multi-tenant architecture.

Multi-tenant structures

In the world of technology, “multi” is quite a common term: multi-tasking when talking about phones, multi-tenant when discussing cloud solutions, and multi-universe in the context of superhero movies. Oh, wait – we will not be focusing on that last part in this book.

When we mention multi-tenant, we are referring to a model where a single software instance serves multiple clients. All these clients use the same...

In this section, you will learn about the concept of an org, find out where it comes from, and discover the types of orgs used by Salesforce. Did you know that there is something called the lifecycle of an org? No? Well, you are about to find out. In the end, I’ll provide you with best practices that will save you from many, many questions from your users and other administrators.

As you probably already know, Salesforce has its own universe – its structure and even its language are tailored to it, and believe me, Salesforce sounds best in English. But, getting to the point, many times when you have spoken, are speaking, or will be speaking to people working within this ecosystem, you will hear phrases such as “in my org” or “but my client’s org is truly a work of art.” You might be wondering what this whole “org” really means.

Well, “org” is short...

In this section of the chapter, you will discover the fascinating world of Salesforce PODs. But what is a POD? The acronym POD stands for Point of Deployment, which may sound a bit enigmatic. To better understand this, let’s start with something you may have heard of – the word “instance.” Salesforce PODs are a different name for Salesforce instances. Instances or PODs are the places where your Salesforce data is located. It is a server location where your Salesforce org is hosted and from where it operates. Does the instance equal the org? No! On the Salesforce instance, there can be multiple Salesforce orgs allocated. Of course, each Salesforce org is separated and secured, so you can’t access the information of orgs that you don’t have access to. However, orgs from different companies are located in the same instance. As you may already know, Salesforce has thousands of customers, so you may now be wondering...

Congratulations! You have just come through the second chapter of this book! I hope you stay motivated and ready for the next chapter. For now, let’s summarize the chapter that you have just finished.

We explored the concept of multi-tenancy, where a single software instance served multiple clients. We examined the challenges faced by Salesforce in maintaining boundaries and making updates. This chapter shed light on why Salesforce employed a multi-tenant architecture. Thanks to comparison to a hotel where guests shared common resources but had isolated, private rooms, you should now remember better what multi-tenant means.

Next, we unraveled the notion of Salesforce orgs, their origins, and the various types in use. We learned about the lifecycle of an org and received practical best practices to address user and administrative concerns effectively.

In the final section of this chapter, we introduced Salesforce PODs, which are essentially server locations for...