SF Framework is basically designed to build web application in the form of modules. To provide reusable features, SageFrame provides SageFrame Library and API (Application Program Interface) to build modules in RAD (Rapid Application Development) environment. Components like Security, Authorization, Authentication, Client API and Messaging are the foundation of SF Library. As we can see in the image, SF Library is built on the top of ASP.NET; therefore, all features that are available in ASP.NET are available in SF Library as well.
SageFrame Module is the building block of SageFrame application. Be it a small feature or a very large application logic, everything is built in the form of SageFrame Module. SF Module architecture is designed in such a way that developers or our application (module) can interact directly with ASP.NET layer or with the database as needed in application logic. Moreover, SF Module supports templating feature as well. So, 'functionality with design' empowers SF Module with feature-rich capabilities as are required in the modern application development.
SageFrame Page is just a collection of modules, templates and page templates. By using modules and templates, SageFrame provides an application that user needs with custom UX and features. And at the same time, SageFrame provides granular privilege on page level as well as module level to the users.
As you can see, SF provides different ways of accessing data from different data sources like Web Service, MS SQL Database, XML or third-party Web Services. So, there are no such limitations for building any type of application in this structure. In short, SF architecture is an N-tier Controller Pattern Modular, Service-Oriented Architecture (SOA).