Question : Which of the following are the layers of an application? (Select all that apply) A. User Interface B. Business Logic C. Business Data D. Data Model E. Objects F. HTML G. Java Script
Explanation: Force.com is Salesforce.com's cloud computing platform as a service (PaaS) development framework. It facilitates developers in building multi-tenant applications to be hosted by and presumably integrated to Salesforce.com. Force.com development is performed using nonstandard, purpose-built tools and a proprietary development language called Apex. Specialized tools are designed for the presentation layer, application layer and data model. For example, Visualforce uses an XML-like syntax for building user interfaces in HTML, Ajax or Flex. The Apex language mimics a C-style syntax and is a pseudo-combination that resembles Java and SQL (structured query language). To maintain integrity, extensibility and continued evolution, custom developed code is positioned in layers of abstraction whereby Force.com's runtime engine can interpret the metadata at the point of execution. Force.com accelerates development time for cloud-based applications that tap into the core Salesforce.com application and hosting delivery network. Developers inherit cloud infrastructure components such as a strong multi-tenant architecture, security and scalability as well as consumer benefits such as mobility and social media tools. On the flip side, many ISVs (independent software vendors) are reluctant to commit to a proprietary development environment that does not have the maturity, depth, tools or market acceptance as compared to more mainstream products such as Microsoft .NET or Java/J2EE. Also, as Salesforce.com's CRM application does not offer cloud portability programmers become locked-in to Salesforce.com's technology, application and hosted delivery network. When considering Force.com, developers often find themselves balancing the sale opportunity from the sizable Salesforce.com captive customer base versus the broader industry at large.a
Question : Data and process-centric applications are best suited for Force.com.
Explanation: Force.com is the only fully integrated design and development platform for building and deploying cloud based custom apps. The Force.com platform allows your company to build apps up to five times faster at half the cost compared to traditional platforms like Java or .NET. The Force.com platform eliminates the usual upfront capital expense of new projects, reduces operating expenses, and easily scales to any size workload. Companies use Force.com to build a vast array of solutions, particularly data and process-centric applications. Some examples of what apps can be built with Force.com: " Lotus Notes replacement, departmental apps (HR, finance, IT, etc.) " Business process apps (electronic health records, insurance claims, inventory management, etc.) " Data-driven websites (e-commerce launch with rapid scalability, cross-selling, etc.)
By freeing your IT organization from assembling and maintaining infrastructure, and freeing developers from having to reinvent the wheel building new components, Force.com offers your business a better way to innovate and meet your needs.
Explanation: You can describe salesforce.com as a two-, three-, or four-tier system.
Server Client Model Controller View Model Business Logic View Logic View
Two tier describes salesforce.com when using an API. The server provides model and business logic services, while the client provides the client business logic and/or a view. This includes Visualforce that is AJAX-only, where the page is rendered by JavaScript or HTML, and all database calls are handled through JavaScript only. Mobile applications may also be considered in this category when using a native app.
Three tier can describe salesforce.com when using the GUI. The model provides database and business logic services, the controller can provide business and view logic services, and the view provides the graphical interface. The controller may be a standard controller, a hybrid of standard and custom controllers, or a pure custom controller.
Four tier describes the model salesforce.com uses most accurately; each tier can be individually tweaked or even replaced without necessarily needing to alter the other tiers, which is a requirement to be classified as a four tier system. The model can have fields added, for example, without altering the other three layers. Similarly, a new database trigger can be added to the business logic layer without necessarily having to change the model, page controllers, or pages.
The four tier model is important to note, because it is possible to interact with just certain layers. For example, you can truncate the model's data, or mass update a picklist value, without interacting directly with the business logic layer. By using the API, you can bypass the controller logic and view without bypassing the business logic or model. And, of course, you can build an application that treats salesforce.com as one layer of its own two or three layer architecture.
So, when you're asked if salesforce.com is a two-tier or three-tier application, you can say, "Well, actually, it uses four tiers." ... Or just stick with three tier, since more people understand that than a four-tier system; just remember that MVC doesn't exactly describe the system 100%. It's more complex than that.