マイクロサービス (Japanese Wikipedia)

Analysis of information sources in references of the Wikipedia article "マイクロサービス" in Japanese language version.

refsWebsite

Global rank Japanese rank

3istio.io

low place

2researchgate.net

120^th place

616^th place

2icsa-conferences.org

low place

2web.archive.org

1^st place

2doi.org

2^nd place

6^th place

2martinfowler.com

8,817^th place

low place

1microservices.io

low place

1worldcat.org

5^th place

19^th place

1microservices-book.com

low place

1vanilla-java.github.io

low place

1microsoft.com

153^rd place

260^th place

1amazon.co.jp

554^th place

50^th place

1envoyproxy.io

low place

1amazon.com

105^th place

738^th place

amazon.co.jp

Lucas Krause. Microservices: Patterns and Applications. ASIN B00VJ3NP4A

amazon.com

aws.amazon.com

In the following diagram, a sidecar runs alongside each container in your application to provide its proxying logic, syncing each of their unique configurations from the App Mesh control plane. AWS Compute Blog (2019) "Learning AWS App Mesh"

doi.org

Chen, Lianping; Ali Babar, Muhammad (2014). Towards an Evidence-Based Understanding of Emergence of Architecture through Continuous Refactoring in Agile Software Development. The 11th Working IEEE/IFIP Conference on Software Architecture(WICSA 2014). IEEE. doi:10.1109/WICSA.2014.45。
Balalaie, Armin; Heydarnoori, Abbas; Jamshidi, Pooyan (2016-05). “Microservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture”. IEEE Software 33 (3): 42–52. doi:10.1109/ms.2016.64. ISSN 0740-7459.

envoyproxy.io

blog.envoyproxy.io

Envoy is the data plane. Matt Klein (2017). "Service mesh data plane vs. control plane"

icsa-conferences.org

Chen, Lianping (2018). Microservices: Architecting for Continuous Delivery and DevOps. The IEEE International Conference on Software Architecture (ICSA 2018). IEEE.
Chen, Lianping (2018). Microservices: Architecting for Continuous Delivery and DevOps. The IEEE International Conference on Software Architecture (ICSA 2018). IEEE.

istio.io

The term service mesh is used to describe the network of microservices that make up such applications and the interactions between them. Istio - Docs - What is Istio
Its requirements can include discovery, load balancing, failure recovery, metrics, and monitoring. Istio - Docs - What is Istio
A service mesh also often has more complex operational requirements, like A/B testing, canary rollouts, rate limiting, access control, and end-to-end authentication. Istio - Docs - What is Istio

martinfowler.com

James Lewis. “Microservices”. martinfowler.com. 2018年12月6日閲覧。
Martin Fowler. “Microservices”. 14 February 2018時点のオリジナルよりアーカイブ。2018年1月2日閲覧。

microservices-book.com

Wolff, Eberhard (2016-10-12). Microservices: Flexible Software Architectures. ISBN 978-0134602417. http://microservices-book.com

microservices.io

Richardson. “Microservice architecture pattern” (英語). microservices.io. 2017年3月19日閲覧。

microsoft.com

docs.microsoft.com

“Backends For Frontends Pattern”. Microsoft Azure Cloud Design Patterns. Microsoft. 2018年1月2日閲覧。

researchgate.net

Chen, Lianping (2018). Microservices: Architecting for Continuous Delivery and DevOps. The IEEE International Conference on Software Architecture (ICSA 2018). IEEE.
Chen, Lianping (2018). Microservices: Architecting for Continuous Delivery and DevOps. The IEEE International Conference on Software Architecture (ICSA 2018). IEEE.

vanilla-java.github.io

“Micro-services for performance”. Vanilla Java (2016年3月22日). 2017年3月19日閲覧。

web.archive.org

Chen, Lianping; Ali Babar, Muhammad (2014). Towards an Evidence-Based Understanding of Emergence of Architecture through Continuous Refactoring in Agile Software Development. The 11th Working IEEE/IFIP Conference on Software Architecture(WICSA 2014). IEEE. doi:10.1109/WICSA.2014.45。
Martin Fowler. “Microservices”. 14 February 2018時点のオリジナルよりアーカイブ。2018年1月2日閲覧。

worldcat.org

search.worldcat.org

Balalaie, Armin; Heydarnoori, Abbas; Jamshidi, Pooyan (2016-05). “Microservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture”. IEEE Software 33 (3): 42–52. doi:10.1109/ms.2016.64. ISSN 0740-7459.