<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Go on wid's blog</title><link>https://wid-blog.pages.dev/tags/go/</link><description>Recent content in Go on wid's blog</description><generator>Hugo</generator><language>ko</language><lastBuildDate>Wed, 03 Apr 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.pages.dev/tags/go/index.xml" rel="self" type="application/rss+xml"/><item><title>concurrency-go 회고</title><link>https://wid-blog.pages.dev/posts/career/personal/concurrency-go-retrospective/</link><pubDate>Wed, 03 Apr 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.pages.dev/posts/career/personal/concurrency-go-retrospective/</guid><description>Go의 동시성 패턴 세 가지(mutex, channel, lock-free)를 직접 구현하고 벤치마크하며 체화한 과정의 기록.</description></item><item><title>Go Concurrency 모델</title><link>https://wid-blog.pages.dev/posts/tech/language/go-concurrency-model/</link><pubDate>Wed, 03 Apr 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.pages.dev/posts/tech/language/go-concurrency-model/</guid><description>Go의 동시성 모델은 CSP를 기반으로 Goroutine과 Channel을 핵심 도구로 제공한다. 각 도구의 동작 원리와 선택 기준을 정리한다.</description></item><item><title>chat-services 회고</title><link>https://wid-blog.pages.dev/posts/career/personal/chat-services-retrospective/</link><pubDate>Sun, 31 Mar 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.pages.dev/posts/career/personal/chat-services-retrospective/</guid><description>실무에서 깊이 다루기 어려웠던 Kafka와 Hexagonal Architecture를 채팅 시스템 개인 프로젝트로 직접 설계하고 구현한 과정의 기록.</description></item><item><title>Go에서 Hexagonal Architecture 구현</title><link>https://wid-blog.pages.dev/posts/tech/architecture/go-hexagonal-architecture/</link><pubDate>Wed, 21 Feb 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.pages.dev/posts/tech/architecture/go-hexagonal-architecture/</guid><description>Hexagonal Architecture의 핵심 개념과 Go에서의 관용적 구현. 암묵적 인터페이스와 패키지 구조를 활용한 의존성 방향 제어.</description></item></channel></rss>