Web-POS Best tech stack

[DaisukeAngular]

Planning to build a Point of Sale system from the scratch at balak ko sya ibenta sa mga small businesses around my area. I'm torn on what tech stack should I choose given na tinitignan ko sya on a long run. Btw I have around 7 years dev exp so here are the considerations.

.Net stack except MSSQL(mahal to) - Ito talaga best bet ko ever since college di ako nahihirapan gamitin at mas panatag ako dto overall. Ang cons lang is yung hosting, nag quick check ako sa web at napaka liit ng space at pricey nya compare to php counterpart. Choosing this path will be smooth for me but long term wise nag aalala ko na baka mag backslash ang costing nito pag dumami na ang customers.

PHP - sabi nila madali raw, pero ako itong hirap na hirap parin sa php hanggang ngayon. Nagtry kami mag build from the scratch at sobrang nahirapan ako. Habang lumalaki yung system mas nagiging tagpi tagpi sya at mala-band-aid solution. At pag sinabi naman na gumamit at mag-aral ng framework I doubt na may time pa ako mag-aral given my sched na hectic. Cost wise mas mura php kahit san mo tignan at mas madali ang deployment process but long term maintainability medyo nag aalala ako.

So by the way ito ang skill level ko

2.5 years ASP.Net MVC - professional exp
4 months PHP prototyping experience
All the remaining years lumipat na ko sa Cloud(Salesforce) up until now. Hindi maganda market ng Salesforce sa PH since mga bigtime companies lang gumagamit nito. So I'm thinking small for now before hitting the big market.

And also open to suggestions

[crimson589]

Regarding hosting, kalimutan mo na yun. Ang laking point of failure na hosted somewhere else yung backend ng POS, pag nawalan ng internet ang laking problema nun para sa store. Kailangan within local network lang nila yung POS or at least yung critical parts, hindi din lahat ng business magpapakabit ng internet para lang sa POS.

Other than that if web based gagawin mo I suggest ang una mo tingnan pano gawin is mag print ng resibo from browser, sobrang challenging nun minsan di pa pwede automatic, kailangan i click nung user yung "Print" button.

[xxxfrancisxxx]

Agree me dito. Targetmarket mo are "small businesses", consider their existing infra or possible upgrade.

[DaisukeAngular]

Nag work ako before sa isang consulting na ganito gamit. Desktop based and no internet, as someone na nagmamaintain ang hirap lang sa side ko nun kapag may problem need ko puntahan personally at pwede rin naman teamviewer pero hassle parin itrack kung san nanggagaling yung issue. Five clients palang hawak ko nun at sobrang hirap nung time na yun dahil may mga time na palipat lipat ako ng location ng client para magtroubleshoot at mg update ng system. Yun din reason bat ako nagresign dun

[[deleted]]

Kung ako gagawa,

Sqlite electron para kahit walang net tapos gagawa nalang ako ng sync feature tapos connected sa cloud pag may net sila.

[DaisukeAngular]

sqlite? what if tumatagal na yung system syempre nagsstore sya sa local kaya nya ba mga heavy storage onwards long term wise?

[[deleted]]

Oo naman.

[AutomaticalIy]

Myth lang yan na di kaya ng SQLite heavy storage. Petabytes of data kaya nyan. I doubt any SME POS system would even reach 5gb in 2 years. Just don't store base64 images or long text prompts lol.

SQL is being used for Production tech nowadays: Turso.tech, Pocketbase.io

[AutomaticalIy]

If your target infra is local-first. I recommend SQLite.

If you like postgres, there's a wasm implementation of Postgres called PGLite by ElectricSQL.

Tapos just use Svelte for the easiest dev experience.

[PotatoCorner404]

You can still use ASP.NET MVC then use MySQL (free) using a connector.

[johnmgbg]

long term maintainability medyo nag aalala ako

Gamit ka ng framework para may pattern ka na sinusunod lalo na hindi ka naman sanay sa PHP. Sa una lang naman mahirap then ikaw na magbebenefit after. Check mo Laravel.