Let’s talk about considering the implications.‘Implications’ are the expected (and unexpected) effects that are applied to your current situation, either after you change something or intend to change something about that situation.
Lazy Event SourcingOr How to Live in the NowIf you read Fowler’s article on event sourcing or learned about it through many other sources, there’s one particular mental picture of this approach that you might have affixed to your brain.
Android Application ArchitectureOur journey from standard Activities and AsyncTasks to a modern MVP-based architecture powered by RxJava.
Domain ElementsI'm currently reading Functional and Reactive Domain Modeling by Debasish Ghosh and TIL some characteristics of the various domain elements:Entity: Has an identity; Passes through multiple states in the lifecycle; Usually has a definite lifecycle in the business
Singletons The Safe WayThe Singleton pattern is a useful pattern in Android development, and Java development at large. The Singleton…
Microservices and the organizational ImpactNowadays microservices are a highly discussed topic for software developers. Albeit…
The Current Ecosystem of MicroservicesA few days ago I stumbled upon this article by TechCrunch and among other things it depicts…
Large Application Model issuesIssues which appear with large & scalable applications.In all application we developers challenge quite similar things. One of most important is model layer as meant in MVC. There are a lot of different patterns…
“Almost-Infinite” ScalabilityThe concept of a heavily segregated logical design in order to achieve “Almost-infinitely scalable” systems is stated in the illuminating paper “Life beyond Distributed Transactions: an Apostate’s Opinion” (Pat Helland) as well as in “Implementing Domain Driven Design” by…
