monolith-modularization
Improve the internal structure of a monolith by introducing clear module boundaries, reducing coupling, and enabling future extraction if needed. Use when a monolith is becoming hard to change, or as a step toward possible service extraction.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- monolith-modularization
- description
- Improve the internal structure of a monolith by introducing clear module boundaries, reducing coupling, and enabling future extraction if needed. Use when a monolith is becoming hard to change, or as a step toward possible service extraction.
03 SKILL.md 正文
Monolith Modularization
Overview
A well-structured modular monolith often provides many of the organizational benefits of microservices with far less operational cost.
When to Use
- Monolith is painful to change or understand
- Teams are stepping on each other inside one codebase
- Preparing for possible future extraction of modules into services
Practices
- Identify candidate modules aligned with business capabilities / bounded contexts
- Enforce dependency rules (no deep reach-ins across module internals)
- Define clear public APIs for each module
- Reduce shared database entanglement where possible
- Improve testability of modules in isolation
- Use packaging, code ownership, and architectural tests to protect boundaries
Principles
- Modularization is valuable even if you never extract services
- Prefer modular monolith over premature microservices
- Boundaries should follow business seams more than technical layers
Verification
- Module boundaries are visible and mostly respected
- Changes in one module rarely require changes in many others
- Ownership of modules is clear
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.