0 views collected around this technical thread.
This article explains why, when, and how to split a monolithic application into microservices, covering the goals of splitting, timing decisions, guiding principles, granularity considerations, functional and non‑functional strategies, merging practices, and associated risks.
This article examines the transition from monolithic to microservice architectures, outlining the advantages and costs of microservices, the conditions under which they should be adopted, practical implementation options, risk assessments, service‑splitting strategies, and a concise comparison with SOA.
This article describes how Worktile introduced Scrum, built an 8‑person self‑organizing Scrum team for the Lesschat product, iterated through two‑week Sprints, identified and solved scaling challenges, and eventually evolved into a multi‑team, hundred‑person agile R&D organization with continuous delivery practices.
The article explains how to design and evolve agile R&D organization structures—from a small startup team to medium, large, and multinational groups—by applying high‑cohesion, low‑coupling, and full‑functionality principles, using Spotify’s squad‑tribe‑chapter‑guild model and rotation mechanisms to eliminate bottlenecks and single points of failure.
This article examines the transition from monolithic to microservice architecture, outlining the benefits and drawbacks of each, the conditions under which microservices should be adopted, the necessary technical and team resources, risk assessments, and practical guidance on service decomposition and migration.
This article recounts how a rapidly growing payment team split off from its original department, faced scaling, performance, and maintainability issues with a legacy SSH‑based Java architecture, and chose a micro‑service redesign, detailing the problems encountered, the restructuring approach, and the insights gained.
This article explains how startup engineers can design and implement a scalable web architecture—covering server clustering, load balancing, distributed caching, database replication, and team organization—to handle rapid user growth without compromising performance or reliability.