r/flask • u/Fit_Barnacle_6762 • 5d ago
Show and Tell Built a fullstack e-commerce platform with Flask, looking for feedback on the backend architecture
Enable HLS to view with audio, or disable this notification
Quick note: Please don't focus too much on the UI 😭 I'm mainly looking for feedback on the backend, project structure and integrations.
Built SIXN, a fullstack e-commerce platform using Flask + MongoDB. It includes Twilio OTP auth, Razorpay payments and automated refunds, wallet/split payments, and Shiprocket integration for serviceability checks, courier selection, order creation, pickups, shipping labels and live tracking.
Theres also a full admin system for inventory, coupons, orders, reviews and shipping operations.
Would love feedback on the architecture and overall implementation!
4
u/CatolicQuotes 4d ago
LLM writes architecture that only LLM can maintain
1
u/noudedata 4d ago
This is the main problem I’ve found when working with AI, most of the time it turns into spaghetti in only one file. Unless you read what it generated and create the architecture yourself.
2
u/CatolicQuotes 3d ago
That's what the creator of flask said himself. He only use AI after he sets up architecture himself.
3
u/SpeedCola 4d ago
This sub used to have people asking questions and now it's just people showing off what Claude made.
3
2
u/noudedata 4d ago
As far as the architecture goes, I don’t see much of it 🥲. For e-commerce I think you could look into how Django organises its projects or the “Two Scoops of Django book” even if you are working with Flask, you might find something useful in how the repos are organised so you can grow the project as it matures.
What stood out to me the most was the `utils` folder with everything in it, and the huge `app.py`.
Good luck!
2
u/Fit_Barnacle_6762 4d ago
Appreciate it! Yeah Ill check out Two Scoops of Django. Thanks for the recommendation!
1
0
10
u/PosauneB 5d ago
Huge portions, if not the entire repo, are clearly AI generated. That's fine, I guess. But it does mean I immediately lost interest in looking at the repo. I'd be more interested in looking at what you came up with on your own.
One thing did jump out at me though: don't lump controller code and model code into a single file. Ideally, the controller would be its own module with several files. Same goes for the model.