<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://huisam.github.io/</id><title>huisam</title><subtitle>huisam's blog — backend &amp; AI tech engineering notes.</subtitle> <updated>2026-08-12T21:18:58+09:00</updated> <author> <name>huisam</name> <uri>https://huisam.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://huisam.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://huisam.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 huisam </rights> <icon>https://huisam.github.io/assets/img/favicons/favicon.ico</icon> <logo>https://huisam.github.io/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Serving Text and Tools with an LLM API (feat. OpenAI)</title><link href="https://huisam.github.io/posts/llm-api/" rel="alternate" type="text/html" title="Serving Text and Tools with an LLM API (feat. OpenAI)" /><published>2026-08-12T19:00:00+09:00</published> <updated>2026-08-12T19:00:00+09:00</updated> <id>https://huisam.github.io/posts/llm-api/</id> <content type="text/html" src="https://huisam.github.io/posts/llm-api/" /> <author> <name>huisam</name> </author> <category term="AI" /> <category term="LLM" /> <summary>In Coming Last time we walked through how an LLM basically works and what happens under the hood. Today I want to take a more practical angle and show how you can actually put a Frontier Model to work. The term Frontier Model may not be obvious at first, so let’s split the LLMs we commonly use into two categories: Frontier Model: trained on an enormous amount of data with a huge number o...</summary> </entry> <entry><title>An easy look at the structure and principles of an LLM (feat. llama)</title><link href="https://huisam.github.io/posts/llm-architecture/" rel="alternate" type="text/html" title="An easy look at the structure and principles of an LLM (feat. llama)" /><published>2026-08-10T19:00:00+09:00</published> <updated>2026-08-10T19:00:00+09:00</updated> <id>https://huisam.github.io/posts/llm-architecture/</id> <content type="text/html" src="https://huisam.github.io/posts/llm-architecture/" /> <author> <name>huisam</name> </author> <category term="AI" /> <category term="LLM" /> <summary>In Coming Today I want to walk through the structure and the way an LLM (Large Language Model) works, in a way that is easy to follow. The deeper you go, the more you end up explaining mathematical formulas and paper-level material, so I am not going to dive to that depth here. Instead let’s unpack it step by step in plain language 😁 Architecture An LLM is, at its core, a model that predic...</summary> </entry> <entry><title>Gradle multi module(project) with Spring Boot (feat. Kotlin)</title><link href="https://huisam.github.io/posts/gradle-multi-module-build/" rel="alternate" type="text/html" title="Gradle multi module(project) with Spring Boot (feat. Kotlin)" /><published>2026-08-06T19:00:00+09:00</published> <updated>2026-08-06T19:00:00+09:00</updated> <id>https://huisam.github.io/posts/gradle-multi-module-build/</id> <content type="text/html" src="https://huisam.github.io/posts/gradle-multi-module-build/" /> <author> <name>huisam</name> </author> <category term="Backend" /> <category term="Gradle" /> <summary>In Coming Most projects these days are structured with multi modules in mind. Teams split their code into multiple modules to separate each module’s responsibility and to push reusability further. But the moment you split into multi modules, the biggest pain point that shows up is having the same build configuration duplicated across every module. To solve exactly that, Gradle offers module...</summary> </entry> <entry><title>Why do SocketException: Connection reset and ClientAbortException happen?</title><link href="https://huisam.github.io/posts/socket-exception-connection-reset/" rel="alternate" type="text/html" title="Why do SocketException: Connection reset and ClientAbortException happen?" /><published>2026-08-05T18:00:00+09:00</published> <updated>2026-08-05T18:00:00+09:00</updated> <id>https://huisam.github.io/posts/socket-exception-connection-reset/</id> <content type="text/html" src="https://huisam.github.io/posts/socket-exception-connection-reset/" /> <author> <name>huisam</name> </author> <category term="Backend" /> <category term="Network" /> <summary>In Coming As MSA has become the norm, we end up operating a variety of domain servers in order to work through complex business requirements. The more domain servers there are, the more network communication grows along with them. And with that growth comes a whole family of network-related exceptions. But analyzing a network error and reasoning about all the situations that could have produ...</summary> </entry> <entry><title>Observability - Integration with Spring Boot</title><link href="https://huisam.github.io/posts/observability-spring-boot/" rel="alternate" type="text/html" title="Observability - Integration with Spring Boot" /><published>2026-07-31T19:00:00+09:00</published> <updated>2026-07-31T19:00:00+09:00</updated> <id>https://huisam.github.io/posts/observability-spring-boot/</id> <content type="text/html" src="https://huisam.github.io/posts/observability-spring-boot/" /> <author> <name>huisam</name> </author> <category term="Backend" /> <category term="Observability" /> <summary>In Coming In our previous post, we covered the fundamental concepts of Observability. To briefly recap: Observability aims to understand why errors occur, and refers to the act of instrumentation — enabling even someone unfamiliar with a system’s internals to find the root cause of a problem. The three most important pillars of Observability are: Metric Trace Log Therefore, when o...</summary> </entry> <entry><title>Observability - Concepts with Grafana Examples (feat. Prometheus, Tempo, Loki)</title><link href="https://huisam.github.io/posts/observability/" rel="alternate" type="text/html" title="Observability - Concepts with Grafana Examples (feat. Prometheus, Tempo, Loki)" /><published>2026-07-29T20:10:00+09:00</published> <updated>2026-07-29T20:10:00+09:00</updated> <id>https://huisam.github.io/posts/observability/</id> <content type="text/html" src="https://huisam.github.io/posts/observability/" /> <author> <name>huisam</name> </author> <category term="Backend" /> <category term="Observability" /> <summary>Background Today, let’s talk about Observability. Monitoring Most of you have probably heard of the term “Monitoring.” The reason teams build monitoring systems is to check the state of their systems in real time. Monitoring is tooling or a technical solution that allows teams to watch and understand the state of their systems. Monitoring is based on gathering predefined sets of metrics ...</summary> </entry> <entry><title>Implementing Idempotent HTTP APIs with the Idempotency-Key Header</title><link href="https://huisam.github.io/posts/spring-idempotency/" rel="alternate" type="text/html" title="Implementing Idempotent HTTP APIs with the Idempotency-Key Header" /><published>2026-07-28T20:07:00+09:00</published> <updated>2026-07-29T20:07:59+09:00</updated> <id>https://huisam.github.io/posts/spring-idempotency/</id> <content type="text/html" src="https://huisam.github.io/posts/spring-idempotency/" /> <author> <name>huisam</name> </author> <category term="Backend" /> <category term="Spring" /> <summary>Introduction As systems grow larger, communication between different backend services becomes more frequent and more complex — and with more network calls comes a higher chance of network failures. These failures can stem from many causes: brief network blips, client-side connection timeouts, packet loss, and so on. Digging into the root cause every single time is expensive, and even when you...</summary> </entry> </feed>
