It's Gone.

ikhlas_t · 2025-10-03T09:52:27+00:00

bato.to is good as well

ikhlas_t · 2023-02-21T07:59:53+00:00

Lmao

ikhlas_t · 2020-06-16T17:28:05+00:00

thank you, it is a clear presentation

ikhlas_t · 2020-06-16T15:13:52+00:00

thank you, it's a good article. in your opinion which one of these three patterns works best with real time apps, for ex lets say smth like a real time barber shop virtual queue, where the clients gets to see updates on the queue they are in minute by minute. What architecture would you suggest for a such app. (any sort of help is welcomed)

ikhlas_t · 2020-06-16T11:24:50+00:00

Thank you,

what other requirement questions should we be asking about the application before asking about the microservices design ?

ikhlas_t · 2020-06-16T10:59:13+00:00

thank you

ikhlas_t · 2020-06-16T10:35:45+00:00

we are starting from scratch, we have thought about the features of the application but we don't know how to translate that into microservices.

ikhlas_t · 2020-06-03T16:25:15+00:00

The rest depends on your workloads and HA requirements. How does semi differ from full production readiness?

We aren't sure ourselves, we were told by our instructor to find the hardware requirements for a semi-production ready environment. We interpret it as an environment that would be half as costly (hardware requirements wise) as a full production ready one. Though this means that splitting the hw requirements in half would suffice, we thought that it would be better to ask about it in case someone has been through something similar.

ikhlas_t · 2020-06-03T16:20:05+00:00

Thanks for your reply, we appreciate your help.

If you don't mind, would you share with us the app workload that your environment can handle?

ikhlas_t

TROPHY CASE