<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Microservices on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/microservices/</link><description>Recent content in Microservices on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Wed, 01 Sep 2021 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/microservices/atom.xml" rel="self" type="application/rss+xml"/><item><title>Gateway Service on Kubernetes: APISIX</title><link>https://www.chenshaowen.com/en/blog/a-gateway-under-kubernetes-named-apisix.html</link><pubDate>Wed, 01 Sep 2021 00:00:00 +0000</pubDate><atom:modified>Wed, 01 Sep 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/a-gateway-under-kubernetes-named-apisix.html</guid><description>1. Comparing a Few Common Gateways Nginx, a reverse proxy with a modular design, written in C OpenResty, a web development platform built around Nginx that can parse and execute Lua scripts Kong, an application on top of OpenResty, an API gateway with API management and request proxying, using PostgreSQL for storage APISIX, which replaces Kong&amp;rsquo;s PostgreSQL with Etcd and is built on Nginx&amp;rsquo;s core libraries APISIX&amp;rsquo;s advantage lies in the API management and extensibility it provides, so the gateway no longer merely forwards traffic to services but can be configured and customized.</description><dc:creator>微信公众号</dc:creator><category>Kubernetes</category><category>APISIX</category><category>Microservices</category><category>Gateway</category><category>Operations</category><category>Proxy</category><category>Learning</category><category>Cloud Native</category></item><item><title>Etcd, Confd, and Nginx Service Discovery</title><link>https://www.chenshaowen.com/en/blog/service-discovery-etcd-confd-nginx.html</link><pubDate>Thu, 08 Feb 2018 14:51:16 +0000</pubDate><atom:modified>Thu, 08 Feb 2018 14:51:16 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/service-discovery-etcd-confd-nginx.html</guid><description>This post mainly explains why the service discovery feature is needed and compares several service discovery tools. It also puts service discovery with Etcd, Confd, and Nginx into practice on CentOS. 1. Service Registration and Discovery 1.1 Why Service Registration and Discovery Are Needed With the rise of microservices, a</description><dc:creator>微信公众号</dc:creator><category>Tools</category><category>Microservices</category><category>Etcd</category><category>Confd</category><category>Nginx</category><category>Service Discovery</category></item><item><title>API Rate Limiting for Backend Services</title><link>https://www.chenshaowen.com/en/blog/rate-limiting-of-api.html</link><pubDate>Thu, 11 Jan 2018 00:00:00 +0000</pubDate><atom:modified>Thu, 11 Jan 2018 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/rate-limiting-of-api.html</guid><description>1. Flow Control Caching, degradation, and rate limiting are common methods for protecting high-concurrency systems. Caching trades space for time and cuts the time spent on CPU and network calls; degradation protects the high availability of core services by delaying or refusing to handle non-core requests during peak periods; rate</description><dc:creator>微信公众号</dc:creator><category>API</category><category>Microservices</category><category>R&amp;D</category><category>Architecture</category><category>Rate Limiting</category></item></channel></rss>