Architecture & Design
Sharing system architecture and design decisions and experiences.
[Integrated Real Estate AI Agent 1/2] Making AI Answers Lead to Real Service Actions
Aiming for an integrated AI agent that solves real estate problems in a single conversation, this post covers how we made the AI's answers lead to real service features such as brokerage requests.
November 13, 2026
[Integrated Real Estate AI Agent 2/2] Dividing the Roles Between the LLM and Code
While connecting the AI's answers to our service, I summarize how we divided what to leave to the LLM and what the service should be responsible for, how we enforced that in code, and how we dealt with the slower responses.
November 13, 2026
Building an AI Property Recommendation System — How We Handle 'Recommend me a new apartment near Gangnam Station, around 30 pyeong'
Hi, I’m Jeongil Jeong, a backend developer at a proptech platform. It seems like many companies these days are thinking hard about how to integrate AI into their services in ways that deliver real value. Our company is no different. We’ve been continuously exploring how we could use AI to provide a ...
March 25, 2026
MSA Was Too Much for Us - Our Journey to Modular Monolith
Hello. I’m Jeongil Jeong, a backend developer working at a proptech platform. Our company had successfully completed a zero-downtime migration from a legacy Java Servlet monolithic service to MSA and was operating it in production. The process wasn’t easy, but we learned a great deal by experiencing...
February 20, 2026
[Reflections on MSA 7/7] Do We Really Need MSA?
Previous: [Reflections on MSA 6/7] Event-Based Data Consistency Issues and Solutions in MSA Over the past six parts, we’ve explored various aspects of MSA. How to divide services, how to communicate between them, how to respond to failures, and how to separate data while maintaining consistency. I’v...
January 22, 2026
[Reflections on MSA 6/7] Event-Based Data Consistency Issues and Solutions in MSA
Previous: [Reflections on MSA 5/7] How Should We Separate Data? In the previous part, we explored why we should separate DBs in MSA environments and how to solve the JOIN problem after separation. There were two methods: API Composition and Data Replication. But choosing “data replication” doesn’t m...
January 21, 2026
[Reflections on MSA 5/7] How Should We Separate Data in MSA?
Previous: [Reflections on MSA 4/7] How Failures Propagate and Where We Should Break the Chain In the previous part, we explored how failures propagate in MSA environments and various patterns to prevent them. From Timeout, Retry, to Circuit Breaker, there were many different approaches. But there’s ...
January 20, 2026
[Reflections on MSA 4/7] How Failures Propagate and Where We Should Break the Chain
Previous: [Reflections on MSA 3/7] Inter-Service Communication in MSA - How Should We Do It? In the previous part, we looked at communication methods between services in an MSA environment. We had various options from REST, gRPC, to message queues. However, regardless of which communication method y...
January 19, 2026
[Reflections on MSA 3/7] Inter-Service Communication in MSA - How Should We Do It?
Previous: [Reflections on MSA 2/7] How to Divide Services in MSA In the previous episode, we looked at how to divide services and the principles and considerations for setting boundaries. One of the things I thought about most while working in an MSA environment was “inter-service communication.” Wh...
January 16, 2026
[Reflections on MSA 2/7] How to Divide Services in MSA
Previous: [Reflections on MSA 1/7] What is MSA (Microservices Architecture)? In the previous episode, we explored the concept of MSA, its background, and various alternatives. If you’ve decided to adopt MSA, you now face the first question. “How do we divide services?” Why is this question important...
January 15, 2026