Skip to content
JM.
Back to projects

Configuration Management and Work-Order Platform

Spring Boot microservices for tracking configuration changes, validating templates, and orchestrating work-order workflows across network domains.

Backend Engineering, professional work for an employer

Problem and motivation

Manual network configuration changes across distributed devices introduce human error and prolong provisioning times. Changes need to be tracked, validated, and traceable from request to completion.

Solution and architecture

Modular Spring Boot microservices expose REST APIs for configuration and work-order workflows, validate configuration templates, orchestrate multi-step work orders, and audit every deployment state, backed by relational and wide-column storage and deployed on Kubernetes.

My role

Backend development on microservices and their deployment. This was professional work for an employer.

Technology stack

  • Java
  • Spring Boot
  • MySQL
  • Cassandra
  • Docker
  • Kubernetes
  • Maven

Key engineering decisions

  • Keep services small with clear API contracts, separating template rendering from device execution.
  • Choose the data store per access pattern rather than using one for everything.
  • Use a transactional outbox pattern to keep configuration services and audit logs reliably in sync.

Challenges and solutions

  • Recovering gracefully from transient transport failures mid-workflow.

    Idempotent configuration APIs and explicit, resumable state transitions.

Lessons learned

  • Idempotency in network configuration APIs is crucial for recovering gracefully from transient failures.
  • Database constraints and application validation serve different purposes; use both.
  • MCP-based Network Configuration Agent

    AI Agents and MCP, professional work

    A Model Context Protocol server exposing secure, capability-limited tools so agents can read and reason about network configuration data.

    • Spring AI
    • MCP
    • Java
    • Spring Boot
    • REST APIs