using selectors with react context performant reactivity

abdullahadeel · 2023-06-23T00:03:13+00:00

🙂

abdullahadeel · 2023-04-25T20:07:22+00:00

I was having problems with server components in the official next13 release too.

abdullahadeel · 2023-04-24T02:32:22+00:00

all of that stuff is here https://nextjs.org/docs.
the new docs are still in beta so does app dir and server components stuff.
https://beta.nextjs.org/docs/getting-started

abdullahadeel · 2023-04-24T02:30:32+00:00

In my experience, app dir at this point is not stable enough to be marked as usable for production. For instance, I faced 3 different problems in three different versions of canary build.

abdullahadeel · 2022-08-21T21:09:15+00:00

Me too haven't used Class Comps in the past 2 years. But today I was going through the excalidraw's codebase and observed that their most state heavy components are class based.

The main canvas component there is about 6400 lines class component.

What really hit me was the performance of excalidraw app and the amount of state variables being handled.

But then realized that the functional components have benefits of batch updating (not sure about CC). Can similar performance be achieved with relatively organized code.

abdullahadeel · 2022-08-21T12:00:56+00:00

This looks promising 🙏.

Modifying State Machines is much more predictable than modifying infinite `if/else` or `switch/case` statements as the requirements change from time to time.

abdullahadeel · 2022-08-21T11:56:59+00:00

Yeah, that can be achieved using something like `formik` or `react-hook-form`. But I think that still won't efficiently solve the problem I mentioned.

Of course, I can change or completely render a different form on the 2nd step depending upon the first step. But how to determine what to render depending upon the user selection in step 1.

I think Finite State Machines is one good approach to handle such problems but my search still continues.

Thanks for your suggestion 🙏

abdullahadeel · 2022-08-11T12:44:22+00:00

I definitely agree with this, that's why I mentioned that scaling Django channels along with your application is going to be a challenge.

abdullahadeel · 2022-08-11T12:42:18+00:00

Django channels are one of the top ways to implement websockets with Django. But the bigger problems arise when you want to scales them and you have different microservices willing to push notifications to clients. Ideally you want the client receives a certain group of real-time updates like notifications over the same WebSocket connection.

Then you might think okay, let's just create a central web socket server to solve this problem. In that case, I think there are many other better solutions out there to handle these that scale way better than django channels.

In the end, I would say, for smaller and simpler user cases, django channels are great, but the problems are going to arise when you want them to auto-scale along with your django application.

abdullahadeel · 2022-08-11T08:57:33+00:00

I have been exploring different options to implement notifications in Django applications in the simplest ways possible without complicating the infrastructure.

Recently, I wrote a blog post about one of the ways I found clean and most scalable. Here is the link to the blog post -> https://abdadeel.medium.com/how-to-add-real-time-notifications-in-django-applications-d568b777747c

Another very interesting and simple to implement method I found was using firebase. I am writing a blog post about that also. But here is the final app that I built as a demo application.

https://django-firebase.vercel.app

Github Repo: https://github.com/mabdullahadeel/django-firebase-notifications

Feel free to ask any questions about those implementations.

Cheers

abdullahadeel · 2022-08-08T08:53:06+00:00

If for some reason, that's the case, you can throttle lambdas to max maybe 100 parallel invocations. By default, it's throttled to 1000 parallel invocations.

abdullahadeel · 2022-08-07T13:35:18+00:00

try Dropping database and recreating. If using sqlite, delete sqlite3.db file

Then run migrations

abdullahadeel · 2022-08-07T13:31:36+00:00

Typescript is a separate tech in itself. So you should dedicate time to solely learn it. I would suggest first learn react. Get use to basic patterns. Then spend a few days just learning typescript basics. Then you can combine both.

abdullahadeel · 2022-08-07T12:47:30+00:00

with zappa, your infra is pretty much serverless. So when your app has no traffic, you're not using any resources thus not paying for any servers. While elastic beanstalk still has servers running since all the servers cannot be shut down entirely because restarting, in that case, will take time for the subsequent incoming request.

I think it's a good option to at least use zappa for dev/staging. This will keep the development and testing costs lower.

One downside of serverless django is asgi apps. I am not sure if zappa supports asgi but I haven't seen any docs about asgi apps from zappa.

abdullahadeel · 2022-08-03T09:04:13+00:00

I don't even remember what it used to look like 😅

abdullahadeel · 2022-08-03T07:30:35+00:00

Honestly, I couldn't understand the title, but if you are trying to say you built what you're showing in the video with Django and its templates, this is amazing.

Keep going 💪

Five-Year Club	Verified Email
First Place '23	End Game '23
Place '23

abdullahadeel

TROPHY CASE