Data Platform Architecture: Runtime First
By William Zhu & the InfiniSynapse Data Team · Published: 2026-09-02 · Last updated: 2026-09-02 · Last verified: 2026-09-02 · Next review: 2026-12-02 · Editorial standards · Corrections
Table of Contents
- TL;DR
- What data platform architecture hosts beside the database
- A three-layer frame: database, runtime, app
- Another warehouse, another app, or a runtime
- Landscape: stores, runtimes, and shells
- How to map the runtime before you buy a store
- Desk sample: database vs runtime vs app (illustrative)
- Scorecard: add a warehouse or host the job
- Failure modes
- Frequently Asked Questions
- Conclusion
TL;DR
Direct answer: Data platform architecture for agents is a runtime with isolation and resume, sitting beside the database. Adding another warehouse does not host the Decision Job. Draw database versus runtime versus app. Put state, artifacts, and the veto on the runtime. The database keeps facts. The app keeps screens.
We review these patterns at the InfiniSynapse desk on sanitized composites. Figures on this page are illustrative, not customer uplifts.
What you'll learn:
- Why data platform architecture is a runtime first, a store second
- Which layer owns state, SQL, UI, and secrets
- A mapping sequence that stops a warehouse purchase from pretending to be a host
- When to keep the database you have
- How this map sits under the data infrastructure hub
What data platform architecture hosts beside the database
Key Definition: Data platform architecture for agents is the placement of a hosted runtime—identity, isolation, resume, quota—beside the database that holds facts. The runtime hosts the Decision Job. The database does not. A new warehouse slide is not data platform architecture. It is a store purchase.
Teams still draw data platform architecture as boxes labeled lake, warehouse, and BI. That drawing answers “where do facts rest.” It does not answer “who hosts the work after the question is asked.”
The NIST AI Risk Management Framework treats AI as a system with owners and failure modes. Use that system lens for data platform architecture. A store without a runtime is not a system for an agent job.
The AWS Machine Learning Lens still treats workload identity, isolation, and recovery as architecture. Data platform architecture for agents inherits that bar even when the worker is a model.
Runtime is not a synonym for database
A database answers queries. A runtime hosts a job that may stall, retry, and write files. Data platform architecture must keep those verbs on different objects. If you collapse them, resume becomes a query log and isolation becomes a shared role.
The FTC home page is a reminder that automated decisions attract scrutiny. Data platform architecture that cannot show who hosted the job will not survive that scrutiny with a warehouse diagram.
Why another warehouse does not host the job
A warehouse can be the correct next store and still leave data platform architecture unfinished. The Decision Job still needs an id, a checkpoint, and a veto. Those are runtime objects.
Analyze a database without ETL is the source-binding lesson: point at what you already authorize. This page is the placement lesson: the bind is not the host. Data platform architecture needs both.
A three-layer frame: database, runtime, app
Draw three layers before you add a box. That drawing is a map you can defend.
| Layer | Owns | Does not own | Acceptance signal |
|---|---|---|---|
| Database | Facts, grants, query engines | Job identity, resume, veto | A killed agent job is not a dropped table |
| Runtime | Job id, events, views, artifacts, quota | Domain copy, final business action | The same id reopens after a tab close |
| App | Screens, domain rules, the human action | Secrets, checkpoints, deny lists | A theme change does not move the trail |
Google BigQuery documentation is a store-and-query surface. Point the runtime at BigQuery. Do not call the project a finished platform because the query was fast.
What each layer must refuse
The database must refuse to be the job log. The runtime must refuse to be the product UI. The app must refuse to store secrets. Data platform architecture is those three refusals written down.
Python documentation shows how a notebook can look like all three layers. A notebook can be a view factory. It is not the three-layer map.
Choose the three-layer frame if more than one app will share facts and jobs. Choose a single-process script if you are still proving a question and you accept that you will throw the script away.
The definition page on what is data infrastructure lists runtime, isolation, resume, and quota. This page places those objects beside the database. Definition without placement is a slogan. This page is the placement.
Another warehouse, another app, or a runtime
Teams pick the wrong next box. The runtime column is the one that hosts the job.
| Next box people buy | What it actually is | Choose it if | Reject it if |
|---|---|---|---|
| Another warehouse | Facts at rest | You lack a durable grain | You think the purchase hosts the job |
| Another BI app | A screen on facts | People need a known dashboard | You need resume of an agent job |
| Another chat | A paragraph API | The question is disposable | You need isolation or a veto |
| A hosted runtime | Job identity beside the database | Unrelated apps must reuse one kernel | You only have a weekend prototype |
Choose the warehouse if the missing object is a fact. Choose the BI app if the missing object is a known screen. Choose the chat if the sitting ends the question. Choose a runtime when data platform architecture is the actual review question.
Data management still matters for catalogs, retention, and owners of tables. That page does not replace this one. Table ownership is not job hosting. Name both owners.
NIST’s Cybersecurity Framework is the control language for who may touch which layer. If your data platform architecture cannot say who opens a job, you do not have an audit object.
Landscape: stores, runtimes, and shells
The 2026 landscape still sells stores as platforms. Data platform architecture for agents is a runtime sitting beside those stores.
- Operational databases. Source systems. Bind them. Do not copy them into the app.
- Warehouse and lake. Facts at rest. Necessary. Not sufficient.
- Agent runtime. The missing box on most slides. This is the missing box in this pillar.
- App shells. Generated or hand-built. Clients of the runtime.
If the product already exists and you only need a slot, stay with embed an AI data analyst. The embed is an app-layer client. It does not move the runtime into the iframe.
Apps keep the final action
Pattern note, not a review: a mole-style research desk and a ProjectValueLab-style valuation desk can share one runtime and one warehouse. Each app keeps domain rules and the final action. The shared pair is the runtime-plus-database, not the skin.
Do not add a second warehouse because the first one “does not feel like a platform.” Feeling is not a layer.
How to map the runtime before you buy a store
Use this sequence when a review asks for data platform architecture and someone has already booked a warehouse demo.
- Draw database versus runtime versus app. Empty boxes are allowed. Acceptance: every object has one layer.
- List last Friday’s agent demo as a Decision Job. Name input, sources, and artifact. Acceptance: a second person can reject the job.
- Point at where state lives today. Id, events, files. Acceptance: if they live in the chat, the runtime box is empty.
- Point at where secrets live. Acceptance: if they live in the page, isolation is empty.
- Refuse a store purchase as the fill-in. If the empty box is runtime, another lake does not complete the map.
- Only then score a store. Buy a warehouse if the missing object is a fact. Acceptance: the runtime box is already named.
If you fail step 3, stop the tour. The map is still a slide.
A one-page map you can keep
Write four lines: who owns state, who owns SQL, who owns UI, who owns secrets. That page is more honest than a twelve-box vendor map.
Desk sample: database vs runtime vs app (illustrative)
This desk composite is illustrative. It is not a customer result.
A team (illustrative) added a second warehouse because the agent demo “needed a platform.” The query got faster. The job still had no id. Data platform architecture was still a store slide. A second pass kept the first warehouse, added a runtime, and treated the question as a Decision Job. Eight source objects, forty-two named views, and eighty-eight dependency edges are illustrative magnitudes only. The database kept facts. The runtime kept the id. The app kept the veto button.
That is what data platform architecture looks like when the runtime is a layer, not a slogan.
Figure. Illustrative desk composite, not a customer result.
The bars are a desk composite. The database owns SQL and facts. The runtime owns state. The app owns UI. Do not read them as a measured uplift.
Scorecard: add a warehouse or host the job
Score the last architecture review. Data platform architecture is the “host the job” column when the gap is a runtime.
| Signal | Add a warehouse | Add another app | Host the runtime |
|---|---|---|---|
| Missing object is a fact table | Yes | No | No |
| Missing object is a job id | No | No | Yes |
| Secrets live in the page | A store will not fix this | An app will not fix this | Isolation on the runtime |
| You cannot resume after a kill | No | No | Yes |
| People want a known dashboard | Maybe later | Yes, as a client | The runtime still sits beside the database |
Add a warehouse if the facts are missing. Add an app if the screen is missing. Host the runtime when data platform architecture is the actual gap.
Building data infrastructure scores the cost of queues, resume, and audit. Read it after the map exists. Building without a map is how data platform architecture becomes a second warehouse.
Failure modes
Placement failures look like purchases.
Treating the database as the runtime
Query logs are not resume. Roles are not tenant walls for agent jobs. Data platform architecture that collapses those objects will fail the first kill test.
Treating the app as the runtime
A generated screen that stores checkpoints will be copied. The next app forks the trail. Data platform architecture puts state on the runtime, not in the page.
Buying a store to fill an empty runtime box
A new lake can be correct for facts and still leave the job without an id. Data platform architecture names the empty box before the purchase.
Those three failures are why this page exists. The hub on data infrastructure hosts the Decision Job. This page places the host beside the database.
Map the runtime before you add another warehouse
Draw database vs runtime vs app. Put state and artifacts on the runtime. This check uses only sources you authorize.
Commercial association: You do not need the workspace to complete the educational diagnosis on this page.
Open InfiniSynapseHow this page is sourced. William Zhu is cofounder of InfiniSynapse (GitHub @allwefantasy); InfiniSynapse on GitHub. Company self-description, not independent authority. No personal LinkedIn is published. Evaluation basis: We evaluate (hands-on) by reviewing whether data platform architecture named a runtime or only bought a store. Reviewed internally by analytics engineering · data platform · LLM security · editor. Editorial standards · corrections · publishing principles · About · Privacy · Terms · Contact zhuhl@infinisynapse.com. COI: InfiniSynapse sells an AI-native Data Agent; the banner is a commercial association. Fact-check: NIST AI RMF · AWS Machine Learning Lens · FTC · Google BigQuery · Python documentation · NIST Cybersecurity Framework. No external organization audited this page.
Frequently Asked Questions
Is a warehouse the same as this runtime?
Bottom line: No. A warehouse stores facts. Data platform architecture for agents places a runtime beside that store to host the Decision Job.
Can I skip the runtime if the database is fast?
Bottom line: No. Speed does not host identity or resume. Data platform architecture still needs the middle layer.
Does a generated app count as architecture?
Bottom line: It counts as the app layer. Data platform architecture still needs database and runtime boxes that the app does not own.
Do I need a new store before I draw the map?
Bottom line: No. Draw first. Buy a store only if the missing object is a fact. Data platform architecture starts with placement.
How do I test the map this week?
Bottom line: Kill last Friday’s job. If it cannot resume from the same id, the runtime box in your data platform architecture is empty.
Conclusion
Data platform architecture for agents is a runtime with isolation and resume, sitting beside the database. Adding another warehouse does not host the job. Draw three layers. Put state on the runtime. Keep facts on the database. Keep screens on the app.
InfiniSynapse describes itself on About. Privacy and Terms apply. If you later use the workspace, open InfiniSynapse only with authorized, sanitized inputs.