πΎ Archived View for jaeyoung.se βΊ journal βΊ 12283.gmi captured on 2023-07-22 at 16:44:18. Gemini links have been rewritten to link to archived content
β¬ οΈ Previous capture (2023-03-20)
-=-=-=-=-=-=-
While I was following
on the laptop with Vagrant VMs, I was reminded of the conviction that I had been holding: a general application should not deal with computer networking. That is, it should not concern with host addresses or ports or HTTP protocols or anything. Instead, it should work above a messaging abstraction provided by something like
or Kafka or such.
If the application requires low network latency such as video streaming, then it would need to deal with networking. But for an application that processes JSON messages and operates near the business level, the complexity of configuring networking is simply unjustified. Ideally, it would only need to know how to connect to a message broker and get all messaging done through it. It should even dispense with DNS. Any application that relies on DNS for service discovery has a tendency of being subtly broken.
Alas, a saner networking abstraction is not a norm, and that means I have to configure network overlay and DNS server, go through all their platform-specific details, to have a usable Kubernetes cluster.
μ£½λ λ κΉμ§ νλμ μ°λ¬λ¬
ν μ λΆλλΌμ΄ μκΈ°λ₯Ό,
μμμ μ΄λ λ°λμλ
λλ κ΄΄λ‘μνλ€.
λ³μ λ Έλνλ λ§μμΌλ‘
λͺ¨λ μ£½μ΄κ°λ κ²μ μ¬λν΄μΌμ§
κ·Έλ¦¬κ³ λνν μ£Όμ΄μ§ κΈΈμ
κ±Έμ΄κ°μΌκ² λ€.
μ€λ λ°€μλ λ³μ΄ λ°λμ μ€μΉμ΄λ€.