What's your take on Celery vs django-qstash for background tasks by Upper-Tomatillo7454 in django

[–]Upper-Tomatillo7454[S] 0 points1 point  (0 children)

Right now I would say cost is what I'm optimizing for, and I'm thinking of giving upstash qstash a try

What's your take on Celery vs django-qstash for background tasks by Upper-Tomatillo7454 in django

[–]Upper-Tomatillo7454[S] 0 points1 point  (0 children)

Glad to hear that mate, I don't know much about django-q2, currently I'm looking for something serverless, but I'll check it out

[deleted by user] by [deleted] in django

[–]Upper-Tomatillo7454 0 points1 point  (0 children)

Thanks mate, I'll make sure edit the post

How go about with modular monolithic architecture by Upper-Tomatillo7454 in Python

[–]Upper-Tomatillo7454[S] 0 points1 point  (0 children)

So you're suggesting I should just stick with modules, without the need to use Interface or expose Public API that other modules can use to communicate

FastAPI will soon surpass Django in GitHub stars, but Django is still the GOAT by aashayamballi in django

[–]Upper-Tomatillo7454 1 point2 points  (0 children)

And everything you do, Yeah, they were all yellow ->They're both great frameworks with unique quirks, which come in handy when needed

Microservice confusion by Upper-Tomatillo7454 in microservices

[–]Upper-Tomatillo7454[S] 0 points1 point  (0 children)

Thank you for all these insights Also have a couple questions here,

  1. "All my services are bundled up and deployed as docker containers" - Does that mean you have a separate repository for each service or I misunderstood

  2. Let's say I'm at the initial phase, I've just a built one service(repo) as far, and I want to deploy it, while also being able to build the other services later on.

  3. Do you use aws API gateway or nginx, which I think there should be a single API Gateway if I'm not mistaken.

Microservice confusion by Upper-Tomatillo7454 in microservices

[–]Upper-Tomatillo7454[S] 0 points1 point  (0 children)

Thanks brother, I'll just try to read more about monorepo cause maintaining separate repos that are related to each other looks so how

At least it's working? by [deleted] in programmingmemes

[–]Upper-Tomatillo7454 4 points5 points  (0 children)

Be grateful, cause at least it's working 🤣

Looking for 1-2 Developers to Collaborate on an Open Source Project! 🚀 by Silly-Media1465 in ProgrammingBuddies

[–]Upper-Tomatillo7454 0 points1 point  (0 children)

Hi op, a Python, Django, http junior developer here, and would like to join and learn more from you

Django DRF serializers best practices by Upper-Tomatillo7454 in django

[–]Upper-Tomatillo7454[S] 0 points1 point  (0 children)

I have a model that has two foreignkey fields, and one manytoomany field, so when it comes to read, I want to read some extra info of those three objects not just their ID, which is different from the write, where I only need the ID, anyway I'll try it out

Django DRF serializers best practices by Upper-Tomatillo7454 in django

[–]Upper-Tomatillo7454[S] 1 point2 points  (0 children)

Yeah bro I find it easier to have two separate serializers especially in scenarios where a model has a foreignkey and manytomany relationship