|
Hi, Newbie here. I've spun off my university project into a web prototype that I want to launch eventually, and I've submitted it in the current YC batch. I'm pretty good with it so I've got it hosted, put up a fairly basic (1 person usable) proof of concept prototype. It's also innovative (sorry guys, can't give too many specifics yet). However, I'm not experienced when it comes to rolling out on a mass public scale technically i.e. hosting scalability (cloud?), security, concurrency, redundancy, integration with facebook etc. With the odds for YC against me (as a single founder, not on the strength of my application I would hope), I need a little advice on how to proceed ahead for a Plan B case. I have experience with databases, websites and authentication and I could realistically scale the technology to a private beta phase... beyond that, having someone experienced on the deploy side would be incredibly useful. How do new startups deal with this? ps: If you're an HNer in/around London (England) with strong Flash (AS3) skills, taken a web 2.0 from prototype to public beta, (massive bonus if you can do iPhone apps), and keen to get involved in an innovative concept, please do get in touch! |
Second, each of the points you're looking to learn about are simply a matter of googling a bit. Without knowing your backend, it's hard to tell you to either go use Heroku, or slicehost, or ec2. Security is highly context-dependent. And so on.
Anyway, it's very cool that you've taken your university project and have built on it, so congrats on that front. Often times the best ideas come from that setting.
Just share a bit more with us :)