Who it is for
Engineering leads and data platform owners in Taiwan who already run batch or streaming jobs and need an outside reader before the next rebuild.
What you leave with
A written architecture brief: source inventory, failure modes, recommended topology, sequencing for the next two releases, and an explicit list of what not to touch yet.
Scope
One product domain or one warehouse subject area. Typical window: current production paths plus the next planned schema change.
Included
- Kickoff to agree sources, SLAs you already promise, and which jobs are sacred
- Read-through of job definitions, orchestration graphs, and the last three incident notes
- Architecture brief with diagrams you can paste into your own wiki
- Live walkthrough with the commissioning lead (up to ninety minutes)
- A one-page annex for finance that explains why the rebuild costs what it costs
Not included
- Hands-on coding inside your repositories after the brief is delivered
- Managed cloud accounts or vendor contract negotiation
- Software installation on your machines (the optional local record-keeping utility is separate; see Available in Veve)
- Ongoing on-call coverage after the engagement closes
Who writes it
Mei-Ling Chen, pipeline consulting lead, with a second engineer reviewing every flagship brief.
How the work proceeds
- Source and sink inventory against what actually runs in production
- Latency and freshness map for the paths that matter to the commissioning team
- Draft architecture for factual correction by your engineers
- Final signed PDF and walkthrough
Duration
Four to six working weeks from a complete intake pack. Compressed calendars are declined rather than under-scoped.
Where the work happens
Remote sessions preferred. On-site days in Miaoli or Taipei can be arranged when diagrams live only on whiteboards.
What we need from you
Export job definitions and recent run logs as they exist. Do not rewrite them into a polished demo. A short glossary of your internal job names helps more than a cleaned spreadsheet.
Limits
We decline engagements where the only source is a slide deck with no running jobs. We also decline work that asks us to certify a vendor product we have not reviewed.
Fees
Fixed fee by number of source systems and whether streaming paths are in scope. See the Fees page for starting figures. Open the fee guidance.
Next step
Write to info@flow-dockcore.digital with the domain, the jobs that hurt most, and whether freshness SLAs are contractual. There is no enquiry form on this site. Address and telephone are on the contact page.