Tagged articles
13 articles
Page 1 of 1
AI Architecture Hub
AI Architecture Hub
Apr 27, 2026 · Artificial Intelligence

Sub-Agent vs Agent Team: Choosing the Right Architecture for Complex AI Tasks

The article analyzes why many AI projects misuse multi‑agent setups, explains the fundamental differences between Sub‑Agent (isolated parallel executors) and Agent Team (collaborative teams with shared state), and provides concrete guidelines, code examples, and design principles to select the appropriate architecture for a given task.

AI agentsAgent TeamMulti-Agent Architecture
0 likes · 10 min read
Sub-Agent vs Agent Team: Choosing the Right Architecture for Complex AI Tasks
Top Architecture Tech Stack
Top Architecture Tech Stack
Mar 20, 2026 · Artificial Intelligence

How to Scale AI‑Powered Parallel Coding: Worktree, DevSwarm, or Orchestrator?

The article examines three practical approaches—Git worktree with multiple terminals, UI‑driven DevSwarm tools, and an orchestrator pattern—for enabling multiple AI agents to develop code concurrently, compares their trade‑offs, and offers guidance on selecting the right method for individual developers, teams, or bulk repetitive tasks.

AI DevelopmentClaudeDevSwarm
0 likes · 7 min read
How to Scale AI‑Powered Parallel Coding: Worktree, DevSwarm, or Orchestrator?
Design Hub
Design Hub
Mar 17, 2026 · Artificial Intelligence

How to Manage 10 Claude Code Agents Without Losing Your Mind

The article analyzes how Artem Zhutov structures a multi‑agent AI workflow by replacing chaotic browser tabs with named workspaces using cmux, programming a single orchestrator agent, and visualizing status through an Obsidian dashboard, turning ten Claude Code agents into a scalable, controllable system.

AI agentsClaudeObsidian
0 likes · 12 min read
How to Manage 10 Claude Code Agents Without Losing Your Mind
AI Insight Log
AI Insight Log
Feb 11, 2026 · Artificial Intelligence

Why 2026 Will Turn Developers into AI Orchestrators, Not Coders

Anthropic's 2026 Agentic Coding Trends Report predicts that AI will handle most tactical coding tasks, forcing engineers to become orchestrators who define architecture, break down work for AI agents, and validate outcomes, while also highlighting new collaborative agent swarms, marathon‑length AI projects, and emerging security challenges.

AI CodingAI agentsAnthropic
0 likes · 10 min read
Why 2026 Will Turn Developers into AI Orchestrators, Not Coders
Architects Research Society
Architects Research Society
Sep 2, 2025 · Artificial Intelligence

What Really Sets True Agentic AI Apart from Pseudo‑Agent Systems?

The article contrasts pseudo‑agent AI—such as simple LLM chatbots, RPA scripts, and RAG systems—with genuine agentic AI architectures that combine large language models, orchestrators, memory stores, tool‑calling, planning modules, and multi‑agent collaboration, highlighting key capabilities like autonomous planning, feedback loops, and dynamic tool coordination.

Autonomous PlanningLLMOrchestrator
0 likes · 3 min read
What Really Sets True Agentic AI Apart from Pseudo‑Agent Systems?

Design and Implementation of MySQL High Availability Using Orchestrator and DBProxy

This article presents a comprehensive design and implementation for achieving MySQL high availability by replacing the single‑master architecture with Orchestrator‑driven automatic failover, integrating DBProxy for transparent routing, and addressing topology changes and data compensation to ensure continuous, reliable service.

DBProxyData CompensationDatabase Replication
0 likes · 16 min read
Design and Implementation of MySQL High Availability Using Orchestrator and DBProxy
Aikesheng Open Source Community
Aikesheng Open Source Community
Nov 24, 2022 · Databases

Understanding Orchestrator's RegroupReplicasGTID and Candidate Replica Selection in MySQL Failover

This article explains how Orchestrator selects a candidate replica during MySQL master failover, detailing the GetCandidateReplica and RegroupReplicasGTID functions, their sorting logic, promotion rules, GTID-based regrouping, and differences from MHA, while highlighting potential data loss issues and related bugs.

GTIDOrchestratorReplication
0 likes · 22 min read
Understanding Orchestrator's RegroupReplicasGTID and Candidate Replica Selection in MySQL Failover
Aikesheng Open Source Community
Aikesheng Open Source Community
Nov 17, 2022 · Databases

DeadMaster Recovery Process in Orchestrator

This article explains the complete DeadMaster recovery workflow of Orchestrator, detailing how the system selects the appropriate check‑and‑recover function, handles emergency grace periods, reads topology information, registers recovery attempts, validates promotion constraints, executes the actual failover, and runs post‑recovery hooks, with extensive Go code examples.

GoOrchestratorRecovery
0 likes · 18 min read
DeadMaster Recovery Process in Orchestrator
Aikesheng Open Source Community
Aikesheng Open Source Community
Nov 7, 2022 · Databases

Orchestrator Failover Process Source Code Analysis – Simulating Faults and Understanding ContinuousDiscovery

This article walks through a simulated MySQL 3307 cluster failure, examines Orchestrator's source code to explain the ContinuousDiscovery loop, discovery queues, health ticks, caretaking tasks, raft coordination, topology snapshots, and the logic distinguishing UnreachableMaster from DeadMaster states.

ContinuousDiscoveryDatabase HAGo
0 likes · 20 min read
Orchestrator Failover Process Source Code Analysis – Simulating Faults and Understanding ContinuousDiscovery
JavaEdge
JavaEdge
Mar 21, 2021 · Databases

From Single MySQL to Cluster: Master‑Slave Replication, High Availability, and Scaling Strategies

This article explains why growing MySQL workloads require moving from a single instance to a clustered architecture, details the mechanics of master‑slave replication, asynchronous, semi‑synchronous and group replication, and evaluates various high‑availability solutions and read‑write splitting techniques.

Group ReplicationMHAOrchestrator
0 likes · 18 min read
From Single MySQL to Cluster: Master‑Slave Replication, High Availability, and Scaling Strategies