Skip to content

feat(forge): migrate sharded order core#18

Merged
fronzec merged 1 commit into
mainfrom
feat/spring-sharding-migration
Jul 19, 2026
Merged

feat(forge): migrate sharded order core#18
fronzec merged 1 commit into
mainfrom
feat/spring-sharding-migration

Conversation

@fronzec

@fronzec fronzec commented Jul 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Owner

Closes #17

Summary

  • Migrate the synchronized Spring and ShardingSphere order-service core into Forge.
  • Preserve the historical API, package identity, framework versions, and parity sharding rule.
  • Replace machine-bound datasource values with documented environment placeholders and add four infrastructure-independent tests.

Changes

Area Change
database-sharding/order-service/java-spring-shardingsphere/ Add Maven metadata, application source, ShardingSphere configuration, tests, and a minimal migration record.

Review Budget

This PR has 399 semantic lines plus 427 lines of unchanged generated Maven wrapper tooling. The wrapper is reported separately because splitting its scripts from the application would not improve reviewability or rollback.

Test Plan

  • Source main synchronized at c72d2e7; existing WIP remains in source stash@{0}.
  • ./mvnw test passed 4 tests with no failures, errors, or skips.
  • ./mvnw clean removed build output.
  • xmllint --noout pom.xml, YAML syntax parsing, and git diff --check passed.

Chain Context

Field Value
Chain Spring sharded order migration
Tracker PR Not needed
Position 1 of 2
Base main
Depends on None
Follow-up #19
Review budget 399 semantic + 427 generated wrapper lines
Starts at Synchronized source commit c72d2e7
Ends with Buildable sharded-order application core and tests

Chain Overview

main
 └── 📍 #18 Sharded order core
      └── #19 Runtime harness and documentation

Scope

  • Includes: application, sharding configuration, Maven wrapper, focused tests, and minimal status documentation.
  • Excludes: local containers, lifecycle commands, requests, full runtime documentation, source WIP, merge, and archival.

Autonomy

  • CI is expected to pass for this PR branch.
  • This PR has one deliverable scope.
  • This PR can be rolled back without unrelated experiments.
  • Tests are included with the application behavior.

Contributor Checklist

@fronzec Graphite App

fronzec commented Jul 19, 2026

Copy link
Copy Markdown
Owner Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@fronzec fronzec mentioned this pull request Jul 19, 2026
Merged
13 tasks
@fronzec fronzec added the type:feature New feature label Jul 19, 2026
@fronzec
fronzec force-pushed the feat/spring-sharding-migration branch from 6465216 to 17b08f1 Compare July 19, 2026 02:00
@fronzec Graphite App

fronzec commented Jul 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Owner Author

Merge activity

  • Jul 19, 2:01 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jul 19, 2:01 AM UTC: @fronzec merged this pull request with Graphite.

@fronzec
fronzec merged commit 676f820 into main Jul 19, 2026
2 checks passed
fronzec added a commit that referenced this pull request Jul 19, 2026
@fronzec
feat(forge): add sharding runtime harness (#19)
2a93a83 
Closes #16

## Summary

- Add a self-contained two-shard MySQL development runtime through `podman-compose`.
- Add safe environment placeholders, Taskfile lifecycle commands, and parity-focused HTTP requests.
- Expand the experiment record with setup, routing proof, tradeoffs, limitations, and verification evidence.

## Changes

| Area | Change |
| --- | --- |
| `database-sharding/order-service/java-spring-shardingsphere/` | Add Compose, environment example, Taskfile, requests, and complete experiment documentation. |
| `README.md` | Add the sharding experiment to the Forge catalog. |

## Test Plan

- [x] Parsed Maven XML and all four YAML files.
- [x] Re-ran `./mvnw test`: 4 tests passed.
- [x] Re-ran `./mvnw clean`; no build output remains.
- [x] Verified both stack ranges with `git diff --check`.
- [ ] Run container and physical routing proof; Podman 5.8.2 cannot connect to its stopped local machine and the limitation is documented.

## Chain Context

| Field | Value |
| --- | --- |
| Chain | Spring sharded order migration |
| Tracker PR | Not needed |
| Position | 2 of 2 |
| Base | `feat/spring-sharding-migration` |
| Depends on | #18 |
| Follow-up | None |
| Review budget | 248 / 400 changed lines |
| Starts at | The buildable sharded-order core from #18 |
| Ends with | A self-contained documented local sharding experiment |

### Chain Overview

```text
main
 └── #18 Sharded order core
      └── 📍 #19 Runtime harness and documentation
```

### Scope

- Includes: runtime harness, safe local configuration, requests, complete docs, and catalog entry.
- Excludes: framework upgrades, automated container orchestration scripts, source WIP, merge, and archival.

### Autonomy

- [x] CI is expected to pass for this PR branch.
- [x] This PR has one deliverable scope.
- [x] This PR can be rolled back without removing the application core.
- [x] Documentation records executed and skipped verification honestly.

## Contributor Checklist

- [x] Linked approved issue #16.
- [x] Used conventional commit format.
- [x] Added exactly one safe `.env.example`; real `.env` remains ignored.
- [x] Added no AI attribution or co-author trailers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

type:feature New feature

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

feat(forge): migrate sharded order core

1 participant

@fronzec