My name is Ben. I specialize in helping people like you hit the Internet jackpot. You bring the ideas and vision, I bring the expertise and energy to get it done.
I am organized. I run a team of senior programmers, trained by me, who share my philosophy. We never outsource or offshore your project. You get bite-sized deliverables with verifiable progress, all paid by credit card.
I am not a big faceless company. If you call, I will talk to you. Check out my writing. See the difference for yourself. Google me. Ask around. Get to know me. I am the most experienced programmer you will find and won't break your budget.
Yawn. Getting pretty tired of the programmers and media pundits telling you that scalability should be your focus. Or maybe it’s what people say when they don’t have anything smarter to ask.
Scalability is not a property like size, shape, or lines of code. Scalability is an abstract idea that needs to be applied to a situation continuously. There is no such thing as a scalable solution. You only get a solution that can scale in a given situation. Does your situation scale in the same ways as the software was designed? That’s a really hard question to answer until you have an actual problem to talk about.
Once you have server logs measuring traffic, bandwidth, response times, data sizes, peaks and valleys, and all the rest, you can understand what your particular scaling pattern is.
It’s tempting to generalize and imagine that you’ll need to scale for “high traffic” or “high bandwidth”, but that’s seldom the case. You would be wasting your money to invest in generalized scalability before you have a specific solution.
Here’s another way to think about it: I’ve rarely built a web site that needed more than one or two servers to handle all the visitor traffic. Instead, we needed more servers for scheduled maintenance tasks, like importing data or sending masses of emails. I never know which direction a solution needs to scale, so I stay flexible as long as I can.