This is an automated email from the ASF dual-hosted git repository.
juzhiyuan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git
The following commit(s) were added to refs/heads/master by this push:
new 3eade359f89 docs: Added cover images for blog (#1387)
3eade359f89 is described below
commit 3eade359f89d1c562dc17206748278510ab71e86
Author: Bhavya Tewari <[email protected]>
AuthorDate: Thu Nov 3 13:32:33 2022 +0530
docs: Added cover images for blog (#1387)
---
blog/en/blog/2022/08/17/backend-for-frontend-demo.md | 1 +
blog/en/blog/2022/09/23/build-event-driven-api.md | 1 +
2 files changed, 2 insertions(+)
diff --git a/blog/en/blog/2022/08/17/backend-for-frontend-demo.md
b/blog/en/blog/2022/08/17/backend-for-frontend-demo.md
index 7aef45c0626..189cf4b0e06 100644
--- a/blog/en/blog/2022/08/17/backend-for-frontend-demo.md
+++ b/blog/en/blog/2022/08/17/backend-for-frontend-demo.md
@@ -12,6 +12,7 @@ keywords:
- Mciroservices
description: The Backend-For-Frontend pattern describes how to return
different data for each client in a microservices architecture. This article
goes through the code required to implement the different possible
implementations.
tags: [Case Studies]
+image: https://static.apiseven.com/2022/11/03/63634494405e7.png
---
> This article describes a demo code to implement the Backend-For-Frontend
> pattern.
diff --git a/blog/en/blog/2022/09/23/build-event-driven-api.md
b/blog/en/blog/2022/09/23/build-event-driven-api.md
index b89801c8550..5701af6ac98 100644
--- a/blog/en/blog/2022/09/23/build-event-driven-api.md
+++ b/blog/en/blog/2022/09/23/build-event-driven-api.md
@@ -14,6 +14,7 @@ keywords:
- Serverless
description: This blog post explores how to build event-driven API Services
using these 3 well-known patterns to build a highly scalable and distributed
system.
tags: [Case Studies]
+image: https://static.apiseven.com/2022/11/01/63612aab60c8d.png
---
> This blog post explores how to build event-driven API Services using these 3
> well-known patterns to build a highly scalable and distributed system. We
> will break down each concept and understand the role of each in our
> particular approach.
