[B! architecture] krrrrã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

krrrr id:krrrr

architectureã«é–¢ã™ã‚‹krrrrã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (13)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

Event-Driven Architectureã«ãŠã‘ã‚‹Choreographyã¨Orchestration | CyberAgent Developers Blog
ã¯ã˜ã‚ã« ã“ã‚“ã«ã¡ã¯ã€AIäº‹æ¥æœ¬éƒ¨ã®ä¼Šè—¤(@tsutsun17)ã§ã™ã€‚å…ˆæ—¥ã€ãƒ©ã‚¹ãƒ™ã‚¬ã‚¹ã§é–‹å‚¬ã•ã‚ŒãŸAWS re:invent 2022ã«ç¾åœ°å‚åŠ ã—ã¦ãã¾ã—ãŸã€‚ AIäº‹æ¥æœ¬éƒ¨ã§ã¯ä¾‹å¹´ã€ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢æ•°äººãŒç¾åœ°å‚åŠ ã—ã¦ç†±é‡ã¨å¦ã³ã‚’å¾—ã‚‹ã“ã¨ãŒã§ãã‚‹ç’°å¢ƒãŒã‚ã‚Šã¾ã—ãŸã€‚ç›´è¿‘2å¹´ã¯ä¸–ã®æƒ…å‹¢ã‚‚ã‚ã‚Šç¾åœ°å‚åŠ ã‚’æŽ§ãˆã¦ã„ã¾ã—ãŸãŒã€ä»Šå¹´ã¯ç¾åœ°å‚åŠ ã§ãã¾ã—ãŸã€‚ä»Šå›žã¯ã€å‚åŠ ã—ãŸã‚»ãƒƒã‚·ãƒ§ãƒ³ã®ä¸ã§ç‰¹ã«é¢ç™½ã‹ã£ãŸã‚»ãƒƒã‚·ãƒ§ãƒ³ã®ä¸€éƒ¨ã«ã¤ã„ã¦ã€è€ƒå¯Ÿã‚„é–‹ç™ºã—ã¦ã„ã‚‹ãƒ—ãƒãƒ€ã‚¯ãƒˆã®ãŠè©±ã‚‚å«ã‚ãªãŒã‚‰ã”ç´¹ä»‹ã—ãŸã„ã¨æ€ã„ã¾ã™ã€‚ ã‚»ãƒƒã‚·ãƒ§ãƒ³ã®æ¦‚è¦ ã¾ãšã¯ã€ã‚»ãƒƒã‚·ãƒ§ãƒ³ã®æ¦‚è¦ã«ã¤ã„ã¦ã”ç´¹ä»‹ã—ã¾ã™ã€‚ Building next-gen applications with event-driven architectures Event-driven architectures can solve many difficult probl ems in m
krrrr 2022/12/25
event

architecture

microservices

serverless

aws
ãƒªãƒ³ã‚¯
Write-Behind Logging
krrrr 2021/07/06
architecture

è«–æ–‡
ãƒªãƒ³ã‚¯
Catalog of Patterns of Distributed Systems
Distributed systems provide a particular challenge to program. They often require us to have multiple copies of data, which need to keep synchronized. Yet we cannot rely on processing nodes working reliably, and network delays can easily lead to inconsistencies. Despite this, many organizations rely on a range of core distributed software handling data storage, messaging, system management, and co
krrrr 2021/07/04
architecture

Pattern

server
ãƒªãƒ³ã‚¯
ãƒžã‚¤ã‚¯ãƒã‚µãƒ¼ãƒ“ã‚¹ã®ãŸã‚ã®åˆ†æ•£ãƒ‡ãƒ¼ã‚¿ ã€œ ã‚¤ãƒ™ãƒ³ãƒˆã‚½ãƒ¼ã‚·ãƒ³ã‚° vs ãƒã‚§ãƒ³ã‚¸ãƒ‡ãƒ¼ã‚¿ã‚ãƒ£ãƒ—ãƒãƒ£ - èµ¤å¸½ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ãƒ–ãƒã‚°
ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³ã®ãŸã‚ã®ãƒŸãƒ‰ãƒ«ã‚¦ã‚§ã‚¢è£½å“ã®ãƒ†ã‚¯ãƒ‹ã‚«ãƒ«ã‚µãƒãƒ¼ãƒˆã‚’æ‹…å½“ã—ã¦ã„ã‚‹å±±ä¸‹ã§ã™ã€‚ ä»Šå›žã¯ ãƒ¬ãƒƒãƒ‰ãƒãƒƒãƒˆã®ã‚·ãƒ‹ã‚¢ã‚¢ãƒ¼ã‚ãƒ†ã‚¯ãƒˆã§ã‚ã‚‹ Eric Murphy ã•ã‚“ã«ã‚ˆã‚‹ã€Œãƒžã‚¤ã‚¯ãƒã‚µãƒ¼ãƒ“ã‚¹ã®ãŸã‚ã®åˆ†æ•£ãƒ‡ãƒ¼ã‚¿ ã€œ ã‚¤ãƒ™ãƒ³ãƒˆã‚½ãƒ¼ã‚·ãƒ³ã‚° vs ãƒã‚§ãƒ³ã‚¸ãƒ‡ãƒ¼ã‚¿ã‚ãƒ£ãƒ—ãƒãƒ£(CDC)ã€ã®ç¿»è¨³è¨˜äº‹ã§ã™ã€‚ã“ã®è¨˜äº‹ã§ã¯ã€ã‚¤ãƒ™ãƒ³ãƒˆã‚½ãƒ¼ã‚·ãƒ³ã‚°ã€CDCã€CDC + Outboxãƒ‘ã‚¿ãƒ¼ãƒ³ã€CQRSã‚’ãã‚Œãžã‚Œç°¡å˜ã«èª¬æ˜Žã—ãªãŒã‚‰ã€ãã‚Œã‚‰ã®ç‰¹æ€§ã®é•ã„ã‚’æ¯”è¼ƒã—ã¾ã™ã€‚ã¾ãŸã€ã‚¤ãƒ™ãƒ³ãƒˆã‚½ãƒ¼ã‚·ãƒ³ã‚°ã¨CQRSã®ç°¡æ˜“ãªèª¬æ˜ŽãŒãªã•ã‚Œã¦ã„ã‚‹ä»–ã€ã‚ã¾ã‚Šæ˜Žç¢ºã«èªžã‚‰ã‚Œã‚‹ã“ã¨ãŒå°‘ãªã„ã‚‚ã®ã®ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã®è¨è¨ˆã«å¤§ããªå½±éŸ¿ã‚’ãŠã‚ˆã¼ã™ãƒ‰ãƒ¡ã‚¤ãƒ³ã‚¤ãƒ™ãƒ³ãƒˆã¨ãƒã‚§ãƒ³ã‚¸ã‚¤ãƒ™ãƒ³ãƒˆã®é•ã„ã«ã‚‚è§¦ã‚Œã‚‰ã‚Œã¦ã„ã¾ã™ã€‚ [åŽŸæ–‡] Distributed Data for Microservices â€” Event Sourcing vs. Change Data Captur
krrrr 2020/03/08
CQRS

event

microservices

architecture

Debezium
ãƒªãƒ³ã‚¯
åˆ†æ•£ã‚·ã‚¹ãƒ†ãƒ ã§ã®ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯ã®å›žé¿
é‡å¤§ãªéšœå®³ãŒç™ºç”Ÿã—ãŸã‚µãƒ¼ãƒ“ã‚¹ã‹ã‚‰ã¯ã€æœ‰ç”¨ãªçµæžœã‚’å¾—ã‚‹ã“ã¨ãŒã§ããªããªã‚Šã¾ã™ã€‚ãŸã¨ãˆã°ã€e ã‚³ãƒžãƒ¼ã‚¹ã‚¦ã‚§ãƒ–ã‚µã‚¤ãƒˆã§ã¯ã€è£½å“æƒ…å ±ã®ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚¯ã‚¨ãƒªãŒå¤±æ•—ã™ã‚‹ã¨ã€ã‚¦ã‚§ãƒ–ã‚µã‚¤ãƒˆã¯è£½å“ãƒšãƒ¼ã‚¸ã‚’æ£å¸¸ã«è¡¨ç¤ºã§ãã¾ã›ã‚“ã€‚Amazon ã®ã‚µãƒ¼ãƒ“ã‚¹ã¯ã€ä¿¡é ¼æ€§ã‚’é«˜ã‚ã‚‹ãŸã‚ã«ã€é‡å¤§ãªéšœå®³ã®å¤§éƒ¨åˆ†ã‚’å‡¦ç†ã™ã‚‹å¿…è¦ãŒã‚ã‚Šã¾ã™ã€‚é‡å¤§ãªéšœå®³ã‚’å‡¦ç†ã™ã‚‹ãŸã‚ã®æˆ¦ç•¥ã«ã¯ã€å¤§ããæ¬¡ã® 4 ã¤ã®ã‚«ãƒ†ã‚´ãƒªãƒ¼ã«åˆ†ã‹ã‚Œã¾ã™ã€‚ â€¢ å†è©¦è¡Œ: ã™ãã«ã€ã¾ãŸã¯å°‘ã—é…ã‚Œã¦ã€å¤±æ•—ã—ãŸã‚¢ã‚¯ãƒ†ã‚£ãƒ“ãƒ†ã‚£ã‚’å†åº¦å®Ÿè¡Œã—ã¾ã™ã€‚ â€¢ ç©æ¥µçš„ãªå†è©¦è¡Œ: ã‚¢ã‚¯ãƒ†ã‚£ãƒ“ãƒ†ã‚£ã‚’ä¸¦è¡Œã—ã¦è¤‡æ•°å›žå®Ÿè¡Œã—ã€æœ€åˆã®ã‚¢ã‚¯ãƒ†ã‚£ãƒ“ãƒ†ã‚£ã‚’ä½¿ç”¨ã—ã¦çµ‚äº†ã—ã¾ã™ã€‚ â€¢ ãƒ•ã‚§ã‚¤ãƒ«ã‚ªãƒ¼ãƒãƒ¼: ã‚¨ãƒ³ãƒ‰ãƒã‚¤ãƒ³ãƒˆã®åˆ¥ã®ã‚³ãƒ”ãƒ¼ã«å¯¾ã—ã¦ã‚¢ã‚¯ãƒ†ã‚£ãƒ“ãƒ†ã‚£ã‚’å†åº¦å®Ÿè¡Œã™ã‚‹ã‹ã€ã§ãã‚Œã°ã‚¢ã‚¯ãƒ†ã‚£ãƒ“ãƒ†ã‚£ã®è¤‡æ•°ã®ä¸¦è¡Œã‚³ãƒ”ãƒ¼ã‚’å®Ÿè¡Œã—ã¦ã€ãã‚Œã‚‰ã®å°‘ãªãã¨ã‚‚ 1 ã¤ãŒæˆåŠŸã™ã‚‹ç¢ºçŽ‡ã‚’ä¸Šã’ã¾ã™ã€‚ â€¢ ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯: ç•°ãªã‚‹ãƒ¡ã‚«ãƒ‹ã‚º
krrrr 2020/01/05
ã‚ˆã

aws

architecture
ãƒªãƒ³ã‚¯
Documenting Architecture Decisions
Context Architecture for agile projects has to be described and defined differently. Not all decisions will be made at once, nor will all of them be done when the project begins. Agile methods are not opposed to documentation, only to valueless documentation. Documents that assist the team itself can have value, but only if they are kept up to date. Large documents are never kept up to date. Small
krrrr 2018/11/26
architecture

Tools
ãƒªãƒ³ã‚¯
EIP - Java EEå‹‰å¼·ä¼š
Menu Top JavaEEå‹‰å¼·ä¼š å‚åŠ ã™ã‚‹ã«ã¯ FAQ MakingSenseofStreamProcessing MicroservicesVsSOA ModernJavaEEDesignPatterns BSA EIP DSL DDD è°äº‹éŒ² æœ€æ–°ã®20ä»¶2023-11-24 MicroservicesVsSOA/The World of Service-Based Architectures 2020-11-14 DDD/Knowledge-Rich Design MakingSenseofStreamProcessing/Example Implementing Twitter 2020-10-28 EIP/Aggregator 2019-12-18 EIP/Publish-Subscribe Channel 2018-06-10 FrontPage 2017-07-08 Ma
krrrr 2018/08/02
java

ddd

architecture
ãƒªãƒ³ã‚¯
ç¶šã€…ãƒ»ãƒªãƒˆãƒ©ã‚¤ã¨å†ªç‰æ€§ã®ãƒ‡ã‚¶ã‚¤ãƒ³ãƒ‘ã‚¿ãƒ¼ãƒ³ - ã‚ã‚‰ã‚†ã‚‹æ“ä½œã‚’å†ªç‰ã«ã™ã‚‹æ–¹æ³• - Blog by Sadayuki Furuhashi
ã„ã¤ã‚‚å¿ƒã«å†ªç‰æ€§ã€‚å¤æ©‹ã§ã™ã€‚ ãƒªãƒˆãƒ©ã‚¤ã¨å†ªç‰æ€§ã®ãƒ‡ã‚¶ã‚¤ãƒ³ãƒ‘ã‚¿ãƒ¼ãƒ³ã®å®Œçµç·¨ã§ã™ã€‚ ã ã„ã¶é–“ãŒç©ºã„ã¦ã—ã¾ã„ã¾ã—ãŸãŒï¼ æœ€å¾Œã«å†ªç‰æ€§ã‚’å®Ÿè£…ã™ã‚‹æ±Žç”¨çš„ãªå®Ÿè£…æ‰‹æ³•ã«ã¤ã„ã¦ã¾ã¨ã‚ã¦ã„ãã¾ã™ã€‚ ãƒ‘ã‚¿ãƒ¼ãƒ³ï¼–ï¼šæ“ä½œãƒã‚°ã¨ãƒªã‚¯ã‚¨ã‚¹ãƒˆIDã§UPDATEã‚’å†ªç‰ã«ã™ã‚‹ åŒã˜IDã§è˜åˆ¥ã•ã‚Œã‚‹å€¤ãŒUPDATEã•ã‚Œã‚‹å ´åˆã€ã¤ã¾ã‚Šmutableã§ã‚ã‚‹å€¤ã®ç®¡ç†ã¯ã€ä¸€èˆ¬ã«å†ªç‰ã«è¡Œã†ã®ãŒé›£ã—ã„ã€‚ ä¾‹ãˆã°ã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã”ã¨ã«ã€Œæœ€å¾Œã«è³¼å…¥ã—ãŸã‚¢ã‚¤ãƒ†ãƒ ã€ã‚’æ›´æ–°ã™ã‚‹æ“ä½œã‚’è€ƒãˆã¦ã¿ã‚‹ã¨ï¼š 1. ãƒ¦ãƒ¼ã‚¶ãƒ¼AãŒæœ€å¾Œã«è³¼å…¥ã—ãŸã‚¢ã‚¤ãƒ†ãƒ ã‚’ã‚¢ã‚¤ãƒ†ãƒ 1ã«å¤‰æ›´ã™ã‚‹ï¼ˆUPDATEï¼‰ 2. ãƒ¦ãƒ¼ã‚¶ãƒ¼AãŒæœ€å¾Œã«è³¼å…¥ã—ãŸã‚¢ã‚¤ãƒ†ãƒ ã‚’ã‚¢ã‚¤ãƒ†ãƒ 2ã«å¤‰æ›´ã™ã‚‹ï¼ˆUPDATEï¼‰ ã“ã®æ“ä½œã«ä½•ã®å¯¾ç–ã‚‚ãªããƒªãƒˆãƒ©ã‚¤ã‚’å®Ÿè£…ã—ãŸå ´åˆã€å¾Œç¶šã®UPDATEå‡¦ç†ã®çµæžœã‚’å¤ã„å†…å®¹ã§ä¸Šæ›¸ãã—ã¦ã—ã¾ã†å¯èƒ½æ€§ãŒã‚ã‚‹ï¼š 1. ãƒ¦ãƒ¼ã‚¶ãƒ¼AãŒæœ€å¾Œã«è³¼å…¥ã—ãŸã‚¢ã‚¤ãƒ†ãƒ ã‚’ã‚¢ã‚¤ãƒ†ãƒ 1ã«å¤‰æ›´ã™ã‚‹ï¼ˆUPDATEï¼‰â†’
krrrr 2017/08/10
ã‚ã¨ã§èªã‚€

architecture

å†ªç‰æ€§

retry
ãƒªãƒ³ã‚¯
Serverless Architectures
Serverless architectures are application designs that incorporate third-party â€œBackend as a Serviceâ€ (BaaS) services, and/or that include custom code run in managed, ephemeral containers on a â€œFunctions as a Serviceâ€ (FaaS) platform. By using these ideas, and related ones like single-page applications, such architectures remove much of the need for a traditional always-on server component. Serverl
krrrr 2016/09/06
architecture

serverless
ãƒªãƒ³ã‚¯
Scalability, Availability & Stability Patterns
This document provides an overview of patterns for scalability, availability, and stability in distributed systems. It discusses general recommendations like immutability and referential transparency. It covers scalability trade-offs around performance vs scalability, latency vs throughput, and availability vs consistency. It then describes various patterns for scalability including managing state
krrrr 2015/10/18
scalability

architecture
ãƒªãƒ³ã‚¯
Handling five billion sessions a day â€“ in real time
Since we first released Answers seven months ago, weâ€™ve been thrilled by tremendous adoption from the mobile community. We now see about five billion sessions per day, and growing. Hundreds of millions of devices send millions of events every second to the Answers endpoint. During the time that it took you to read to here, the Answers back-end will have received and processed about 10,000,000 anal
krrrr 2015/05/08
twitter

architecture
ãƒªãƒ³ã‚¯
ãƒ‰ãƒ¡ã‚¤ãƒ³é§†å‹•è¨è¨ˆã¨ã‚ªãƒ‹ã‚ªãƒ³ã‚¢ãƒ¼ã‚ãƒ†ã‚¯ãƒãƒ£
Spring Bootã«ã‚ˆã‚‹APIãƒãƒƒã‚¯ã‚¨ãƒ³ãƒ‰æ§‹ç¯‰å®Ÿè·µã‚¬ã‚¤ãƒ‰ ç¬¬2ç‰ˆ ä½•åƒäººã‚‚ã®é–‹ç™ºè€…ãŒã€InfoQã®ãƒŸãƒ‹ãƒ–ãƒƒã‚¯ã€ŒPractical Guide to Building an API Back End with Spring Bootã€ã‹ã‚‰ã€Spring Bootã‚’ä½¿ã£ãŸREST APIæ§‹ç¯‰ã®åŸºç¤Žã‚’å¦ã‚“ã ã€‚ã“ã®æœ¬ã§ã¯ã€å‡ºç‰ˆæ™‚ã«æ–°ã—ããƒªãƒªãƒ¼ã‚¹ã•ã‚ŒãŸãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ã‚ã‚‹ Spring Boot 2 ã‚’ä½¿ç”¨ã—ã¦ã„ã‚‹ã€‚ã—ã‹ã—ã€Spring Boot3ãŒæœ€è¿‘ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã€é‡è¦ãªå¤‰...
krrrr 2015/02/24
architecture
ãƒªãƒ³ã‚¯
The Onion Architecture : part 1
Programming with Palermo Jeffrey Palermo, Microsoft MVP, Author, Speaker, Clear Measure Chief Architect, Azure DevOps Expert This is part 1.Â part 2. part 3. part 4. Â My feed (rss). Iâ€™ve spoken several times about a specific type of architecture I call â€œOnion Architectureâ€.Â Iâ€™ve found that it leads to more maintainable applications since it em phasizes separation of concerns throughout the system.
krrrr 2015/02/24
architecture

Pattern
ãƒªãƒ³ã‚¯
1