Files

T

Antigravity Agent f8b21af4be Wiki cleanup: error-doc removal, dedup merge, link normalization

10_Wiki/Topics 대규모 정리:
- 오류 캡처/미완성 stub 문서 227개 제거
- 교차폴더 중복 43클러스터 병합 (63파일 → redirect)
- 링크명 정규화: 깨진 링크 수정·redirect 직결·개념 매핑 ~2,400건
- 카테고리 MOC 6개 신규 생성
- Graph 섹션 미해결 related-keyword 링크 10,058건 제거

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-20 23:52:15 +09:00

5.0 KiB

Raw Blame History

id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack

title

Enterprise Service Bus

매 한 줄

"매 ESB = SOA 시대 의 integration backbone — 매 2026 의 legacy + event mesh 의 hybrid". 매 hub-and-spoke 의 anti-pattern 회피 위한 message-bus pattern. 매 modern 의 Kafka + service mesh + iPaaS (MuleSoft, Boomi) 가 ESB 의 기능 의 분산.

매 핵심

매 ESB 의 6 capabilities

Routing: 매 content-based, header-based.
Transformation: 매 XML↔JSON↔Avro, schema mapping.
Protocol bridging: 매 SOAP↔REST↔AMQP↔JMS↔FTP.
Orchestration: 매 multi-step workflow (BPEL, Camel routes).
Mediation: 매 versioning, throttling, security policy.
Monitoring: 매 audit, SLA tracking, error queues.

매 versus alternatives

Point-to-point: 매 N×N integration — ESB 의 N+1.
Hub-and-spoke: 매 single hub bottleneck — ESB 의 distributed.
Event mesh (modern): 매 Kafka + Schema Registry — 매 ESB 보다 throughput ↑, transformation logic 의 service-side.
iPaaS: 매 cloud-native ESB — 매 SaaS connector 의 thousand+.

매 응용

Bank legacy mainframe ↔ digital channel integration.
ERP (SAP) ↔ CRM (Salesforce) sync.
B2B EDI translation (X12, EDIFACT).

💻 패턴

Apache Camel content-based router

from("jms:queue:incomingOrders")
    .choice()
        .when(jsonpath("$.priority == 'HIGH'"))
            .to("kafka:high-priority-orders")
        .when(jsonpath("$.region == 'EU'"))
            .to("amqp:eu-orders")
        .otherwise()
            .to("jms:queue:standardOrders")
    .end();

XML → JSON transformation

from("file:input/orders?include=.*\\.xml")
    .unmarshal().jacksonXml(Order.class)
    .marshal().json(JsonLibrary.Jackson)
    .to("http://api.example.com/orders");

Saga orchestration (Camel)

from("direct:placeOrder")
    .saga()
        .compensation("direct:cancelOrder")
        .timeout(java.time.Duration.ofMinutes(5))
    .to("direct:reserveInventory")
    .to("direct:chargePayment")
    .to("direct:scheduleShipment");

Dead letter channel

errorHandler(deadLetterChannel("jms:queue:dlq")
    .maximumRedeliveries(3)
    .redeliveryDelay(2000)
    .useExponentialBackOff());

Modern replacement: Kafka + KStreams

StreamsBuilder builder = new StreamsBuilder();
builder.stream("orders", Consumed.with(Serdes.String(), orderSerde))
       .filter((k, v) -> v.getAmount() > 1000)
       .mapValues(o -> enrichWithCustomer(o))
       .to("high-value-orders");

Service mesh sidecar (Istio) replacement

apiVersion: networking.istio.io/v1beta1
kind: VirtualService
metadata:
  name: order-routing
spec:
  http:
  - match:
    - headers:
        x-region:
          exact: EU
    route:
    - destination:
        host: order-service-eu

매 결정 기준

상황	Approach
Greenfield microservices	Kafka + service mesh, ESB X
Legacy mainframe + SaaS integration	iPaaS (MuleSoft, Boomi)
Heavy XML/SOAP B2B	Apache Camel or MuleSoft
Event-driven architecture	Kafka + Schema Registry
Complex orchestration	Camel + Saga or Temporal.io

기본값: 매 2026 의 new project — Kafka + service mesh. 매 legacy integration — Camel or iPaaS. 매 traditional ESB (WSO2, Mule 3) 의 신규 도입 X.

🔗 Graph

🤖 LLM 활용

언제: 매 EIP pattern matching, 매 Camel DSL generation, 매 XSLT/XPath debugging, 매 legacy SOAP WSDL → REST OpenAPI 변환. 언제 X: 매 production routing rules 의 직접 deploy — 매 정확한 schema validation, dead-letter handling 의 review 필요. 매 transformation logic 의 round-trip test 필수.

❌ 안티패턴

God-ESB: 매 모든 business logic 의 ESB 의 집중 — 매 bus 의 monolith. 매 logic 의 service-side.
Synchronous chains: 매 ESB 의 long sync calls — 매 cascading failure. 매 async + saga.
No schema governance: 매 transformation 의 implicit contract — 매 producer change 시 silent break.
2026 의 new ESB 도입: 매 platform team 의 maintenance cost ↑ — 매 Kafka + iPaaS 의 분산.

🧪 검증 / 중복

Verified (Hohpe & Woolf "Enterprise Integration Patterns" 2003, Apache Camel docs 4.x, Gartner ESB→iPaaS 의 2024 report).
신뢰도 A.

🕓 Changelog

날짜	변경
2026-05-08	Phase 1
2026-05-10	Manual cleanup — Camel patterns, modern Kafka/mesh replacement, iPaaS context 추가

5.0 KiB Raw Blame History Unescape Escape