What is the best accommodation to maintain a system?

Asked

Viewed 148 times

-2

Hello.

We are developing a Task Management system (in the company where I do internship) and now we will need to host the system on the web.

  • The system is made with a lot of Javascript/jQuery, PHP and uses the Mysql database.

  • The system will be used by about 100 users and the interactions will be done practically all the time (daily).

My question is this::

What kind of hosting plan will we have to look for to store the system without slowing down, processing failures and crashes ?

  • We are starting in this area of Web Development and we do not have much notion of hosting systems.

The image below is shown in a hosting plan that offers its services.

inserir a descrição da imagem aqui

Among the options shown in the image, we should base ourselves on that when choosing the package of the hosting plan ?

If you can explain each field (which is shown in this image), I would be grateful.

Below is a system image.

inserir a descrição da imagem aqui

This system will be used by several users and will always have interaction with the database (Mysql) using jQuery/Javascript and PHP.

I would like to have a sense of which "accommodation package" to use. Because we don’t know much about it. D

They mentioned that the question was out of scope, but I think it is within the scope of the "Hosting" TAG, which exists here in Stack.

Thanks in advance. Thank you!

php javascript mysql

  • What is the most expensive user action (CPU and Memory) for the served? In this action, how many Kbs did the server send to the client? What is the bank’s growth forecast for the next few years? Does it have file upload functionality (e.g. pdf, word, excel...)? These answers will help you in part of the problem.

  • The database will increase in the future (next months) and will have file upload functionality, but will not be very constant.

  • 3

    Tags do not define scope. The site is only about programming, and tools when used for programming itself. IT support, hosting, things that depend on opinion, even if a programmer uses (such as the ideal height of the monitor, suitable keyboard and "best screen background color to program") are not in scope.

  • So what are the tags and what could I talk about using the "hosting" tag? It’s just a clarification...

1 answer

3


Hello, Thiago, all right?

Below I provide a brief explanation about each of the plane information that is seen in the image, they are almost identical to the notions of functioning of a computer, with the difference of being "virtual".

Operating system: refers to the system that will be used by your server: Windows Server or a Linux distro (usually Debian, Ubuntu...).

vCPU: is a virtual processing unit, the virtual processor allocated for your shared hosting.

Memory RAM: is the memory that will be consumed by the web server (such as Apache), the execution of PHP, DBMS and all other routines such as firewall, task scheduler and etc.

Disk space: is the memory that will be consumed by the files on your site, that is, your PHP/HTML pages, image files, CSS style sheets and JS scripts, for example.

Speed (dedicated link): it may be that the hosting is even using with another meaning, but I do not see other than the speed of the server access to the internet, this would be like the speed of your internet plan.

IP dedicated: a unique IP number unique to your virtual server.

Backup: certainly a file copy service and automatic database offered by hosting.

Anyway, simply put, see as being the information of a computer, because in fact they are, the difference is that in shared hosts everything is virtual, IE, you will not have a machine with 3 vCPUs (virtual processors)rather the right to use a higher processing speed that is provided by one or more physical processors and divided between various hosting accounts such as your.

My recommendation is that you do not worry about this at first, of course performance is important, but right away, being new in the area, publish your project and constantly analyze the use of resources and how each new user that enters consumes them.

Think about it: isn’t it much better to publish your application and over the 2-3 week period evaluate the resource consumption by the server? If there are bottlenecks or if you’ve chosen a plan "that’s too much"?

Browser other questions tagged php javascript mysql

You are not signed in. Login or sign up in order to post.