# Systems: about design

## Patterns

* [10 design patterns every software architect must know](https://ravindraelicherla.medium.com/10-design-patterns-every-software-architect-must-know-b33237bc01c2)

## Microservices

* [A lot about Microservices](https://kgoralski.gitbook.io/wiki/microservices)
* [Multi-Runtime Microservices Architecture](https://www.infoq.com/articles/multi-runtime-microservice-architecture/)
* [Microservices & Conway's Law](https://twitter.com/allenholub/status/1279472949976797187)

## Event driven architecture

* [How event-driven architecture solves modern web app problems](https://stackoverflow.blog/2020/03/16/how-event-driven-architecture-solves-modern-web-app-problems/)
* [Webhooks: the building blocks of an event driven architecture](https://thenewstack.io/webhooks-the-building-blocks-of-an-event-driven-architecture/)


---

# 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://arielgerardorios.gitbook.io/personal-wiki/systems_design.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.