Which three actions restrict the ability of a web application to scale in response to load as
additional computing resources are made available to it?
A.
Implementing the Singleton pattern in the web tier
B.
Implementing core business logic in the web tier
C.
Implementing core business logic using stateless session beans
D.
Storing users’ session state in a database
E.
Maintaining users’ session state by using stateful session beans
Why on earth would stateless session beans restrict scaling? I would have probably said D instead on C
Maintaining users’ session state by using stateful session beans woud also restrict scaling?
a,b,d
ADE
ABD is correct?
ABE
ABD is correct answer.
ABD
Why D ?
If we moved the storage from an in-memory tier to a persistent tier – at the end of the day, you might end up facing scalability issues because of the Database. I am not saying this will happen for sure, but depending upon your application, your DB might get overloaded and latency might creep in e.g. in case of a fail over scenario, think about recreating the entire user session state from the DB for use within another cluster instance – this can take time and affect end user experience during peak loads.