Architecture of Salesforce
By now, you would have understood that you can use Salesforce to deliver a highly customizable application to your customers.
In order to understand how Salesforce works, it is important to understand the architecture of Salesforce.
Think about the Salesforce architecture as a series of layers sitting on top of each other.
Watch this Salesforce video:
Interested in learning Salesforce? Enroll in our Salesforce Training now!
Let’s focus on the following things for now:
- Salesforce is a cloud company, and it offers trusted and multi-tenant cloud.
- The Salesforce platform is the foundation of Salesforces’ services. It is powered by metadata and is made up of several different parts, like data services, artificial intelligence, and robust APIs for development.
- All apps sit on top of the platform. Their pre-built offerings like Sales Cloud and Marketing Cloud, along with apps you build using the platform, have consistent, powerful functionality.
- Everything is integrated. The Salesforces’ platform technologies like Einstein predictive intelligence and lightning framework are built according to the users’ convenience.
Here are the topics which we are going to discuss in this section:
Core Architecture of Salesforce
The core architecture of Salesforce has been put into the following layers for better understanding.
Before discussing the Salesforce architecture, let’s first go through several important terminologies of Salesforce architecture:
- App: All metadata elements like objects, Visualforce pages, classes, etc. are independent of the app. An app simply helps you cluster things visually. However, internally metadata has nothing to do with the app, but you’ll be able to have a similar tab, VF Page, etc. in multiple apps.
- Instance: An instance of Salesforce is the particular configuration that you see when you log into Salesforce. Salesforce instance is basically indicating server details for particular Salesforce organization on which it lives. It is possible for many Salesforce instances living on one server. The instance was created based on the location of the user. It will be changed based on the region from where you log in.
- Superpod: Superpod is the arrangement of frameworks and stack balancers, including outbound intermediary servers, system and capacity foundations, mail servers, SAN texture, and various other framework supporting different instances.
- Org (Organization): It is a single consumer of the Salesforce application. Every trial that begins on www.salesforce.com or developer.force.com produces another org. An org is incredibly adjustable and has a very clear security and sharing setting. The UI look and feel, work processes, triggers, custom articles, custom fields on standard salesforce.com CRM questions, and also the custom APIs are very adjustable.
- Sandbox: Whenever a Sandbox is created, Salesforce copies the metadata from your production org to the sandbox org. By doing so, you can create multiple copies of your production org in separate environments.
Interested in learning Salesforce? Check out the Salesforce Training in Bangalore!
There are four kinds of sandboxes:
- Developer Sandbox
- Developer Pro
- Partial Copy
- Full Sandbox
Watch this tutorial on Salesforce architecture to understand the basics
Different Layers of Salesforce Architecture
- All data is stored in a single database schema for all their customers.
- It is economical because resources and maintenance are shared.
- A single instance of a software server with multiple tenants.
- The provider has to update only one application, and the changes will get updated for all clients.
In a multi-tenant architecture, there is one common application serviced to multiple clients. So, in this case, the developer can create an application, upload it onto the cloud, and share it with multiple clients. The major advantage of the multi-tenant architecture is that it becomes cost-effective as the application is shared by multiple clients. The application and maintenance cost of a particular application can be shared at once. This makes the application very economical per client. Also, if the developer/provider wants to make any updates to the provided software, he can directly update it in just one place. All clients using that application will get the updated version.
Comparing this with the single-tenant architecture, each client will be owning one particular software/application. So in the single-tenant architecture, the development and maintenance cost has to be completely owned by one particular client. Also, if the developer wants to update the application, he has to manually update that application for each client. Only one application will be able to satisfy one client.
Prepare yourself for the industry by going through this Top Salesforce Interview Questions and Answers!
- Salesforce platform uses a meta-driven development model.
- Developers need to concentrate only on building the application.
- Functionalities of an app are defined as metadata in a database.
- This increases developers’ productivity.
The issues of security get sorted with this particular architecture, since all the data is stored on different levels, i.e., data above data. All the data is stored in shared databases; the metadata points to one particular clients’ data in a shared database.
Consider, three clients, A, B, and C, sharing a single database. So, each client will have access to their own metadata from the shared data. So, each client will have separate metadata. This ensures that you don’t get into someone else’s metadata. This also increases the security of the shared database. Developers just need to create the application and deliver the application to the respective clients’ metadata.
A powerful source of APIs is provided by Salesforce. These APIs help in the development and customization of Salesforce Mobile Application. These APIs enable diverse bits of programming to interface with each other and trade data. These APIs are comparable. Without knowing much details, you can connect your apps with other apps.
Salesforce design isn’t just a random series of hit and trial experiments. Rather, each and every feature of its design has been planned and placed at the precisely needed places. Once you start working on this architecture, you’ll understand almost all of its functionalities.
In this session of the Salesforce tutorial, we learned about the robust salesforce architecture. In the next session of this tutorial, we’ll see how we can create a Salesforce developer account.
Come to Intellipaat’s Salesforce Community if you have more queries on Salesforce!