The database plan, queues, and deploying with Wrangler

Transcript preview

Okay, so let's see where the mobile application development is done. So we checked the plan, we were ready with the plans, we approved it. And all the details were mentioned there, the kind of API routes which will be created. It even plans for thumbs up, I don't know what that is, have a health API which is very interesting guys like when I used to mobile create mobile application even I was not planning that much. It created the table of what the information it should include. Let me give you a quick overview of what that is. So whenever you are planning of how the database looks like, imagine a Google sheet. So Google sheet like this one, I'll just create a sample one to show you something. So here when it's saying K, I will be saving an ID, ID is a random variable which will be created so that it has a unique thing, primary key it's called. Primary key because through that the whole row will be identified. So you know how products have ID, a unique ID so that you can identify its details. Similarly there is a unique ID which it has already planned for each recipe. Each recipe will have a source URL. So that will be an Instagram URL and you know the type of it is defined as text. So here's how it looks like. This is the ID column, this is the source URL column and so on and so forth. The details will be saved in that column and like that the database looks like. The reason I'm explaining this to you, created ad will be an integer. How can the created ad will be integers on scale? So it's a unit thing, don't worry about it. We can kind of convert that into however we want. But this is the reason I'm explaining this so that you will be able to imagine the database so that you can understand that hey maybe I want to save that also. So you can communicate your requirement.…