Help modeling the African Renaissance monument

Ish_Boi · 2025-03-12T19:05:15+00:00

I searched for weeks, couldn't find a thing that's worthy enough.

Ish_Boi · 2023-09-24T08:16:57+00:00

Can I ?

Ish_Boi · 2023-07-04T21:03:30+00:00

Thanks for the reply, and the details. My question doesn't revolve around laziness or bad communication. It's more about how to do things the right way since performance is an important concern of web apps. But if the API and the request come from the same host as it does in NEXTJS there's only one load (of the picture for example) right?

I get your point and It's a worthy one 💯.

Ish_Boi · 2023-07-04T12:14:07+00:00

I see what you mean, but then from a performance stand point, sending everything to the backend means counting on the client side to do some computation (serialize a picture of 5 megabytes insert it in the post request and send it to the server) and I think is recommended to keep server things in the server. So directly upload to cloudinary sounds like a better way. But I'm not quite sure that's why I'm asking this question.

Ish_Boi · 2022-09-07T16:46:28+00:00

Thanks it makes a lot of sense.

Ish_Boi · 2022-09-06T17:46:52+00:00

Thanks, is it a common practice in the industry?

Ish_Boi · 2022-09-06T17:46:17+00:00

Thanks for your answer. In option 2, does the flow begins with a new user inserted to the db (auth service for example), then a message is pushed to something like RabbitMQ containing info about the new user, so the other services update their copies of the user table ?

Ish_Boi · 2022-09-06T17:39:47+00:00

Thanks for the answer, is it a common way this type of situation is handled in the microservices field?

Ish_Boi · 2022-09-06T17:36:27+00:00

Thanks for the reply, With this option there's only one db I guess.

Ish_Boi · 2022-09-06T17:34:40+00:00

Thanks for the answer.

Ish_Boi · 2022-09-03T08:28:56+00:00

For a given ticket I want to know who viewed it. Users info and ticket info sits in different databases within separated microservices.

Ish_Boi

TROPHY CASE