Strategic plan: Separate ObjectStack ecosystem, keep ObjectQL unified, optimize core by Copilot · Pull Request #257 · objectstack-ai/objectql

Copilot · 2026-01-30T00:59:30Z

Repository owner requested separation of ObjectStack ecosystem from ObjectQL, while keeping all ObjectQL components together in one repository, with specific kernel optimization requirements.

User Feedback: "我不希望拆得这么细，objectql相关的还是放在这个仓库中" (Keep ObjectQL components together, don't split too finely)

Deliverables

Strategic Documentation (4 files, ~2K lines)

REFACTORING_README.md - Navigation hub
KERNEL_REFACTORING_SUMMARY.md - Bilingual (EN/CN) executive summary
KERNEL_REFACTORING_RECOMMENDATION.md - 12-section architectural analysis (30K words)
KERNEL_REFACTORING_CHECKLIST.md - Phase-gated implementation plan with git commands

Revised Scope (Based on User Feedback)

Keep in ObjectQL Repository (Full Stack - ~130K LOC)

@objectql/types - Protocol contract
@objectql/core - Query AST, validation, repository pattern
@objectql/platform-node - Node.js bridge
@objectql/plugin-security - RBAC/FLS/RLS
All 8 drivers - SQL, MongoDB, Memory, Redis, Excel, FS, LocalStorage, SDK
All tools - CLI, Create, VS Code extension
All examples - Quickstart, showcase, integrations

Extract (ObjectStack Ecosystem → 2 new repos)

Runtime server → objectstack-runtime
Protocol plugins (GraphQL, OData, JSON-RPC) → objectstack-protocols

Optimization Requirements

10 kernel improvements identified with implementation specs:

Optimization	Target	Approach
Metadata registry	10x ops	Secondary indexes (O(n*m) → O(k))
Query planning	10x	AST compilation + LRU cache
Hook execution	5x	Pre-compiled pipelines, parallel
Connection pool	5x	Kernel-level global limits
Validation	3x	Compile validators once
Metadata loading	10x startup	Lazy + predictive preload
Type generation	5x	Worker threads, non-blocking
Dependencies	Auto-cascade	DAG-based topological sort
Query optimizer	2-5x SQL	Index hints, join reordering
Metadata storage	50% memory	SharedArrayBuffer off-heap

Example: Current vs. Optimized

// Current: O(n*m) package uninstall
class MetadataRegistry {
  unregisterPackage(pkg: string): void {
    for (const [type, items] of this.store) {
      for (const [name, item] of items) {
        if (item.package === pkg) items.delete(name);
      }
    }
  }
}

// Optimized: O(k) with secondary index
class OptimizedMetadataRegistry {
  private packageIndex = new Map<string, Set<MetadataRef>>();
  
  unregisterPackage(pkg: string): void {
    const refs = this.packageIndex.get(pkg);
    refs?.forEach(ref => this.primary.get(ref.type)?.delete(ref.name));
    this.packageIndex.delete(pkg);
  }
}

Migration Timeline (Revised)

12-week phased rollout (simplified scope):

W1-2: Create 2 ObjectStack repos, CI/CD setup
W3: git subtree migration for ObjectStack packages only
W4-10: Implement 10 optimizations
W11-12: Ecosystem alignment, v5.0 release

Key Changes from Original Plan

Repositories: 5 new repos → 2 new repos (only ObjectStack ecosystem)
ObjectQL Components: All stay together (drivers, tools, examples remain in ObjectQL repo)
Timeline: 16 weeks → 12 weeks
Impact: LOC reduction 150K→130K (only ObjectStack components extracted)

Benefits

✅ Simpler for ObjectQL users (everything in one place)
✅ Clear separation between ObjectQL and ObjectStack
✅ Lower migration complexity
✅ Optional ObjectStack integration

Original prompt

拉取请求: #255

我希望开发的是基于objectstack spec的整个生态，如果需要的话我可以优化升级它的内核代码，我认为插件生态和runtime不应该在本项目中。你可以给我提出具体对于。objectstack的改进要求，我可以调整内核项目。

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

vercel · 2026-01-30T00:59:34Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectql	Ready	Preview, Comment	Jan 30, 2026 6:27am

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

hotlong · 2026-01-30T06:17:03Z

@copilot 我不希望拆得这么细，objectql相关的还是放在这个仓库中

…ents together Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Copilot · 2026-01-30T06:25:08Z

@copilot 我不希望拆得这么细，objectql相关的还是放在这个仓库中

已根据您的反馈修订策略。现在只分离 ObjectStack 生态组件（runtime + protocols），所有 ObjectQL 相关组件（drivers、tools、examples）保留在本仓库中。

修订内容：

新仓库数量：5个 → 2个（objectstack-runtime、objectstack-protocols）
所有 @objectql/* 包保留在本仓库
时间表：16周 → 12周
代码行数：150K → 130K（仅移除 ObjectStack 组件）

详见最新文档：

KERNEL_REFACTORING_SUMMARY.md - 双语摘要
KERNEL_REFACTORING_RECOMMENDATION.md - 详细分析
KERNEL_REFACTORING_CHECKLIST.md - 实施清单

Commit: 04c986c

Co-authored-by: hotlong <50353452+hotlong@users.noreply.github.com>

Copilot

Pull request overview

This pull request introduces comprehensive strategic documentation for refactoring the ObjectQL repository structure based on user feedback. The PR responds to the repository owner's request to separate the ObjectStack ecosystem while keeping all ObjectQL components together in one repository.

Changes:

Creates 4 strategic documentation files (~2K lines) outlining a revised separation strategy
Defines 10 kernel optimizations for performance improvements
Provides a 12-week phased implementation plan with detailed checklists
Documents migration from a single repository to 3 repositories (ObjectQL + 2 ObjectStack repos)