Once the product becomes famous and the customer base increases, it is no longer viable to serve the customers using simple systems without too many bottlenecks. Distributed software systems are inevitable, and it is directly related to the growth of the product. Building distributed systems is hard, and at the same time, it is fun. It is solving one big never-ending puzzle that gives you one unique challenge every day or every week depending on the size of the system. You cannot imagine any systems being built without security under consideration since for most organizations security is “job zero” or “job one,” whichever order they follow. Now building the security into distributed systems being a big challenge is an understatement.
Software developers previously primarily focused on getting the product to work and tried to fit the security into the product later. This approach came with a lot of overhead cost and reworks. It has changed a lot in recent times since organizations started to focus on it more than before. Developers started considering security in the early stage of the project. However, this kind of adoption varies across various sizes of the organization and their maturity. This article is going to talk about a few common distributed security trends from recent security reports and how developers can try to defend them when building.
