Minor architecture diagram improvements

deliahu · deliahu · commit 2e113bd12681 · 2021-12-20T17:22:53.000-08:00
diff --git a/docs/overview.md b/docs/overview.md
@@ -35,4 +35,4 @@ Visit the workload-specific documentation for more details.
 
 ## Architecture Diagram
 
-![](https://user-images.githubusercontent.com/4365343/121231768-ce62e200-c85e-11eb-84b1-3d5d4b999c12.png)
+![](https://user-images.githubusercontent.com/808475/146854233-505fb8c2-513d-4836-920b-5d447da95dee.png)
diff --git a/docs/workloads/async/async.md b/docs/workloads/async/async.md
@@ -26,4 +26,4 @@ You can fetch the result by making a GET request to the AsyncAPI endpoint with t
 
 The pool of workers running your containers autoscales based on the average number of messages in the queue and can scale down to 0 (if configured to do so).
 
-![](https://user-images.githubusercontent.com/4365343/121231833-e470a280-c85e-11eb-8be7-ad0a7cf9bce3.png)
+![](https://user-images.githubusercontent.com/808475/146854251-fed4235f-3627-4cd0-bc86-066272d7f138.png)
diff --git a/docs/workloads/batch/batch.md b/docs/workloads/batch/batch.md
@@ -25,4 +25,4 @@ After the worker pods have emptied the queue, the job is marked as complete, and
 
 You can make GET requests to the BatchAPI endpoint to get the status of the Job and metrics such as the number of batches completed and failed.
 
-![](https://user-images.githubusercontent.com/4365343/121231862-ed617400-c85e-11eb-96fb-84b10c211131.png)
+![](https://user-images.githubusercontent.com/808475/146854256-b5b0c9a0-1753-4018-bda2-5ebddd8a6ffa.png)
diff --git a/docs/workloads/realtime/realtime.md b/docs/workloads/realtime/realtime.md
@@ -20,4 +20,4 @@ When you deploy a Realtime API, Cortex initializes a pool of worker pods and att
 
 The proxy is responsible for receiving incoming requests, queueing them (if necessary), and forwarding them to your pod when it is ready. Autoscaling is based on aggregate in-flight request volume, which is published by the proxy sidecars.
 
-![](https://user-images.githubusercontent.com/4365343/121231921-fe11ea00-c85e-11eb-9813-6ee114f9a3fc.png)
+![](https://user-images.githubusercontent.com/808475/146854245-ed0fc153-d083-47d8-a7e2-ac5beb114ee6.png)
diff --git a/docs/workloads/task/task.md b/docs/workloads/task/task.md
@@ -18,4 +18,4 @@ Cortex will initialize a worker pod based on your API specification. After the w
 
 You can make GET requests to the Task API endpoint to retrieve the status of the Task.
 
-![](https://user-images.githubusercontent.com/4365343/121231738-c30fb680-c85e-11eb-886f-dc4d9bf3ef17.png)
+![](https://user-images.githubusercontent.com/808475/146854267-3785e8ee-4233-4473-a0db-37a5c5438fb4.png)

Original file line number	Diff line number	Diff line change
`@@ -35,4 +35,4 @@ Visit the workload-specific documentation for more details.`
`35`	`35`
`36`	`36`	`## Architecture Diagram`
`37`	`37`
`38`		`-![](https://user-images.githubusercontent.com/4365343/121231768-ce62e200-c85e-11eb-84b1-3d5d4b999c12.png)`
	`38`	`+![](https://user-images.githubusercontent.com/808475/146854233-505fb8c2-513d-4836-920b-5d447da95dee.png)`
Original file line number	Diff line number	Diff line change
`@@ -26,4 +26,4 @@ You can fetch the result by making a GET request to the AsyncAPI endpoint with t`
`26`	`26`
`27`	`27`	`The pool of workers running your containers autoscales based on the average number of messages in the queue and can scale down to 0 (if configured to do so).`
`28`	`28`
`29`		`-![](https://user-images.githubusercontent.com/4365343/121231833-e470a280-c85e-11eb-8be7-ad0a7cf9bce3.png)`
	`29`	`+![](https://user-images.githubusercontent.com/808475/146854251-fed4235f-3627-4cd0-bc86-066272d7f138.png)`
Original file line number	Diff line number	Diff line change
`@@ -25,4 +25,4 @@ After the worker pods have emptied the queue, the job is marked as complete, and`
`25`	`25`
`26`	`26`	`You can make GET requests to the BatchAPI endpoint to get the status of the Job and metrics such as the number of batches completed and failed.`
`27`	`27`
`28`		`-![](https://user-images.githubusercontent.com/4365343/121231862-ed617400-c85e-11eb-96fb-84b10c211131.png)`
	`28`	`+![](https://user-images.githubusercontent.com/808475/146854256-b5b0c9a0-1753-4018-bda2-5ebddd8a6ffa.png)`
Original file line number	Diff line number	Diff line change
`@@ -20,4 +20,4 @@ When you deploy a Realtime API, Cortex initializes a pool of worker pods and att`
`20`	`20`
`21`	`21`	`The proxy is responsible for receiving incoming requests, queueing them (if necessary), and forwarding them to your pod when it is ready. Autoscaling is based on aggregate in-flight request volume, which is published by the proxy sidecars.`
`22`	`22`
`23`		`-![](https://user-images.githubusercontent.com/4365343/121231921-fe11ea00-c85e-11eb-9813-6ee114f9a3fc.png)`
	`23`	`+![](https://user-images.githubusercontent.com/808475/146854245-ed0fc153-d083-47d8-a7e2-ac5beb114ee6.png)`
Original file line number	Diff line number	Diff line change
`@@ -18,4 +18,4 @@ Cortex will initialize a worker pod based on your API specification. After the w`
`18`	`18`
`19`	`19`	`You can make GET requests to the Task API endpoint to retrieve the status of the Task.`
`20`	`20`
`21`		`-![](https://user-images.githubusercontent.com/4365343/121231738-c30fb680-c85e-11eb-886f-dc4d9bf3ef17.png)`
	`21`	`+![](https://user-images.githubusercontent.com/808475/146854267-3785e8ee-4233-4473-a0db-37a5c5438fb4.png)`