# Chap 3. Infrastructure/platform design

Working on infrastructure has multiple responsibilities.

**Identify the gap** 

There are multiple gaps that the infrastructure could help to facilitate the workflow. More precisely,

* Research (If the DVC + MLFlow + Anaconda stack works for you, that's great. Metaflow provides similar features. Cloud integration is really important at Netflix's scale

  <https://news.ycombinator.com/item?id=21702831>)

  * GPU management: how to connect multiple servers
  * Data management: Data management system/data warehouse
  * Server maintenance
  * The Codebase for research: the pre-processing/post-processing pipeline(DAG), the training pipeline,  visualization&#x20;
  * Mini app: inference pipeline for testing (MVP)
  * Model register(Model management): a platform to track models with different functionalities
* Product:
  * Deployment&#x20;
  * Dashboard
  * The Codebase for the app
  * Monitor mechanism/ health-check
  * User activity analysis
* Commercial:
  * A platform to track record and transfer money
  * A platform to interact with customers
* Others/internal tools:
  * internal wiki
  * internal StackOverflow
  * internal compiler

**Build the platforms**

* design reviews
* code and test

**Maintain the platforms**

* collect feedbacks from each site on period
* fix the bug and add the patch
* upgrade the versions of dependencies if needed
* add new features if requested


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://lwang010.gitbook.io/longw/mlops/chap-6.-team-infra.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.