Skip to content

Scaling MAGI #3

@isi-lincoln

Description

@isi-lincoln

So this is to talk / track the concept of making MAGI a bit more modern.

The idea being is that each module is a service, services expose RESTful API. MAGI takes with the module to implement the functionality. Modules (services) are self-contained, handle error checking, and wont cause MAGI to crash.

Some amount of code rewrite is necessary. The idea is if we can gut MAGI to keep only the necessary state, limit the amount of overhead, and access modules via API. In the process make it so MAGI can be testbed independent (which as I understand it - it has hardcoded values for DETER)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions