Member Avatar for Deechickie

Hi everyone, I'm Dee
I'm new here so please excuse me if I'm asking this in the wrong forum. I must also admit that I also know very little about .NET / PHP and techie stuff :confused: so I'm after some help and guidance if possible.

I'm getting an enormous database driven site built and there are 2 main suggestions as to what it should be written in.
1. PHP / MySql
or
2. Microsoft .NET / SQL

I need the site to be very secure, FAST FAST FAST, robust and with the capabilities to be able to add to the database and site later down the track with new enhancements.
I'm also of course looking for the site to be cost effective and have been told it is much more expensive to develop a site in .NET and then there's the cost of hosting on a Microsoft Windows Server...

I just don't know. I think of 'Windows' and I think "blue screen, blue screen" :D
In your opinion, what would be best and why?

Many thanks in advance for any suggestions / advice.
Dee

  • 4 Contributors
  • 4 Replies
  • 129 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by Deechickie

Dani AI

Generated

Thread context: asked whether to pick PHP/MySQL or .NET/SQL and replies from , and favored different approaches. Rather than pick a side, a requirements-first checklist and a short practical path reduce risk and give a measurable way to choose.

Start by quantifying needs: expected peak requests/sec, concurrent users, data volume, read/write mix, SLAs, regulatory constraints, integrations, target launch date, and hiring budget. These figures drive DB design, caching, and hosting choices far more than language slogans.

Key evaluation items to compare across stacks:

  • Functional and nonfunctional requirements: transactionality, latency, complex reporting, real-time features.
  • Team and ecosystem: local hiring availability, existing libraries, vendor support, long-term maintenance.
  • Operations model: managed DBs, container/PaaS options, backups, patching, and disaster recovery.
  • Security baseline: TLS, parameterized queries/ORM use, strong password hashing, least-privilege DB accounts, logging/alerting, WAF, and regular dependency patching (see OWASP Top Ten for common app risks).
  • Extensibility: API-first design, migration toolchain, clear data versioning, and modular architecture so new features can be added without full rewrites.

Performance and scaling knobs to plan from day one: proper indexing and query plans, application-level caching (Redis/memcached), CDN for static assets, async queues for heavy work, connection pooling, and continuous load testing/profiling to validate assumptions.

A low-risk path: build a small proof-of-concept that implements the core flows in the stack that can be staffed quickly, run realistic load tests, put in place CI/CD, automated backups and monitoring, then decide based on measured results and real TCO. In practice, architecture, testing, and operational practices determine security and speed more than the choice of language alone.

Recommended Answers

All 4 Replies

Member Avatar for kad1r

If you want to secure application you can write both two languages. But .Net is much more secure than Php and also much more fast than Php.
Web application developing is not expensive in .Net. Everone told this but you can use expression editions. These are free.

Member Avatar for wilch

I'd say go for open source (PHP/MySQL or Postgres) - free everything.
- Cheaper on your bandwidth when you download the software, compared to say >200Mb for SQL Express, .NET ..., Service Packs etcs
- I have forgotten other reasons

Member Avatar for KushMishra

Hello Dee, In my point of view .Net should be preferred because its a new technology and obviously a new technology comes with some new enhancements and .Net provides you the security,robustness,reliability and faster web pages although I don't know much about PHP but still its very obvious to think that why most of the programmers have switched to .Net from PHP.
There may be many articles on the Internet and its just like a question : Whether you want to eat an orange or an apple?
What does it matter to you if you're getting something to eat and the major point is that you're not empty stomach after eating either of the two fruits i.e., your same work is done with both of the technologies.So, decision is yours whether you choose an old language or a new one.
Hope that helps.
Thanks.

Edited by KushMishra because: n/a
Member Avatar for Deechickie

Thanks so much everyone for your advice, feedback and suggestions. Much to digest (pardon the pun KM499 :)).

Thanks again!
Dee :)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.