I was just curious, what data if any does your product hold in the HTTP session object.
I am just wondering if it is worth it for me to come up with a solution for session replication or session affinity in a distributed environment (like terracotta web sessions).
I know the cart is persisted to a database.
Is there anything of importance that I should be aware of that is stored in memory and not in the database?
If a user logs on an establishes a session on box A, what will be lost if the user transistions to box b?
Thanks in advance.
-Roy
The server engine doesn't hold client state but the client engine does hold state in the session, so if you are intending to use our store front application (which in turn uses the client engine) you should implement sticky sessions when load balancing.
If you intend using our server engine through the Java API or web services API, then you can pick a different instance on each request.