Codesophy

Balancing between row and columnar DBs

Columnar databases have a lot of benefits, especially for OLAP workloads. Rows-based is also still in the game, but mostly applied to OLTP? Is there a well-balanced solution? Probably yes. Last days I was actively writing about aspect-oriented approaches that seems to be such

Codesophy

Aspect-oriented modeling

Many of us have heard about aspect-oriented programming. When some concerns like logging, validations and other aspects are flexibly injected into processes. But what's about design of the application? Aren't there any aspects? I think there are. One of the most frequent examples is

Codesophy

Business objects redesigned

We used to define business objects mostly as classes. But what if they become interfaces while instances will be created automatically from some factory (like IoC container)? Philosophically let's imagine we are talking about some laptop. What is usually important for us? Probably it's

Codesophy

Divide and conquer as a philosophy

In programming we frequently use principle of atomicity, trying to implement things as small as possible. SRP principle in SOLID forces us to make responsibility atomic. Micro-services also reflect this idea. Agile methods use the same approach for changes, instead of one huge "change"

Codesophy

Philosophy of issue tracking

While working on Codesophy project I am trying to refactor my vocabularies and make them more simple and consistent. Today I have an "issue tracking" tools like JIRA on the table. I understand the a historical nature of this term, but in my opinion

Subscribe to Stan Ego