>Yes, your app/site/service needs to be built within a technical architecture that can scale…
This is where many teams drop the ball. They start building their app/service with persistence technology that really can't make it to web scale. Their plan is to "build a team to solve the big-data challenge when we hit that level of scale".
Many of these shops that decide to worry about big-data challenges later on do end up solving the problem in time so from the outside they look like a success. What you're not seeing is how the founder's equity gets eroded as he is forced to borrow money in order to build out the team to rearchitect the app in order to deal with the scale. Many VCs want for us to accept this as a normal part of building apps because it ensures that they get a major piece of the pie. It doesn't have to be this way though, we can start thinking about data access patterns in the large from the very beginning.
This is where many teams drop the ball. They start building their app/service with persistence technology that really can't make it to web scale. Their plan is to "build a team to solve the big-data challenge when we hit that level of scale".
Many of these shops that decide to worry about big-data challenges later on do end up solving the problem in time so from the outside they look like a success. What you're not seeing is how the founder's equity gets eroded as he is forced to borrow money in order to build out the team to rearchitect the app in order to deal with the scale. Many VCs want for us to accept this as a normal part of building apps because it ensures that they get a major piece of the pie. It doesn't have to be this way though, we can start thinking about data access patterns in the large from the very beginning.