We're in the process of revamping a web application which is relatively large. I would like to use the "Providers" design pattern for numerous reasons, but I'm not sure it will be enough to convince management. Currently, we log in a user through manual database calls, and at the same time retrieve tons of other information on that user and dump it all into the Session, which is relatively efficient since no further database lookups for any demographic or credential information are required during use.Can someone help me expand these argument FOR using Providers?:The "Provider" design pattern follows a standard API, but that API is then open to your own customization. For example, the method GetUser is provided for you to implement however you need to get a user.