No, the issue is very much the to-the-curb side. I plan on doing my development at home (at least to start), so I need solid bandwidth to here, even though the actual *site* will run elsewhere. (I don't enjoy trying to do major development remotely -- done it enough times to think it introduces unfun pokiness.) I've already got ISPs; the question is how I connect to them.
And Dreamhost isn't an option. This isn't an ordinary website: this is going to be a fairly high-power AJAX/Java application. That in and of itself lets Dreamhost out, since they explicitly *don't* support servlets. (Unless you are doing dedicated hardware, which pretty much misses the point of Dreamhost.)
Keep in mind, this isn't a personal project. I'm building something that is *intended* to have a million daily users in a year's time. (No, I'm not necessarily expecting that fast a growth curve -- but it's plausible, and I want to be able to handle it if it happens.) So rapid scalability is absolutely key here, from the architecture on up. Heck, one of the reasons I'm planning on Hibernate for the middle of the DB layer is so that I can switch from MySQL to Oracle reasonably quickly, should that prove necessary...
no subject
And Dreamhost isn't an option. This isn't an ordinary website: this is going to be a fairly high-power AJAX/Java application. That in and of itself lets Dreamhost out, since they explicitly *don't* support servlets. (Unless you are doing dedicated hardware, which pretty much misses the point of Dreamhost.)
Keep in mind, this isn't a personal project. I'm building something that is *intended* to have a million daily users in a year's time. (No, I'm not necessarily expecting that fast a growth curve -- but it's plausible, and I want to be able to handle it if it happens.) So rapid scalability is absolutely key here, from the architecture on up. Heck, one of the reasons I'm planning on Hibernate for the middle of the DB layer is so that I can switch from MySQL to Oracle reasonably quickly, should that prove necessary...