The kwizbot platform represents services that interact with each other. The services themselves are wrapped in docker and can be delivered as isolated containers or native services if needed. The architecture provides for the deployment of the platform on: bare metal, cloud (AWS is preferred), other dedicated servers or virtualizations.
Architecturally, it can be a monolithic server, fragmented services from several servers, microservices in a cloud infrastructure. The platform can be orchestrated by using well-known tools or self-written control systems.
The bandwidth of the kwizbot platform has no limitations at the level of functionality or infrastructure, one of the conditional limits is limiting at the level of messengers.
The recommended capacities are based on additional integrations or interactions with other modules / services.
Monolithic architecture on one server
Monolithic diagram (example of implementation)
https://lh6.googleusercontent.com/47g_ql1lf0MAlFm2JcB5NNaDs4L5aLHVn7eXkrbAEe7FXi6LhGI4UoivSrxgnFxOs6KpGx1yUScMDPFN-GAIc9xmhL1cSV-hnWgTj6RU3DSsD7vaD1cQQhPB4_0n7tOsYy2r4qOF
Cloud AWS scheme (example of implementation)
https://lh4.googleusercontent.com/SdvTk4M4MUTztzPRHTuVJWESf77kv96lALFraj5LCW1n99KZ7vtp1G2o5QVu-tLk8JuWYYezYHd7fMw_EFo8hgawYDoK_j_Z0J_ZsJm6Uy6Q0AK3adPOz6Hhg5hi9QILUpaC4kN0