JSON moving: a non-revolutionary approach

In terms of features and workload products tend to grow evolutionarily. The backend has to follow this process. In practice, however, it is much more difficult to evolve the backend to meet the needs of a product than it is to design the service correctly once. This often raises the desire to redesign everything from scratch.

The report will take us through the evolution of an imaginary backend service from startup to enterprise, addressing the major pains of each development stage.

Along the way, we’ll discuss:
— How to minimize the now-we-have-to-rewrite-everything situations
— What changes in cross-service interaction as the service size grows
— What interesting things happen in the backend when moving to neural network APIs