Adds ByteByteGo guides and links (#106)

This PR adds all the guides from [Visual
Guides](https://bytebytego.com/guides/) section on bytebytego to the
repository with proper links.

- [x] Markdown files for guides and categories are placed inside
`data/guides` and `data/categories`
- [x] Guide links in readme are auto-generated using
`scripts/readme.ts`. Everytime you run the script `npm run
update-readme`, it reads the categories and guides from the above
mentioned folders, generate production links for guides and categories
and populate the table of content in the readme. This ensures that any
future guides and categories will automatically get added to the readme.
- [x] Sorting inside the readme matches the actual category and guides
sorting on production

data/guides/evolution-of-uber's-api-layer.md

@@ -0,0 +1,22 @@
+---
+title: Evolution of Uber's API Layer
+description: Learn about the evolution of Uber's API layer.
+image: 'https://assets.bytebytego.com/diagrams/0397-uber-api-layer.png'
+createdAt: '2024-03-14'
+draft: false
+categories:
+  - real-world-case-studies
+tags:
+  - API Gateway
+  - Microservices
+---
+
+![](https://assets.bytebytego.com/diagrams/0397-uber-api-layer.png)
+
+Uber’s API gateway went through 3 main stages.
+
+First gen: the organic evolution. Uber's architecture in 2014 would have two key services: dispatch and API. A dispatch service connects a rider with a driver, while an API service stores the long-term data of users and trips.
+
+Second gen: the all-encompassing gateway. Uber adopted a microservice architecture very early on. By 2019, Uber's products were powered by 2,200+ microservices as a result of this architectural decision.
+
+Third gen: self-service, decentralized, and layered. As of early 2018, Uber had completely new business lines and numerous new applications. Freight, ATG, Elevate, groceries, and more are among the growing business lines. With a new set of goals comes the third generation.