Game Engine Architecture

A common misconception is that a game engine only draws the graphics that we see on the screen. This is of course wrong, for a game engine is a collection of interacting software that together makes a single unit that runs an actual game. The drawing process is done by one of the subsystems that could be labelled as the rendering engine. But a game engine consists of several parts with much specified functionality: rendering, as mentioned, but also physics, networking, sound, etc. A game engine relies on high performance from each part, or subsystem, and of course on the engine as a whole. Looking back in the history of object oriented programming (OOP), performance for objects has been a major drawback and thus not suitable for games that need optimal speed. Something that you do need in a game engine is parts that can be easily replaced and code reuse so there is a trade-off between OOP and more imperative programming styles in certain parts of a game engine. But things change and so do programming languages s