Facade design pattern with states?

As you already say, having more than 100 APIs in one class is not a good idea. They can be split into different facade classes. Common functionality can be moved to base classes.

This is not a design pattern but core of OO. The state can still be maintained. I am not sure if you are already using the session as a store to save state.

If so you can still continue to do so.

If we go by the principles of Domain-Driven Design, then you can separate your system into stateless services and stateful entities. Combining services and state machines in a single facade is not necessarily a good idea.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.