Model in sessions

Question

I have a GRID (table) that when selecting an item through the ID I load the entity in a session via ajax.

public static class Sessoes
    {
        public static Produto Produto
        {
            get
            {
                return (Produto)HttpContext.Current.Session["Produto"];
            }
            set
            {
                HttpContext.Current.Session["Produto"] = value;
            }
        }
    }

I wonder if it would be a bad decision to save every entity in a session? What do you think? Is there/know any disadvantage in using this practising?

Answer 1

Has several drawbacks.

In this link, for example, the author teaches how to easily capture data from a session.

By putting his Produto within a Session, you lose lazy load capacity because the assignment will cause the object to be highlighted from the context. Changes to it will also not be mapped.

There is also the aggravation of using your application in a distributed environment, with load balancing (Azure environments, other than virtual machines, for example). Using this approach, your application will fail at runtime as Sessions have not been well implemented for this type of environment.

To Session needs to be viewed as a temporary cache per user, and not as a general data storage resource, as is, for example, a ViewBag or a dictionary ViewData.