I feel like data storage scalability in distributed or not systems is often overlooked. Whenever we talk about scalability, we usually imply processing scalability in distributed systems. We talk about ways to scale out dedicated service clusters without downtimes or data flow interruptions. I’ve written a few articles about it myself. But today, let’s talk about data scalability. How can we efficiently handle massive data sets without downtime or performance implications?
When it comes to daily developer routines, Git has proven itself as a reliable and predictable VCS. This article is a collection of practical recommendations for using Git effectively.
Domain-Driven Design can be perceived differently from different perspectives. It is a philosophy, a framework, a set of architectural patterns, and many more things with the ultimate purpose of building the right thing right.
A lot has changed in the Internet world in the past few decades. What and how do we consume on the Internet. The size of the data. Security expectations. At the same time, not much has changed in the world of protocols that enable the Internet. Is the introduction of HTTP/3 a necessary step or a revolution? What is it, and what problems does it solve.
Data Consistency might be a pain in the ass. It is a well-known source of unexpected surprises. What is it? What does it depend on? Why is it so often overseen? And how to achieve different types of consistency in a distributed system? All right here...
Nowadays, many developers consider Monolithic Architecture as a disputed one. Sometimes even referenced as an anti-pattern. Is it a deserved stamp? Why is it still being deliberately chosen and used by many organizations? Finally, a few words about common delusion around Microservice Architecture and how easily and unconsciously it becomes Distributed Monolith.
Clean Architecture is a pretty bold statement and quite a hollow and opaque thing to say. I think of Clean Architecture as philosophy. It is not about the system today, but about the system today and tomorrow. More details inside
Systems do evolve and unavoidably evolution leads to breaking changes... If you are doing event sourcing, events evolution is unavoidable, ultimately you will crash 🔥🚒 into it. The more you know, the better you prepared, as they say 🤓
Just want to share one of the tools I'm using daily. A React component for building Web forms from JSON Schema. Transform annoying, time consuming task into simple routine
Events, events, events... Events are everywhere... Event Sourcing, Event Streaming, Asynchronous services and much more. All these technical contexts have something in common, but a lot is different. And this is what this article is about 🤓
Too often, I found myself with bloated Controllers. Or when Controllers seemed like an awkward and redundant solution. Anyhow I kept using them. I know I'm not the only one who trapped in a similar situation? Is it Controllers or us doing something wrong? Here I tried to shed a bit of light on this topic.