๐ก Enterprise Archi Principles: High โ Executive Summary
Technical architectural analysis, practical configuration manifests, and deployment instructions for Enterprise Archi Principles: High.
๐ Table of Contents
Business
Repository
Architecture & System Flow
Diagram
Application
Cluster Overview
Architecture & System Flow
Diagram
GitOps
Architecture & System Flow
Diagram
CI/CD
Architecture & System Flow
Diagram
Jenkins CI
Architecture & System Flow
Diagram
North-South Traffic-flows
Architecture & System Flow
Diagram
East-West Traffic-flows
Architecture & System Flow
Diagram
GitOps
Node-self Helmfile
Architecture & System Flow
Diagram
ArgoCD
Architecture & System Flow
Diagram
CICD
Architecture & System Flow
Diagram
Monitoring
Thanos Deployments
Architecture & System Flow
Diagram
Extra
Hardware
Networks
Architecture & System Flow
Diagram
E2E Testing tool
Architecture v1 (backend dependent) + API token
- Suggestions for existing architecture problems
1. Necessity of selecting AI service call method (Agent VS API)- Optimality of Harness Engineering in the Agentic AI Environment
- Harness technology is a core optimizer that helps AI agents self-correct errors and reliably control local tools
- Licensing structure issues
- โLLM API Tokenโ and โAgent AI Asset (Solution Framework)โ have an independent licensing system that is completely separate conceptually and contractually.
- Server operation risk
- Unlike stable one-time API calls, when running AI that thinks and acts directly on the server, the risk of system down due to server overload and infinite loop is very high
- WebSocket Transmission
- Real-time screen streaming structure using web sockets is difficult to implement technically and consumes a lot of development resources.
- Optimality of Harness Engineering in the Agentic AI Environment
Architecture & System Flow
Diagram
Architecture v2 (Local Packaging) + Local Agentic AI
- Architecture Features
1. Provide npm-based local initialization- Provide agent options
- Provides playwright and agent installation
- Licensing
- Basic harness configuration pre-complete
- Optional: Call the backend and load existing harness settings, etc.
- Integration (automation) of Chrome extension distribution
- The backend exists for log recording, migration, and inquiry
- Actual execution is performed by calling the agent on localhost.
- You can also operate the backend directly from localhost. (management page)
- Uses playwright directly locally by playwright-mcp, so headed tests are stable
- Provide agent options
- Threshold
- Inference calculations use the cloud, so they do not require a GPU, but they basically look for the specifications of the test terminal.
- cpu/ram
Architecture & System Flow
Diagram




Leave a Reply