I want to show Components in a tabs , so first of all create few components. In this project we have three components, First View Component public class AllViewComponent : ViewComponent { private readonly UserManager<ApplicationUser> _userManager; public AllViewComponent(UserManager<ApplicationUser> userManager) { _userManager = userManager; } public async Task<IViewComponentResult> InvokeAsync() { List<StudentViewModel> allUsers = new List<StudentViewModel>(); var items = await _userManager.Users.ToListAsync(); foreach (var item in items) { allUsers.Add(new StudentViewModel {Id=item.Id, EnrollmentNo = item.EnrollmentNo, FatherName = item.FatherName, Name = item.Name, Age = item.Age, Birthdate = item.Birthdate, Address = item.Address, Gender = item.Gender, Email = item.Email }); }
In this architecture of SQL server, it is possible to keep the UI-centric processing on a computer, near the client. In addition, database developer may keep the data-centric processing components on another computer near the database server, so that you get significant performance benefits.
Three-tier architecture is used till the manageable size of business tier. As the business complexities increases, the business tier became larger and unmanageable. This led to the evolution of N-tier architecture, where the business services model was divided into smaller manageable units. N-tier architecture is also called as multi-tier architecture.
The N-tier architecture consists of the following layers:
A banking application, when further expanded, can depict an example of n-tier architecture. The client tier would deal with the user interface, which would include the user interface controls, such as forms, menus, and toolbars. The server tier would comprise data-handling including saving data to the database server.
The business logic would include the rules and guidelines for different types of accounts, Interest rates, fixed deposits, ATMs, and overdrafts. All these would form the middle tier. However, there would be some rules that need to be implemented on the user interface and on the database. You can place these rules either on the UI-centric processing components of data-centric processing components, based on the functionality.
Applications that follow multi-tier architecture can be used across various locations. For Example, in Web applications, the application is stored on the Web server. The clients access the application from any location through a browser software. The clients make requests and receive response from the Web server.
The Web server transfers the request for data to a database server, as shown in the following figure.
In above diagram, all the computers are web clients, remains are specified. Depending on the relevance of the business rules, they can be implemented on any of the tiers, such as the Web clients, Web server, or the database server.
To provide support to applications where users can send requests simultaneously, the database server needs to be a fast, reliable, and secure. SQL Server 2005 is one such comprehensive database platform that provides a fast, reliable, and secure RDBMS. It also helps in data analysis with integrated tools.
Here BI application is an application that is used by the top management of an organization for data analysis to make future decisions. BI tools are the tools that help in creating reports that enable data analysis.
Three-tier architecture is used till the manageable size of business tier. As the business complexities increases, the business tier became larger and unmanageable. This led to the evolution of N-tier architecture, where the business services model was divided into smaller manageable units. N-tier architecture is also called as multi-tier architecture.
The N-tier architecture consists of the following layers:
- Client tier
- UI-centric processing components
- Data-centric processing objects
- Database server
A banking application, when further expanded, can depict an example of n-tier architecture. The client tier would deal with the user interface, which would include the user interface controls, such as forms, menus, and toolbars. The server tier would comprise data-handling including saving data to the database server.
The business logic would include the rules and guidelines for different types of accounts, Interest rates, fixed deposits, ATMs, and overdrafts. All these would form the middle tier. However, there would be some rules that need to be implemented on the user interface and on the database. You can place these rules either on the UI-centric processing components of data-centric processing components, based on the functionality.
Applications that follow multi-tier architecture can be used across various locations. For Example, in Web applications, the application is stored on the Web server. The clients access the application from any location through a browser software. The clients make requests and receive response from the Web server.
The Web server transfers the request for data to a database server, as shown in the following figure.
In above diagram, all the computers are web clients, remains are specified. Depending on the relevance of the business rules, they can be implemented on any of the tiers, such as the Web clients, Web server, or the database server.
To provide support to applications where users can send requests simultaneously, the database server needs to be a fast, reliable, and secure. SQL Server 2005 is one such comprehensive database platform that provides a fast, reliable, and secure RDBMS. It also helps in data analysis with integrated tools.
Here BI application is an application that is used by the top management of an organization for data analysis to make future decisions. BI tools are the tools that help in creating reports that enable data analysis.
Comments
Post a Comment