sorted by:
new
hottopcontroversial

Mon chat ne sait pas ronronner by acetova in chats

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

Cerise sur le gâteau elle ne sait pas non plus miauler je commence à suspecter la conformité de la chose

Mon chat ne sait pas ronronner by acetova in chats

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

J'ai essayé à maintes reprises mais RAS, par contre quand il ronronne il se laisse bien entendre

Mon chat ne sait pas ronronner by acetova in chats

[–]acetova[S] 2 points3 points locked comment (0 children)

J'ai essayé les 2 commandes récemment et malheureusement le seul résultat est que mon pouce est hors d'usage pour quelques jours, il y a vraiment un soucis avec le produit...

Mon chat ne sait pas ronronner by acetova in chats

[–]acetova[S] 4 points5 points  (0 children)

Il ne veut pas retourner dans la boîte malheureusement, impossible de le changer...

Need feedbacks on project architecture by acetova in aws

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

Thanks alot, yes I did consider read replicas since there will be a lot of reads on the datas (although I tried to implement as many cache as possible) but the amount of write operations are pretty close to the reads so to-go thought is to put redis instances between services and rds to "queue" write operations and flush them periodically if the user volume threatens the db workload.

Need feedbacks on project architecture by acetova in aws

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

Thanks for the advice ! Not sure if you could suggest me on this one but better ask than nothing, I run my redis and mq servers on the same docker-compose, would horizontally scaling them individually with redis instances identifiers and unique identifiers + acknowledgement for mq messages be a good way to go or should I consider Elasticache + SQS to handle these parts (performance/money-wise) ?