Data togetherness

There are moments when a design and architecture of software speaks through code. It might be the simplicity of a specific piece or nightmarish gymnastics one has to do to make something out of it. Recently I was working on an architecture of one solution. I was going back and forth trying to cut the cost of performing some calculations. It stroke me that there was a quality of code that was a result of higher level assumption. It was something related to bringing computation to data and splitting services the right way. The best term that I came up with though, was data togetherness.