Looking for some design advice.
I’m using AF for the CLA and it feels like it makes sense for the Database to be a non-actor class that my controller Actor uses. Controller Actor would have Database class in its private data. Calls the databases methods when it needs info from it, so can access it as synchronously as it wants.
But every AF exam example I’ve seen has the database as a nested actor - Is there something I’m missing as to why people choose that?
I would have thought that given you’re supposed to request things from actors rather than demand them that it’s more aligned with actor design to not rely on a database actor to give you info back in any time period, unless you also put in a 'waiting for info' state. Yet it's in every example.
What gives me pause is this requirement:
“A separate user interface shall be provided to full access to the data records. The integration of the user interface in the main application will be done in future project”
If my database is an actor then it would be easier to add a UI to it in a future project- is that what’s making this difference?
I’ve attached one of the exam examples with the requirements for the database highlighted.
-------------------
CLD
