Repository navigation
Home
This wiki contains the architecture documentation of RayMigrator, structured according to the arc42 template. RayMigrator is a cross platform database migration framework for versioned, release based schema migrations across SQL Server, PostgreSQL, MariaDB, MySQL and SQLite.
The pages here describe why the system is built the way it is and how its
parts fit together. The detailed implementation and configuration reference
lives in the repository under
Docs/ and is linked
from each chapter.
| # | Chapter | Answers |
|---|---|---|
| 1 | Introduction and Goals | What is RayMigrator, for whom, and what must it achieve? |
| 2 | Architecture Constraints | Which technical, organizational and legal constraints shape it? |
| 3 | Context and Scope | Where are the system boundaries, who and what interacts with it? |
| 4 | Solution Strategy | Which fundamental decisions and approaches drive the design? |
| 5 | Building Block View | How is the system decomposed into projects, layers and components? |
| 6 | Runtime View | How do the building blocks interact in the important scenarios? |
| 7 | Deployment View | How is RayMigrator built, packaged, distributed and run? |
| 8 | Crosscutting Concepts | Which concepts apply across the whole system? |
| 9 | Architecture Decisions | Which important decisions were made, and why? |
| 10 | Quality Requirements | Which quality goals matter, expressed as concrete scenarios? |
| 11 | Risks and Technical Debt | What are the known risks and debts? |
| 12 | Glossary | Which terms are used, and what do they mean? |
The wiki is generated from
Docs/arc42/
on the main branch. Edit the Markdown files there and open a pull request;
edits made directly in the wiki are overwritten by the next sync.
Generated from Docs/arc42/ on main. Do not edit pages in the wiki directly; changes are overwritten by the next sync.