I'm about to start work on a project that uses some complex models. The storage of the entities to which these models map is rather odd:
- their full details span tables across several databases;
- reading their details is a combination of reading from these databases plus querying an external service;
- updates to them do not occur through the database at all but through an external service.
The external service is a server (or several) with which I exchange UDP messages.
These are hard constraints that are out of my control so I have to work with them. The obvious solution is to just have a class for each entity and write getters and setters that interact with the databases and external service like I need them to. But from everything I've read that sounds like it goes against the ethos of Phalcon's models and their ties to ORM. Can Phalcon support models with such a strange persistency layer?
I'm new to Phalcon, MVC and ORMs, so perhaps I'm asking a silly question. I couldn't find anything on this forum or elsewhere however.