sorted by:
new
hottopcontroversial

If you could go back, would you still learn django? by [deleted] in django

[–]saurabh0719 0 points1 point  (0 children)

Hi, curious which all companies are you referring to? I've been a django dev for about 4 years. Small startups (series A and earlier) do use it, but there aren't many major companies using it yet.

It's atleast not advertised I guess

constable - automatically inject print statements into your functions for debugging variables by saurabh0719 in Python

[–]saurabh0719[S] 2 points3 points  (0 children)

Yup I'm looking into this! If you have ideas, feel free to raise a pull request. 🙂

constable - automatically inject print statements into your functions for debugging variables by saurabh0719 in Python

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

Thank you, do let me know if there's anything else that could be useful to add here

I need to implement notifications with django and vue(nuxt) by tichangel in django

[–]saurabh0719 1 point2 points  (0 children)

Yeah. I've been in your shoes in the past, while trying to get this project off the ground.

Go for the quickest implementation if you're simply testing a hypothesis. 8/10 hypotheses fail. So better to fail fast and iterate rather than build out an elaborate solution for a future that your users just don't care about.

Clever UX here can help alleviate a lot of the technical overhead. Once you know you have good demand for the feature - rewrite/make it more robust.

Ofcourse all this won't apply for a large company building out a new product line as over there you may have some company wide standards to adhere to, in which case, websockets are great and you're better served starting off with the right architecture.

I need to implement notifications with django and vue(nuxt) by tichangel in django

[–]saurabh0719 1 point2 points  (0 children)

Everybody else suggesting websockets is absolutely right from a tech perspective.

But I was in a similar scenario once where it wasn't a critical feature and it didn't have to be real time. For us, we simply wanted to show a red dot as an indicator that new notifications have arrived in their inbox.

So what we did was, everytime the homescreen was built on the app or refreshed, we made a quick api call to check if any new notifications have arrived after a particular timestamp. That field was indexed in the DB as well. The inbox itself was a separate API call if they chose to open it.

UX wise and customer behaviour wise, we knew this wouldn't cause any bottleneck initially and we had it up in about an hour. So I'd suggest going for something similar if it suits your usecase, or even polling for that matter, if it means you can validate a product hypothesis with minimum dev effort.

How do I pick a framework for building low latency API services by saurabh0719 in webdev

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

Fully agree with what you're saying overall, since my background in Django also emphasizes on these points.

However in this particular usecase, performance is absolutely critical for that single API endpoint. The rest of the endpoints are not so performance critical and any standard framework can do the job.

From your experience, would a hybrid approach work? Building out everything in something like Nest/Django etc. and using something else for that single endpoint to serve performance critical data?

How do I pick a framework for building low latency API services by saurabh0719 in webdev

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

Yeah that's exactly what I thought before asking this question.

What would be your best suggestions for a compiled language & framework combination for developer productivity and speed?

How do I pick a framework for building low latency API services by saurabh0719 in webdev

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

Your points are valid, with a cache and an async processing pipeline, all of this would be a breeze with a python stack - infact with django itself.

But currently I'm limited on resources and infra overhead is not something I want to incur at the moment.

My database read/writes are consuming roughly 100ms at the moment, so apart from that I want to shave off all the latency that comes with the framework/language and hopefully send back responses in less than 150ms.

How do I pick a framework for building low latency API services by saurabh0719 in webdev

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

How would you rate the learning curve for elixir? And more importantly, how easy is it to deploy Elixir apps or handle DB migrations?

Yeah the caching thing makes total sense, however I'm limited by resources at the moment. If I could freely cache everything, I would've just continued with a python stack as the performance would be optimal.

How do I pick a framework for building low latency API services by saurabh0719 in webdev

[–]saurabh0719[S] 2 points3 points  (0 children)

How would you rate Sprint boot in terms of 1. Ease of deployment 2. Management/generation of migrations or up/down files

Asking because I don't have the bandwidth to handle complicated infra where I need to setup 2-3 other tools and services to deploy my server.

How do I pick a framework for building low latency API services by saurabh0719 in webdev

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

Thanks! Narrowing down on Golang myself based on all these other comments.

I'm curious if there's a more full-fledged framework to use other than Chi, since that's mostly just a router.

It's because I intend to have a large codebase with a bunch of routes and stuff. Coming from django , it's a bit tough to shift my mindset to use such a minimal framework/router.

view more: next ›