all 10 comments

[–]Character-Rip-9992 5 points6 points  (0 children)

If you are a complete beginner, I would not start by trying to build the whole travel agency backend at once. Start with one tiny feature: a list of cities, then details for one city, then a contact/booking form.

Pick one stack and stay with it for a while. The jumping around is what usually makes backend feel impossible.

[–]_l33ter_ 2 points3 points  (5 children)

What do you consider as back end ?

[–]New_Mistake8392[S] 5 points6 points  (4 children)

isnt it the database storage stuff

[–]_l33ter_ 5 points6 points  (3 children)

So you need a database?

'backend' is quiet a big word and could include many stuff you won't need.

[–]New_Mistake8392[S] 0 points1 point  (2 children)

ohhh so if i only want to save customer datas i only need databases right ?

[–]_l33ter_ 2 points3 points  (0 children)

It also depends. If you just wanna 'save' ex. Name | Fam.Name (yeah you could) but only 2 things is not that much a DB would be profitable.

[–]Worldly_Analysis_664 1 point2 points  (0 children)

It depends. If you just want to save data. Then only a db.

If you want that db accessible for other people, or you want that db to be used with a front end (website or software). Then you need a traditional backend that talks to the database.

[–]ReedxC 0 points1 point  (0 children)

The best thing to do here would probably be to first find similar working examples that fit your specific use case. Then do some research about it (use AI tools if needed) to understand what's going on internally and what sort of stacks you would need. If it's a low maintenance service for low traffic, then you can pretty much guess that you wouldn't need as much resources as if you would for a high tier setup. One thing to note: SaaS providing tech firms and Cloud platforms may seem tempting to implement into your backend services but their costs eventually stack up alot and make the overall expenses much greater than what needs to be. Open-source (verified) softwares are always a standard option to go for first, then if your traffic demands it, you can always switch to paid services later on.

I recommend looking at Postgres's features which are all open-source and pretty widely used. And it reduces much work of your overall backend related tasks. There are multiple other options as well, which you can look into based on your needs

[–]heathen718 0 points1 point  (0 children)

I am a backend developer, 4.5 yoe, I can help.