2

!rant

A question to all the guys and girls that launched a startup: How powerful was your infrastructure at the beginning? How many requests per seconds did you encounter after the first few weeks after the launch? Did you distribute the workload to different systems in the first place or was that something that was done later?

I am currently working hard in my freetime to get my first project done. As it's still a side project, that I am working on in my freetime, I want to make the launch as smooth as possible. I imagine that it's really hard to make serious changes to the whole design, just because the initial approach doesn't scale well enough. So I am currently in the process of stresstesting the whole infrastructure. But during the stresstest I realized that I don't really know what I should aim for.

What I also want to avoid is, that I am wasting my time on creating a large infrastructure of database servers, caching instances and load balancers that isn't really necessary for the initial launch.

Would really love to hear your experiences on that.

Comments
  • 1
    From an infrastructure view make it scalable, separate as much as possible.

    I haven't been part of a startup but I do work on scale out projects. Modularity is key, no point tying yourself to one web server unless you are confident that you won't hit its limits.
  • 1
    @philcr yeah that's also my approach, but I am unsure how powerful that infrastructure should be in the beginning. I don't want to invest a lot of money in the infrastructure, not knowing if even somebody wants to use it.

    I would really be interested in some figures to see how others approached the launch :)
  • 2
    Use Heroku and Mongo DB( integrated with Heroku ) bootstrap it.

    You can simply pay more to scale it when the time comes. Odds are you'll never get to a point where it's too expensive, and it's by far the easiest way to do this
Add Comment