There are two main ways how to develop the backend for Zion v2:

monolith and micro-service architecture.

Each options meets initial and crucial requirements to performance

provided by Zion management team

Total users / MAU 500,000

Avg DAU 50,000
Daily Activity Index 100
Daily Post Activity 10
Data per user a day 1 Kb
Total communities 10,000
Avg users per community 500
Max users per community 150,000
Avg transactions a day 5,000,000
Max (TPS) trancations a sec 150
% of internal 90
Needed storage capacity per month for new data 150 Gb

With monolith architecture we can start from simple system and evolve it
over time, focusing on parts which really need to be enhanced from
scalability point of view

Developing a complex micro-service architecture, which include

message queues, inter-service communication etc. under the time
pressure can cause troubles and architectural mistakes, which may cost
too much

According to our expertise and experience of other companies, e.g

• https://martinfowler.com/bliki/MonolithFirst.html
• https://martinfowler.com/bliki/MicroservicePremium.html
• https://buttercms.com/books/microservices-for-startups/
should-you-always-start-with-a-monolith/
• https://dsg.tuwien.ac.at/team/sd/papers/
Zeitschriftenartikel_2021_SD_Benchmarks.pd

micro-service architecture is not a silver-bullet for all cases, especially,

for startups.