18
SALESFORCE as PaaS Architecture of Rishabh Karajgi

Salesforce as a PaaS - Architecture of Force.com

Embed Size (px)

Citation preview

Page 1: Salesforce as a PaaS - Architecture of Force.com

SALESFORCE as PaaS

Architecture of

Rishabh Karajgi

Page 2: Salesforce as a PaaS - Architecture of Force.com

What is Salesforce.com?

A Software as a Service(Saas) provider and a major Customer Relationship

Management (CRM) software provider delivered entirely over the internet

(cloud computing).

What is CRM?

It is a model used to manage an organization’s interactions (Phone calls,

emails, meetings, social media etc.)

-with customers and prospects pertaining to Sales, Marketing and Support

Page 3: Salesforce as a PaaS - Architecture of Force.com

Salesforce products

Page 4: Salesforce as a PaaS - Architecture of Force.com

What is Force.com?

A Platform as a Service (PaaS) and multi-tenant cloud development platform

designed to simplify the development and deployment of cloud-based applications

and websites. Developers can create apps and websites through the cloud IDE

(integrated development environment) and deploy them quickly to Force.com’s

multi-tenant servers.

Basically a social and mobile app development platform on the cloud!

Page 5: Salesforce as a PaaS - Architecture of Force.com

Architecture of Force.com

Page 6: Salesforce as a PaaS - Architecture of Force.com
Page 7: Salesforce as a PaaS - Architecture of Force.com
Page 8: Salesforce as a PaaS - Architecture of Force.com

➢ Infrastructure - Representing the servers and the data centers

supporting the platform

➢ Database - Comprises both business data and metadata

➢ Application logic - is mostly workflow logic. It is the application

specific coordination of domain and infrastructure components

according to the requirements of that particular application.

➢ Controller - responsible for controlling the flow of the

application execution. Responsible for returning a response to a

request made to an application

➢ APIs - External programmatic access. To make client side web

service calls through Javascript represented in the view

➢ Views - Components for defining the User Interface of the app.

Page 9: Salesforce as a PaaS - Architecture of Force.com

Services stack

Page 10: Salesforce as a PaaS - Architecture of Force.com

● Architectural stack sits on top of the stack of cross cutting services.

● Any service canintersect with the architectural stack

● While the Architectural stack may be static, the service stack is scalable and dynamic, hence adding additional services becomes easy!

Page 11: Salesforce as a PaaS - Architecture of Force.com

● Combination of

architectural layers,

intersecting services

and security features

along with chatter

which enables social

capability

● Features or

capabilities crosses

architectural layers

● Not only click and go

dev but programming

functionality can be

injected by a developer

Page 12: Salesforce as a PaaS - Architecture of Force.com

Let’s get a bit more technical

Page 13: Salesforce as a PaaS - Architecture of Force.com

Force.com - foundation of Salesforce

Core components :

Page 14: Salesforce as a PaaS - Architecture of Force.com

Multi-Tenancy

Sharing IT resources ( Server, Databases, Application ) cost effectively and securely.

Page 15: Salesforce as a PaaS - Architecture of Force.com

Meta-Data Kernel

● Facilitates multi-tenant applications

● Separates each tenant’s :

○ Runtime Engine

○ Metadata of Tenant

Polyglot Persistence

● Transaction Details.

● Metadata Caching.

● Full-text Multilingual Search

Engine.

Page 16: Salesforce as a PaaS - Architecture of Force.com

Advantages of Force.com

Faster, more active development

Easier to obtain started

Simpler and less expensive to keep

Conceived with the future of the web in mind (Chatter )

Developed for change

Page 17: Salesforce as a PaaS - Architecture of Force.com

Disadvantages of Force.com

THERE IS NO REAL DEBUGGER hence debugging process becomes very slow and you have to manually edit the debug logs by creating debug requests.

Difficult to understand

No proper tooling available such as code refactoring, code analysis etc.

Modelled on JAVA 5, which is considered to be lagging behind other languages and without proper tooling, work becomes cumbersome

Page 18: Salesforce as a PaaS - Architecture of Force.com

https://github.com/karajrish/getting-started-

force.com

Wanna get started with Force.com?