Salesforce Application Architecture & Design

Salesforce is a cloud-based platform with a cost-effective multi-tenant architecture, which means that you can develop one common application to service multiple clients. Multi-tenancy allows many users to share the same server and applications, hence, very cost-effective.

It uses a metadata-driven development model, i.e. Salesforce stores, both, the metadata as well as the application data in a shared database. It stores ‘the data’ along with ‘what data does’. So, the developer can focus on building the application as the functionality will be defined as metadata in the database.

The third layer is the API, i.e. Application Programming Interface, which defines interactions between multiple software/application intermediaries. These APIs enable the developers to access apps from any location, using any programming language that supports Web services, like Java, PHP, C#, or .NET.

This Salesforce architecture is seated onto a platform which is utilized by various applications integrated with Sales Cloud, Marketing Cloud, etc. cloud solutions to offer a steady and powerful functionality.

Instance: It is a particular configuration that basically indicates server details for a particular Salesforce organization on which it lives.

App: An app is a collection of solutions that help transform your instance of Salesforce into the perfect business application.

Org: It is a single consumer of the Salesforce application. An org is incredibly adjustable and has very clear security and sharing settings.

Sandbox: Whenever a sandbox is created, Salesforce copies the metadata from your production org to the sandbox org, creating multiple copies of your production org in separate environments.

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 frameworks supporting different instances.