In-process, out-of-processs

ScimoreDB Embedded provides software developers multiple ways of instantiating the database. Depending on the application requirements, the developer can choose the optimal model.

In-process

ScimoreDB Embedded can be loaded into the process space of the client application. This way, the database engine hides completely behind the program it is deployed with and the end user will never notice that their applications are running ScimoreDB Embedded.

Out-of-process

ScimoreDB Embedded is capable of running in a separate process. The first application accessing the embedded database, will start the database process. Other applications, will be accessing the existing database process. When all applications stop using the embedded database, the embedded database process will stop.

Using out-of-process you gain reliability, and it's the default and prefered way of using ScimoreDB Embedded.

With the out-of-process feature, ScimoreDB Embeeded allows multiple applications to use the same database: whether it’s the database manager accessing the database while the client application is running, or it’s multiple deployed applications sharing the same database, or multiple web processes accessing the same database – ScimoreDB Embedded supports it all.

Read more about the different ways to instantiate the ScimoreDB engine.