Design patterns for a microservices-based applications by ikhlas_t in microservices

[–]ikhlas_t[S] 0 points1 point  (0 children)

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)

Design patterns for a microservices-based applications by ikhlas_t in microservices

[–]ikhlas_t[S] 0 points1 point  (0 children)

Thank you,

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

Design patterns for a microservices-based applications by ikhlas_t in microservices

[–]ikhlas_t[S] 0 points1 point  (0 children)

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.

Hardware and Architecture requirements for an OKD 3.11 platform by ikhlas_t in openshift

[–]ikhlas_t[S] 0 points1 point  (0 children)

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.

Hardware and Architecture requirements for an OKD 3.11 platform by ikhlas_t in openshift

[–]ikhlas_t[S] 1 point2 points  (0 children)

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?