# How do you guys approach architecture and system design in games? — retained record

> Retained reddit record from reddit:gamedev.

Canonical: https://highsignal.app/data/records/ccfbc8f6da4bc00f

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:gamedev)  published 2026-09-16 16:13 ingested 2026-09-17 02:36

[original source ↗](https://www.reddit.com/r/gamedev/comments/1wi1pdz/how_do_you_guys_approach_architecture_and_system/)

## retained text



```
I work mostly with Unreal, and architecture is probably the thing I struggle with the most.

Even when I’m building a single feature, I often have a hard time figuring out how to structure it properly.

Like, where should the data live?  
Where should the logic live?  
What should be its own component or system, and what should just stay simple?

And once multiple systems need to interact, I start second guessing things even more.

Should these systems know about each other directly?  
Should I use events, interfaces, components, some manager, etc.?  
Am I making things too coupled, or am I overengineering them trying to avoid coupling?

I know there probably isn’t one "correct" way to structure things, but I’m curious how more experienced devs actually think about this stuff.

When you start building a new system or feature, do you plan the architecture first, or just make the simplest version that works and refactor once you understand the problem better?

Are there any rules of thumb, talks, books, projects, or even mistakes you made that helped architecture finally click for you?
```



document fetched 2026-09-17 00:26 · canonical https://reddit.com/r/gamedev/comments/1wi1pdz/how_do_you_guys_approach_architecture_and_system
