I have a ‘thin’ (SOAP) API that only knows how to set and get entities in the underlying system.
I am about to to create a ‘rich’ API that encapsulates the ‘thin’ API and implements the logic that is required for complex operations that entail getting and setting several entities in specific order.
Example: The rich API will be responsible for creating a new user account by creating a ‘Lead’ entity that’s linked to an ‘Account’ entity via the thin API.
I’m stuck in a naming block so I turn to SO 😉 What name would you give my rich API? ‘xxxRichAPI’? ‘xxxHelper’? ‘xxxService’?
At first glance, this sounds like the GoF Facade pattern to me. You might considering using the name ‘xxxFacade’.