Architecture review
Independent review of an existing AOP or proxy architecture, with a migration path to generated code, GraalVM and JPMS where it makes sense.
A three to five day engagement that produces a written assessment of your current setup and a concrete migration plan. We look at the architecture as a whole, not just individual classes.
When this is the right format
- You have a working but ageing AOP setup (Spring AOP, AspectJ, ByteBuddy agents, javassist-based wrappers) and want to know whether — and how — to move away from it.
- You are planning a Java-version upgrade (especially to a JPMS-strict module graph) and want to de-risk the proxy and reflection touch-points first.
- You want GraalVM native image and you are tired of reflection configuration files.
- You are about to write your own annotation processor and want a second opinion on the design.
What we do
Day 1 — Discovery. Walk through the proxy/AOP touch-points with you. Read the relevant code, build configuration, runtime configuration. Identify the top three risks and the top three opportunities.
Days 2–3 — Deep dive. Trace reflection usage, classloader paths, JPMS module exports/opens, startup-time hot paths. Sketch the alternative architecture. For one or two representative classes, write the migrated version and benchmark it.
Day 4 — Migration plan. Write up the recommendation: keep, move, replace. Concrete order of operations. Risks and reversibility for each step.
Day 5 — Walk-through. Present the report to your team. Discuss alternatives. Answer questions.
What you get
- Written report. 8–15 pages, English or German. Architecture diagram, risk register, migration plan, ordered backlog of work items with rough estimates.
- Working proof-of-concept. Migrated version of one or two representative classes, checked in alongside the original for comparison.
- Live walk-through. A scheduled call with your team — typically the architects plus the engineers who will execute.
- Two follow-up office-hour calls of 45 minutes each, scheduled within three months.
Logistics
- Format: Remote by default. On-site for the discovery day is sometimes worth the travel — discuss.
- Pricing: From €1,800 per day. Standard engagement is 3–5 days; longer reviews are scoped explicitly.
- Confidentiality: Mutual NDA before discovery starts. Customer-side data stays customer-side; we work on a copy of the code in a private branch you control.
- Language: English or German.
- Lead time: Two to four weeks; sometimes within a week.
Ready to talk?
First 30-minute call, no commitment. We see if the engagement fits and how to scope it.