Aviran: A lot of overall architecture reviews. I am managing many people. Since we work similar to Spotify, we have a guild. There is a lot of the culture and training people involved, and operating the guild and sharing knowledge across the companies. I’m involved in solving our scale issues, especially engineering scale, because I think we are alright regarding our infrastructure scale. We know how to do that. We are now trying to figure out how to scale engineering better and grow the company.

Aviran: Wix has around 80 million website builders that are using our platform. This means we serve millions of websites. We have a complete solution. We host everything at our end, so we have over 2 petabytes of images that are part of the websites. We handle about 2 billion requests a day just to serve those sites. We serve about 100 million websites a week.

We can relax our performance requirements when someone is in editing mode, but we are not willing to pay the price of even 10 extra milliseconds for the viewers.

Aviran: First of all, if you don’t have a problem, then don’t do it.

There can be mini-monoliths or microservices which serve just one function. There is really no good answer here. If things need to stay together, they should stay together. There is no real reason to break them apart. If a team cannot progress in producing code fast enough, then maybe you should think about how do you actually split the teams. If they are each working on a different subset of the system, that is what defines the boundaries of a microservice. If teams can work independently, that is a good starting point, because they can create various microservices which talk with each other. They just have to have well defined interfaces.