Techniques for decoupling access to infrastructure models
In example embodiments, techniques are provided for decoupling user access to infrastructure models from proprietary software that maintains and updates the infrastructure models. A backend application may include an infrastructure modeling backend module that, among other functions, handles communication with an infrastructure modeling frontend module of a frontend application that provides user access to the infrastructure model, infrastructure modeling hub services that maintain repositories for the infrastructure model, and an infrastructure modeling native module that creates, performs operations upon, and updates local instances of a database that stores the infrastructure model. While the infrastructure modeling backend module may pass information obtained from the infrastructure modeling frontend module and infrastructure modeling hub services to the infrastructure modeling native module, it may be functionally separated from the software of the infrastructure modeling native module that understands how to maintain and update infrastructure models, including interacting with local instances of the database.
1. A system comprising:
one or more computing devices that include one or more processors and one or more memories coupled to the processors, the one or more memories configured to store software modules executable on the processors, including:
an infrastructure modeling backend module configured to
obtain from an infrastructure modeling frontend module a request to open an infrastructure model,
call infrastructure modeling hub services executing on the one or more cloud computing devices to obtain one or more changesets from a repository applicable to a local instance of a database that stores the infrastructure model,
provide the one or more changesets to an infrastructure modeling native module,
obtain a request to perform an operation on the infrastructure model, and
call the infrastructure modeling native module to perform the operation; and
the infrastructure modeling native module configured to
in response to receipt of the one or more changesets from the infrastructure modeling backend module, apply the one or more changesets to the local instance of the database to update the local instance, and
in response to receipt of the call to perform the operation, perform the operation on the local instance of the database, the operation to include at least one of inserting into, deleting from, or querying about models, elements, or properties,
wherein the infrastructure modeling backend module is functionally separated from the infrastructure modeling native module and lacks ability itself to interact with the local instance of the database.
2. The system of claim 1 , wherein the infrastructure modeling native module is further configured to return to the infrastructure modeling backend module, a response based on the performed operation, the response usable to update a display of the infrastructure model.
3. The system of claim 1 , wherein the infrastructure modeling frontend module is part of an infrastructure modeling frontend application configured to execute on a client device.
4. The system of claim 1 , wherein the infrastructure modeling frontend module is a part of a web frontend application that is configured to execute within a web browser on a client device.
5. The system of claim 1 , wherein the infrastructure modeling frontend module is a part of a desktop frontend application on a client device that includes an embedded web browser, and the infrastructure modeling backend module is a part of a backend application on the client device.
6. The system of claim 1 , wherein the operation is to insert an element into the infrastructure model.
7. The system of claim 1 , wherein the operation is to retrieve properties of an element of the infrastructure model.
8. The system of claim 1 , wherein the operation is to generate a database query against the instance of the database storing the infrastructure model.