One major mistake I've noticed in the past are people who look for hosting before they have a developer. I really recommend that you involve your developer in the decisions you make as far as what platform, the amount of resources are going to be required and any specific software is required.
Don't just look for the cheap server, then find your developer. Find the right person, make a decision together about what exactly your goals are on the final product is. Consider whether the ability to scale out the finished product is possible. Then once all of these are decided in a concise and reasonable plan, then begin talking with hosting companies with your developer. Let the developer understand what the options are so they can get all the resources they need from said respective host or managed services provider.
Some developers don't know anything server side. I've seen people who can write damn fine applications but don't understand server limitations. Sometimes knowing what a person understands on how an application will effect system resources is more beneficial than getting a good hourly rate. If your dev writes an app that leaves constant open database connections and drives up system load, you'll end up paying them more to fix it, seen it happen. Or you'll make the mistake of thinking just throwing more hardware at the situation is the right move.
Know who you're dealing with, make sure they know more than how to code. They don't have to be a full fledged admin, but they should have a fair idea of how the system be it a Unix based or Windows OS works.
Your managed host should also know that the developer will be heavily involved with the solution, but don't give them too much access. What happens if you decide to go in another direction and no longer wish to do business with this developer. Have an exit strategy ready just in case.
Good luck out there...Excellent post.Very true.100% true. I am with you.
Don't just look for the cheap server, then find your developer. Find the right person, make a decision together about what exactly your goals are on the final product is. Consider whether the ability to scale out the finished product is possible. Then once all of these are decided in a concise and reasonable plan, then begin talking with hosting companies with your developer. Let the developer understand what the options are so they can get all the resources they need from said respective host or managed services provider.
Some developers don't know anything server side. I've seen people who can write damn fine applications but don't understand server limitations. Sometimes knowing what a person understands on how an application will effect system resources is more beneficial than getting a good hourly rate. If your dev writes an app that leaves constant open database connections and drives up system load, you'll end up paying them more to fix it, seen it happen. Or you'll make the mistake of thinking just throwing more hardware at the situation is the right move.
Know who you're dealing with, make sure they know more than how to code. They don't have to be a full fledged admin, but they should have a fair idea of how the system be it a Unix based or Windows OS works.
Your managed host should also know that the developer will be heavily involved with the solution, but don't give them too much access. What happens if you decide to go in another direction and no longer wish to do business with this developer. Have an exit strategy ready just in case.
Good luck out there...Excellent post.Very true.100% true. I am with you.