I'm the person that gets called when a problem has stumped everyone, and a resolution is needed ASAP. I love taking control of a difficult situation, doing root cause analysis & research, getting to the bottom of things, and figuring out and executing a path forward. I've done this in small startups/tech companies to fortune 100 companies. Innovator, problem solver, adventurer. Interested in how technology has the power to improve our lives, as well as how important it is to get away from it all when possible. Interwebs, open-source, cloud, APIs, and CLIs FTW. Great at resolving complex tech issues along the OSI stack. I'm a Lead Architect and Partner at Scalable Path - a San Francisco based premium talent marketplace, where we build awesome internet things. I work with ideas, taking them from conception, strategy, architecture, delivery, and post-delivery execution. Main expertise lies in software & infrastructure architecture, but with enough knowledge to lead most other areas of a project. My current companies & startups: http://whitetalecoffee.com https://dev.eterpret.com http://fixcar.meteor.com
I didn't follow some portions of your question, and hopefully you take this well :).
"I am also considering creating a native app similar to CakePhp or Node.js" --> There are three separate concepts in there that are worth unwrapping, so probably good to talk about that first:
CakePHP is a PHP framework, comparable to Symfony/Laravel/CodeIgniter/etc.
Native apps are usually iOS, Android, Windows, etc, but can be hybrid, too (Ionic, Phonegap, React Native, etc). Connected native applications usually have a backend, which is usually written in a language like the ones mentioned above, and usually with a framework written on top of it to accelerate development.
With that out of the way, let's tackle the main meat of your question:
Can PHP be used to create a platform similar to AirBnB, Ebay, Amazon?
Answer: Absolutely!!! Just one recent example is Slack, who's backend is build on PHP (LAMP stack). Check out this tweet where they mention their stack: https://twitter.com/SlackHQ/status/426469205005705217. Another good discussion on it: https://www.quora.com/What-web-framework-s-does-Slack-run-on.
One bottom line is that choosing a technology stack is important, but more importantly is the correct and effective development on the chosen technologies. I've seen both beautiful and horrible applications written in most languages. Much care needs to be spent architecting and developing the solution, always using best practices, and considering what's the right decision for the business at hand (hint: there's no silver bullet).
My suggestion: choose whatever you're more comfortable with. Also, surround yourself with someone that has created something of the magnitude of what you're aiming for, and ask for advice.
Happy to jump on a call, show you some examples of this, and answer any questions you have!
Lots of good responses already, and to re-iterate and add my $0.02:
* Before raising funds you have to be able to easily communicate your idea, and in most cases, show some kind of traction - this can be some wireframes, click through-prototype, or even scanned napkins of that the screens look like
* At this point I'd recommend getting the idea out of your head, and into something that's an input for the next stages of development. If you're comfortable with creating wireframes, you might want to check out https://www.sketchapp.com/ in order to create all the screens that make up your idea. I've worked with founders for this stage, and it's critical to be able to export what's in your brain into something shareable/tangible
* Validate, validate, validate - once you have screens, share them. Once you have a click through prototype (i.e. Invision), share that, etc.
* Having all the screens is going to be imperative to being able to design the supporting architecture and make technology choices. i.e. is this a standalone app, or does it require a backend (DB in some server, cloud). Should this be iOS only, Android only, all of the above?
So, my prescriptive statement: export the idea from your brain into something shareable if you haven't already, get someone technical to help ask the hard questions and help with technical strategy. Get lots of validation. If it makes sense, build MVP in the most economical way possible (even this has a lot of "it depends" though).