Build StartUp. Part 2
Optimum. The most important thing.
We have two opposites: the first is a project made with the left foot, but having a solid resource in the form of budgets and traffic from the parent company. Such projects, due to the incompetence of management, as well as due to bureaucracy and separation in large offices, are done for months. In the process, dozens of different people manage to participate, after the start of the project, the managers engaged in cuddling and Tetris can change, which ultimately leads to the fact that the project unscrews its banners only at the expense of the “mother”, which drains the traffic to the unlucky child.
The second extreme is a similar project, being done by 1-2 developers in order to disperse the site and start hacking loot as soon as possible (I repeat: as soon as possible). All possible parameters are taken into account, measures are being taken to achieve optimal leafing, passive promotion (the buttons "fertilize", "post to business", the service "send link to a friend", etc.).
In the second case, unlike the first, budgets are often also slightly less bloated, which is why you have to count every penny, as well as every gig of traffic, extra megabytes of memory and disk space on the server.
Find yourself in these two examples. Good luck.
Iron and platform
Not one hour I spent in empty arguments about the platform for the website. Every sandpiper praises its swamp, and I praise mine. There is such a thing: "cost of ownership." Remember these two words and remember the next time students come to you with a proposal to make a site on Java servlets or to do something no less original. The easiest way to determine the most suitable platform is to look at statistics on hosting providers. 99% of providers offer virtual hosting on the Linux platform (FreeBSD) + Apache + MySQL + PHP + Perl.
From here and dance. Buy a regular virtual host and build a new site on it. There are hundreds of Perl or PHP encoders on the market, one or two you will surely find for the right price. And if your encoder is changing, then there will not be a big problem to find a similar one, unlike situations where exotic platforms and environments are used.
There is one more positive point: when starting your project in development on a purchased virtual host (not even VDS), you initially do not count on server resources, which forces you to make more or less optimal code and carefully consume disk space (in the opposite case, the provider’s admin will quickly report on the appetites of your crooked scripts). If at a certain moment such an economical project falls into the “mansions” in the form of a separate, well-tuned server (or cluster), then it’s an honor to praise you, because here an optimally designed and encoded website will work like a clock anyway.
There will be more.
We have two opposites: the first is a project made with the left foot, but having a solid resource in the form of budgets and traffic from the parent company. Such projects, due to the incompetence of management, as well as due to bureaucracy and separation in large offices, are done for months. In the process, dozens of different people manage to participate, after the start of the project, the managers engaged in cuddling and Tetris can change, which ultimately leads to the fact that the project unscrews its banners only at the expense of the “mother”, which drains the traffic to the unlucky child.
The second extreme is a similar project, being done by 1-2 developers in order to disperse the site and start hacking loot as soon as possible (I repeat: as soon as possible). All possible parameters are taken into account, measures are being taken to achieve optimal leafing, passive promotion (the buttons "fertilize", "post to business", the service "send link to a friend", etc.).
In the second case, unlike the first, budgets are often also slightly less bloated, which is why you have to count every penny, as well as every gig of traffic, extra megabytes of memory and disk space on the server.
Find yourself in these two examples. Good luck.
Iron and platform
Not one hour I spent in empty arguments about the platform for the website. Every sandpiper praises its swamp, and I praise mine. There is such a thing: "cost of ownership." Remember these two words and remember the next time students come to you with a proposal to make a site on Java servlets or to do something no less original. The easiest way to determine the most suitable platform is to look at statistics on hosting providers. 99% of providers offer virtual hosting on the Linux platform (FreeBSD) + Apache + MySQL + PHP + Perl.
From here and dance. Buy a regular virtual host and build a new site on it. There are hundreds of Perl or PHP encoders on the market, one or two you will surely find for the right price. And if your encoder is changing, then there will not be a big problem to find a similar one, unlike situations where exotic platforms and environments are used.
There is one more positive point: when starting your project in development on a purchased virtual host (not even VDS), you initially do not count on server resources, which forces you to make more or less optimal code and carefully consume disk space (in the opposite case, the provider’s admin will quickly report on the appetites of your crooked scripts). If at a certain moment such an economical project falls into the “mansions” in the form of a separate, well-tuned server (or cluster), then it’s an honor to praise you, because here an optimally designed and encoded website will work like a clock anyway.
There will be more.