Member Avatar for pooja.naik.1297

Aplication developed in PHP is more stronger than Codeigniter Aplication ?

  • 5 Contributors
  • 5 Replies
  • 381 Views
  • 9 Hours Discussion Span
  • Latest Post Latest Post by Member #120589

Dani AI

Generated

Short answer: it depends what you mean by “stronger.” Raw (core) PHP can be faster for tiny, single-purpose pages because there’s less framework bootstrap to run; but a well-architected CodeIgniter app is usually easier to maintain, more consistent for teams, and gives you built-in helpers (routing, validation, caching) that avoid many common security/quality mistakes. See the CodeIgniter project history and community stewardship for context. (codeigniter.com)

If a CodeIgniter build is noticeably slower than a hand‑rolled script, measure first rather than rewrite. Start with CodeIgniter’s Profiler to see queries, timings and memory, then use a deeper profiler (Xdebug, Blackfire, New Relic) to find hotspots. Only after you know where time is spent should you consider ripping out the framework bits. Example: enable CI’s profiler during dev with the output library. (codeigniter.com)

Quick, practical checklist to diagnose & speed up a slow CI app:

  1. Profile: locate slow controllers, DB queries and libraries. (codeigniter.com)
  2. Cut autoloads and remove unused libraries/helpers; lazy-load heavy services.
  3. Optimize DB: add indexes, reduce N+1 queries, enable query caching where useful. (codeigniter.com)
  4. Use CI output/page caching or fragment caching for pages that can be static. Example call shown in CI docs. (codeigniter.com)
  5. Run recent PHP with an opcode cache (OPcache) and recommended settings — upgrading PHP (7→8+) and enabling OPcache typically yields large, low‑risk speed gains. (php.net)

Practical rule: if the project is small, single‑purpose, and you control every line, a tight core PHP solution can be fine. For anything that will be maintained, extended, or worked on by others, a framework like CodeIgniter normally wins in the long run — but always profile and fix hotspots before choosing a full rewrite. (phptherightway.com)

(References used above: CodeIgniter docs and history, CI profiling & caching pages, PHP release notes, OPcache manual, and profiling tools.)

Recommended Answers

All 5 Replies

Member Avatar for hericles

Codeigniter is a PHP framework though. Are you asking if PHP is better than PHP?
Having said that: if you use a framework you can be limited by the functionality that framework exposes. Coding a solution yourself does give you complete control but at the tradeoff of simplicity or efficiency (as you don't need to do as much background coding yourself).
Is that what you were asking?

Member Avatar for sanjay@srvmedia

CodeIgniter is an Application Development Framework - a toolkit - for people who build web sites using PHP. Its goal is to enable you to develop projects much faster than you could if you were writing code from scratch, by providing a rich set of libraries for commonly needed tasks. CodeIgniter lets you creatively focus on your project by minimizing the amount of code needed for a given task.

Member Avatar for Adrian_5

Speed wise, any application written directly in PHP, if written right, is faster than an application written using a framework. If by "stronger" you mean "without bugs", there is a chance that a framework, whatever its name is, could be stronger...

Member Avatar for pooja.naik.1297

Thank you Adrian..Thats wat i expecting...
Because I came across those kind of situation..The Application build in core php was faster than Codeigniter application, So i Had a doubt.

Edited by pooja.naik.1297
Member Avatar for Member #120589

It depends on what you're doing. A framework has the advantage of having 'experts' develop certain modules that you just 'use' - so a lot of the hard graft has been taken out of developing a solution. Unfortunately, most frameworks have a steep learning curve and are sometimes beyond the ability of a beginner - especially those not familiar with OOP and an MVC-type way of working. So, you have the advantage of gaining good security for your level of experience, but you are also at the mercy of 3rd party developers if you don't understand what they've written in their classes.

Codeigniter is one of the more accessible frameworks and it has a loose way of working with MVC - which can be a good or a bad thing.
Now for the not-so-good news - EllisLabs, the creators of CodeIgniter are trying to get shot of it. They haven't released a news item since August 2013, which may be a bit of a worry. There is a thriving community, so patches and fixes may be produced, but major upgrades don't look very likely at this time. I may be wrong, anybody heard differently?

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.