How ornl/intersect-architecture works
Project type and purpose
• This is the “INTERSECT Architecture Documentation” project—a documentation repository (Sphinx + RST) that describes a system-of-systems and microservice architecture for connecting scientific instruments, robot-controlled labs, and computing/data resources (edge, cloud, HPC).
File structure
• Top-level files:
• conf.py, Makefile, requirements.txt, Dockerfile, .readthedocs.yaml → standard Sphinx docs config and build scripts.
• README.md → overview of project purpose and usage.
• Key directories (each corresponds to a major doc section):
• examples/ → sample patterns (AAM).
• iri/ → design patterns and best practices for the Interconnected Resource Interface.
• ms/ → microservice classification, infrastructure, orchestration, deployment patterns.
• pat/ → science use-case design patterns (architectural, strategic).
• sos/ → system-of-systems (“SoS”) logical, physical, operational, data models, user interfaces.
README for additional insights
• The architecture comprises three pillars:
a. Science use-case design patterns (in pat/)
b. System-of-systems architecture (in sos/)
c. Microservice architecture (in ms/)
• It references edge/cloud/HPC, autonomous experiments, AI-driven workflows.
Detail
• Interaction with protocol or pattern (e.g., “HTTP/REST”, “gRPC”, “publish/subscribe”).