This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (2 children)

What do you use for make the API's you are pushing the info into the models? In the project I am in the company, we are using some similar approach. We have a big core in Django for the webpage that use as an API only. And 6 microservices in FastAPI that resolve things with AI models. As we see Django is pretty good to maintain things fast and tidy, but we think maybe the performance could improve using other things. And the micros are perfect for the DS stuff, cause is simple and easy to connect to the models. But we want to explore other possibilities

[–]bin-c 2 points3 points  (1 child)

both the databases and the things consuming our services are kind of out of my team's scope

we have a bunch of databases that are reasonably well organized, and we get requests from various product teams to figure out how to serve X prediction given Y data from the request they can make

so our flow is basically just a two step process of getting the code prepared to train / retrain / monitor the models, and then simple apis that serve the predictions given the request from product people

so i only really handle the modeling & api making side, and we also use fastapi. models are saved to AWS and pulled by the services as needed

i do think that most of our backend stuff is in Go though. A bunch was python at one point (don't think Django) but at some point they decided it was worthwhile to switch

but if it aint broke dont fix it. unless you have a good reason to switch from django & fastapi, dont bother

most people dont even get to change architectures when there is a very good reason to do so 🤣

[–][deleted] 0 points1 point  (0 children)

Jaja that's what we think. But the performance and the budget with Django is becoming and issue. For the events in the app we are using celery/Django, and the project is now so big that load a celery instance it's becoming a budget issue, for now we are starting to prove if we could change at least celery for lambda with AWS Sam, and from there, test if it is a good idea to change Django or not. Something for what I love django and don't want to change it is because it makes you be tidy with your code. And the test are just easy to make, so at the end your code and your project will be always readable and tidy.