Question

Aoa developers here !! I’m going to start developing my product very soon in sha ALLAH. Need recommendations from developers. I expertise in mobile development. But for this product I have to start with web. Now I want something like olx, pakwheels model to start with which can be converted into aliexpress, flipkart like marketplace after year or two may be. Target audience : Pakistan initially In web development I have some knowledge of php basic scripting and java j2ee. There should be complete separation of backend and frontend so If I have to change backend completely, It can changed. And also do not want to trust any unknown developer to develop it for me (specially backend)

Answer 1

F

Answer 2

Go with RoR

Comments

:P

---

Ror is slow

Answer 3

Go with native script

Comments

Nativescript?

Answer 4

I wish you all the best for your product/products , ALLAH bless you

Comments

Thank you

Answer 5

You could also look at backend as a service to avoid backend dev. Grapcool and mobilehub are some of the options

Comments

Website hi bnani ha abhi. Mobile app bd me

---

Rails is the way to go

---

Muhammad Bilal Iqbal e-commerce wala kam hojayga like daraz?

---

Yes. Look into spree framework built on rails.

---

thanks nigga

---

Why so racist

---

Rails is slow

Answer 6

What about front end in angular and back end in php? And yes its good to have both end as separate. For this first draw architect according to your needs and with out this don't go for anything further.

Comments

Pho framework? Yes paperwork hi kr raha hn abhi

Answer 7

If you are short on time and want to write APIs as quick as possible, then Ruby on Rails can be used to make a rapid and quality Prototype/Minimum Viable Product

Comments

Secure for ecommerce and scalable also? And if no issue of timing?

---

Dont think of scalability at first

---

Application will be secure if best practices are used. You can always afford to switch to a stack that matches your requirements at that time when the product is stable financially. Scalability should not be a worry at the time of inception of a product.

---

Muhammad Bilal Iqbal as far I remember, you used to tell me to have a scalable architecture from start

---

That has nothing to do witg framwork That was abt server architecture

Answer 8

Front end React Redux Backend NodeJS(Express) Or Backend PHP(Laravel or Code Ignitor)

Answer 9

Whatever framework and lang you have grip on, unless you want to learn some new technology. Mostly performance bottleneck comes at storage level so go with better database as per your need and use hybrid approach, I.e choose SQL and No-Sql wisely as per your need. If you want to learn the consider micro services, and choose any language or framework you like Keep your API's 100% indenpendent and loosely coupled and avoid Session based authentication and use Token mechanism like JWT. For frontend it's always good to use some binding framework like React, Angular, all are good and you can choose on your liking. For saving\serving media use cloud services e.g Cloud Front, or Google Cloud storage etc don't try to serve from your Code instance. Don't try to re-invent wheel So any language you choose always use a framework and follow its practices, don't try to do custom stuff unless you really need.

Comments

Agree on all points except saving token in browser. It is not secure.

---

Internally sessions are also managed by a session Id which is saved inside browser or cookies and server needs them to know who is who So all depends how server and clients make this session ID or API token secured , how the transfer and validate data , i.e HTTPs and encryptions etc

---

Session ID can be secured by csrf token. You will have to do the same for api otherwise anyone can read token from cookies and do his thing. If you add support for csrf token in your api then how is it different from session? Why reinventing the wheel?

---

Not reinventing wheel, just talking from perspective of how world is moving, specially in regards of distributed services and microservices where diff modules need authentication but maintaining session on all servers is hard. By the way I just replied for saving in browser, Anyways when it's just one server and if it's just web then using session is no problem. Take care.

---

You are right that world is moving towards api but still some improvements are needed that's why big companies like Facebook AirBnB etc are not willing to take risk to save api token in browser. Well I have experienced these problems that's why I also replied for just saving in browser part. Good bye.

Answer 10

launching a product.... impressive ... best of luck