> For the complete documentation index, see [llms.txt](https://tommyyang.gitbook.io/javainterview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tommyyang.gitbook.io/javainterview/architecture.md).

# 架构篇

## UML图

分享项目设计中需要的类图、对象图、时序图等。\
[UML图总结](/javainterview/architecture/uml.md)

## 设计模式

分享实际项目中的设计模式经验。\
[设计模式](/javainterview/architecture/design_patterns.md)

## 分布式

### 分布式一致性问题

1. 分布式一致性理论
   * [2PC-3PC](/javainterview/architecture/2pc-3pc.md)
   * Paxos 理论
   * CAP 理论
2. Raft协议(etcd)
3. zookeeper在分布式中的应用
4. 金融方面： 任务补偿，最终一致性

## 微服务

## 大型网站架构

## 流行数据库架构

* [MySQL](/javainterview/architecture/mysql.md)
* [Redis](/javainterview/architecture/redis.md)
* [ElasticSearch](/javainterview/architecture/elasticsearch.md)
* MongoDB

## 大数据

* Hadoop
* Hive
* Spark

## 推荐系统

* [推荐系统](https://github.com/joyang1/JavaInterview/blob/master/architecture/recommend_system.md)


---

# 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 dynamically by asking a question.

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

```
GET https://tommyyang.gitbook.io/javainterview/architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.