> For the complete documentation index, see [llms.txt](https://www.opscompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opscompendium.com/mlops/literature.md).

# MLOps Literature

1. [12 Factors](https://12factor.net/) - The Twelve-Factor App is a methodology for building scalable and portable SaaS applications. It emphasizes best practices like maintaining a single codebase, isolating dependencies, storing configuration in the environment, treating services as replaceable resources, and enabling fast, stateless, and resilient deployments across consistent environments.
2. [**Designing data-intensive applications reliable maintainable**](https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321)
   1. [**medium**](https://medium.com/@m_mcclarty/tech-book-talk-designing-data-intensive-applications-eb4908f2f6d6)
3. [**Google SRE**](https://landing.google.com/sre/books/)
   1. [**Site Reliability Engineering**](https://www.amazon.com/dp/149192912X?psc=1\&pf_rd_p=0c07d3ef-dd9a-4ce4-8daa-7b9b90db3048\&pf_rd_r=F4QGSBSPA6DJJCX10WXK\&pd_rd_wg=RfKM8\&pd_rd_i=149192912X\&pd_rd_w=khBYM\&pd_rd_r=5bd80e38-7a30-41bb-ae0e-25a91dd1cb3d\&ref_=pd_luc_rh_crh_rh_sbs_sem_01_03_t_ttl_lh)
   2. [**Site Reliability Workbook**](https://www.amazon.com/Site-Reliability-Workbook-Practical-Implement/dp/1492029505/ref=sr_1_1?dchild=1\&keywords=The+Site+Reliability+Workbook\&link_code=qs\&qid=1598257953\&sr=8-1\&tag=amznsearchff-20)
4. [**Designing Distributed systems patterns paradigms**](https://www.amazon.com/Designing-Distributed-Systems-Patterns-Paradigms/dp/1491983647)
5. [**Building Microservices: Designing Fine-Grained Systems**](https://www.amazon.com/dp/1491950358/?coliid=I1H3OSVXC7XRBL\&colid=300M9JC4311P3\&psc=0\&ref_=lv_ov_lig_dp_it)
6. [**Jez Humble**](https://www.amazon.com/Jez-Humble/e/B003SNGS8E/ref=dp_byline_cont_pop_book_2)
   1. [**Accelerate software performing organizations**](https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339/ref=tmm_pap_swatch_0?_encoding=UTF8\&qid=\&sr=)
   2. [**DevOps Handbook.**](https://www.amazon.com/DevOps-Handbook-World-Class-Reliability-Organizations/dp/1942788002/ref=tmm_pap_swatch_0?_encoding=UTF8\&qid=\&sr=)
   3. [**Continuous delivery deployment**](https://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley-dp-0321601912/dp/0321601912/ref=mt_other?_encoding=UTF8\&me=\&qid=)
   4. **Lean Enterprise**
7. [**Clean code**](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882) **(java) first chapters are good**
8. [**Clean code in Python**](https://www.packtpub.com/product/clean-code-in-python/9781788835831)
   1. [**Medium**](https://medium.com/@m_mcclarty/tech-book-talk-clean-code-in-python-aa2c92c6564f)
   2. [**git**](https://github.com/zedr/clean-code-python)
9. [**Domain-Driven Design**](https://www.amazon.com/Domain-Driven-Design-Reference-Definitions-Summaries/dp/1457501198/ref=pd_cart_crc_cko_mrai_1_1/146-7136232-7217867?_encoding=UTF8\&pd_rd_i=1457501198\&pd_rd_r=e0b19e54-c0c3-4ad1-abd0-eff99f815aee\&pd_rd_w=TP8KJ\&pd_rd_wg=ompBT\&pf_rd_p=77f3805b-bff9-40ee-9688-bcdb2cd9e197\&pf_rd_r=1WF281MJHVQYG506PTRX\&psc=1\&refRID=1WF281MJHVQYG506PTRX)
10. [**The complete python course**](https://www.packtpub.com/product/the-complete-python-course-video/9781839217289)
11. [**pyVideo**](https://pyvideo.org/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opscompendium.com/mlops/literature.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.