...
Page | Content / Findings |
---|---|
Describes “Modularity” as Modularity (and its integration counter-part) is considered at 3 distinct levels:
… Software Component and Entity levels modularity are fully in the scope (controlled by) of openIMIS. openIMIS is built modular "from the core on": even low level features (like login,...) and central features (like Insurance Scheme management,...) are built as a plugins of a core platform. The core platform provides generic components (building blocks) to be used by / particularised in the various plugins and is split in 3 layers:
Although openIMIS is an assembly of components (themselves assemblies of plugins), deployments of openIMIS doesn't impose a distributed deployment. The choice of isolating the various (server-side) components to dedicated infrastructure is taken according to each project's needs. Within a project, scaling up by distributing components as the load increases is a very standard (and easy) operation: Plugins are documented in openIMIS Modules. | |
In openIMIS, (nearly) everything is a module: even "low level" (and mandatory) features follow this principle. … Plugins (can) provide several types of archetypes, dedicated to the various openIMIS layers: openIMIS Mobile FE, openIMIS Web FE, openIMIS Online BE, openIMIS Batch BE,... openIMIS can be deployed with an extra layer dedicated to implement a FHIR API, based on openIMIS core (base) modules. Patrick Delcroix in the comments: Here my point of view on the module list details in 4 groups (core, business...) The module with * leading are not found in JLN IT core
Business
Register
Reporting
| |
| |
| |
|
...