I have a question, why go with AWS Amplifer, It's pretty rough to setup and manage. So with something else that is more flexible and easy to setup, like superbase,, or appwrite, they are more mature products in my experience. What's your thought Process, I would love to known
Hmm okay so I’m not really sure. My basic thought process was; I think I will use AWS for the backend because of the ChimeSDK, so I chose AWS amplify because I assume the integration between the regular AWS backend and the amplify thing will be smooth since it’s all aws. Although as I’m writing this I realise that I don’t even know if there is a difference between the classic AWS backend and amplify🤔
@@CoderCal okay, here's the difference, the amplify is a set of tools that is to set a backend and deploy backend, Just like firebase or Superbase, Where as Classic AWS are a bunch of service that perform a platform on which projects can be run on. Here's my though, Don't use AWS, it is pain, Expensive and verification of account is awful, I have used it and it's not good, Now you want to use ChimeSDK, you are using flutter and to use this there is a package for it as well. So, any backend will work using flutter package you can set the limit as you like, tools are there just need to config it.
@@hershalrao3472 Yeah , all backend is expensive, no matter which route you go with but when you are working on stating up a start up, then you need to launch your Products fast and feature full all, The expand of the grows comes later, you can, the reason why I like superbase is because the cost of moving data from one backend is much cheaper as compare to firebase and for free users to free tier, the migration is free. that's the only reason I like to use superbase for this kind of app start up.
hey! i really have a request for you, if you can make any new video for backend development guide like a roadmap. ( my english is bad please don't mind)
@@CoderCal No one is perfect, I am think about writing a blog post on compare different backend, One app and different backend tech and tell it's pros and con's which one is better for which solution, and you can make a video about this topic, it's something that is unique and fun.
Hey man! I wanted to try a more raw/genuine format and not have the pressure of the videos performing as much So far this is going way better than I expected!
Hey! Just want to say that I really enjoy watching your videos!
Thank you, that really means a lot!
Watching you since pre covid era.
this is refreshing to watch!
Nice!
I have a question, why go with AWS Amplifer, It's pretty rough to setup and manage. So with something else that is more flexible and easy to setup, like superbase,, or appwrite, they are more mature products in my experience. What's your thought Process, I would love to known
Hmm okay so I’m not really sure. My basic thought process was; I think I will use AWS for the backend because of the ChimeSDK, so I chose AWS amplify because I assume the integration between the regular AWS backend and the amplify thing will be smooth since it’s all aws.
Although as I’m writing this I realise that I don’t even know if there is a difference between the classic AWS backend and amplify🤔
@@CoderCal okay, here's the difference, the amplify is a set of tools that is to set a backend and deploy backend, Just like firebase or Superbase, Where as Classic AWS are a bunch of service that perform a platform on which projects can be run on. Here's my though, Don't use AWS, it is pain, Expensive and verification of account is awful, I have used it and it's not good, Now you want to use ChimeSDK, you are using flutter and to use this there is a package for it as well. So, any backend will work using flutter package you can set the limit as you like, tools are there just need to config it.
is supabase really epensive compared to using aws rds in the longer run, if my app will small or large scale??
@@hershalrao3472 Yeah , all backend is expensive, no matter which route you go with but when you are working on stating up a start up, then you need to launch your Products fast and feature full all, The expand of the grows comes later, you can, the reason why I like superbase is because the cost of moving data from one backend is much cheaper as compare to firebase and for free users to free tier, the migration is free. that's the only reason I like to use superbase for this kind of app start up.
Hi! what happened to your old channel?
hey! i really have a request for you, if you can make any new video for backend development guide like a roadmap. ( my english is bad please don't mind)
Great idea, but I’m really not the best person to do that unfortunately 😅
@@CoderCal No one is perfect, I am think about writing a blog post on compare different backend, One app and different backend tech and tell it's pros and con's which one is better for which solution, and you can make a video about this topic, it's something that is unique and fun.
Yay back to cpding
We need live coding live previous channel.
hi man, why this new channel ?
Hey man! I wanted to try a more raw/genuine format and not have the pressure of the videos performing as much
So far this is going way better than I expected!
@@CoderCal Love it ✨
Please try ruby on rails 8
Go and learn nvim tutorial
This is also not bad ASMR 😂
node backend with nvim club 🔥🔥🔥
This man needs telescope.nvim so badly.Also you can have ai code sugesstions with supermaven or avante or copilot much like vscode or even cursor.