Salesforce as a PaaS - Architecture of Force.com
Download as PPTX, PDF4 likes2,094 views
Force.com is a Platform as a Service (PaaS) and multi-tenant cloud development platform designed by Salesforce to simplify building and deploying cloud-based apps and websites. It utilizes a multi-tenant architecture with separate runtime engines and metadata for each tenant to securely share IT resources. Developers use the cloud IDE to create apps through declarative programming and workflow logic across architectural layers that are intersected by scalable services, enabling social and mobile capabilities. While Force.com streamlines development, debugging remains difficult without a real debugger or advanced tooling support.
Salesforce as a PaaS - Architecture of Force.com
- 1. SALESFORCE as PaaS Architecture of Rishabh Karajgi
- 2. 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
- 4. 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!
- 8. ➢ 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.
- 10. ● Architectural stack sits on top of the stack of cross cutting services. ● Any service can intersect with the architectural stack ● While the Architectural stack may be static, the service stack is scalable and dynamic, hence adding additional services becomes easy!
- 11. ● 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
- 12. Let’s get a bit more technical
- 13. Force.com - foundation of Salesforce Core components :
- 14. Multi-Tenancy Sharing IT resources ( Server, Databases, Application ) cost effectively and securely.
- 15. 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.
- 16. 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 )
- 17. 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