Создание своего продукта - довольно рисковая идея. Есть множество подводных камней, о которые может споткнуться. Некоторые из них могут погубить проект на корню. В статье описываем проблемы, возникающие при создании сайта 

Прочитать позже

The main risks of a web project. Analysis of problems when creating a site.

The main risks of a web project. Analysis of problems when creating a site.
Creating your own product is a rather risky idea. There are many pitfalls that can be tripped over. Some of them can ruin the project in the Bud. This article describes the problems that arise when creating a site.

Creating your own product is a risky idea. There are many pitfalls that you can stumble over. Some of them can ruin the project in the Bud. 

What problems will you face when creating your site? 

Let's look at them in more detail. 

We take the risk, evaluate its criticality and probability (from 1 to 3). And we are developing measures to reduce this risk. 

Risk is something that will happen to you or another person sooner or later, here or elsewhere

Reading the table below, I don't want to think that this can actually happen. We all hope for the best, and rightly so.

But by spending very little time working through these risks, you can significantly reduce the likelihood of their implementation. And even if an unpleasant story has happened, you have already made sure that the consequences are minimal and not so critical.

Web project risk table

 Risk

Criticality

Probability

Metrica

Measures to reduce criticality

Probability reduction Measures

Site

developer Error

1

3

3

- client-side tester;
- error logging in the database

- dev & prod
without emergency frequent fills on prod
detailed documentation

hacking the admin panel

3

1

3

- for over-critical functions, require an additional password or SMS password

- SSL,
server protection (updates, port closures)
periodic change - 1P in 2 months

User complaints

2

3

6

- offer bonus for errors;
- script for handling complaints;
- improve faq and help on the system

- periodic testing,
email errors

mail Doesn't work

3

3

9

- if mail hits an exception, then send an SMS to the site owner

- periodic mail verification (testing forms in the mail)

Deposit withdrawal does Not work

3

1

3

- write instructions for users to be notified of the problem

- manual check once a week

registration does Not work

3

2

6

- write instructions for users to notify them of the problem;
- correlate Yandex Metrica data with site data

- manual check once a week

Advertising on a non-working page

3

1

3

- in advertising, make sure that ads are disabled if the page does not work

- check after placing ads
tracking metrics every 2 days

As the site grows, it works slower and slower

2

3

6

- increasing server parameters

- periodically optimize the code and site loading

Financial claims from users

3

2

 6

- it is easier to submit and process a claim for marketing purposes

- have the maximum possible metrics for fin transactions on the site

Server

the entire server Crashed

3

1

3

- restart
disabling some parts

- post server audit and monitoring of its parameters

hard drive Burned

3

1

3

- restoring the server on another server based on the image (you need an image and a typical instruction + database backup)

- making an image < br /> recovery instructions and permanent remote backup

DB dropped

2

2

4

- reloading the database

- optimization of the application code.
- search for heavy queries
indexes

IIS fell

1

1

1

- restart (or set the pool to automatically restart)

- optimizing the app code

Lost password

1

1

1

- request from the hoster

- save in a password-protected archive,
or come up with a clear hint

Constantly crashes due to loads or problems in the app

3

2

6

- performance monitoring

- constant optimization of the project;
- tracking of critical parameters on the server

server Hacking

3

1

3

- periodically changing the password.
- monitoring server parameters;
- antivirus

- server configuration by admin;
- remove all unnecessary SOFTWARE and services;
- antivirus

developer Error on the server

1

2

2

- keep a log of changes on the server;
- standard exact instructions;
- monitoring server parameters

- hire an admin

Not paid on time

3

1

3

 

- add it to Google Calendar;

- make auto-renewal

Backups are not made according to the task

3

3

9

 

- checking once a week that there are backups

DOS attack

3

1

3

 

- hosters offer this protection;
- have a second server on which to quickly deploy the project

Contractors 

Steal the customer database

3

2

6

 

- restricting access to the database via;

- dB-level access control

setting a logic bomb

3

2

6

 

- part amicably with everyone who has access to the project;

- perform code revision

Changing the fin data

3

1

3

 

- constantly track metrics and study anomalies in more detail

Delete the database and backups

3

2

6

 

- periodically upload backups from Yandex. Disk to a separate storage that is not available for developers

Selling the code to others.

3

1

3

 

- legal agreements;

- tracking the code of similar competitors (HTML markup);
- allow only trusted developers to access the code

Slow down your site

3

1

3

 

- permanent tracing of site requests

Enter the parameters for antecea.

3

3

9

 

- periodic site audit via special services

Missing contractor

3

2

6

- create documentation for the system;
- have a full-fledged backup version

- payment and motivation system;
- transparent agreements and relationships with contractors

Competitors and the external system 

Complaint to Yandex

2

3

6

- response complaint

- take an exact copy of other services and unique texts at a minimum

Court plagiarism

2

1

2

 

- work out the issue with a lawyer

Negative reviews

2

3

6

- constant processing of such reviews (there are services for searching for them)

- systematically correct what customer complaints indicate

Legal verification (e.g. processing of personal data)

 3

1 6

 

- consult a lawyer and read about such checks

You can share your risks with your partner, at least this will reduce the risk criticality for you personally. About working with a partner in a web project.

P.S. Risk awareness is a big step forward. Make a plan to minimize risks and start working in this direction. 

 

Насколько полезной была статья?
Falcon Space, автор блога

The author of the article is Ruslan Ryanov

The creator of the Falcon Space platform

Watch demo

Product marketplace Service platform Rental site CRM for B2B CRM for cargo transportation
Demo solutions can be developed and cardinally business logic for your subject area
 Demo of ready-made solutions

How do I know the budget / timeline for my project?

1. Create a project concept

Concept Template

2. Send us your concept paper

to Whatsapp +7 920 954 2217

3. We will prepare a commercial proposal with details by modules

KP example

Falcon Space Platform

This is a reduction in the cost of ownership

at the expense of fewer people to support

This is a quick change

while using the program

This is a modern interface

full adaptation for mobile devices

Component demo stand
At the stand you can see various components in action - tables, forms, modal windows, diagrams, a map, etc.
Solution demo site
Basic solutions that can be flexibly adapted for yourself - change the appearance, business logic and even the structure of the database.
Discuss the project
Ask the initial questions about the project that concern you right now. We will advise you for free and recommend the best solution.

If you like our articles, then please subscribe to our channel in Telegram - Falcon Space.
In it we will publish updates on articles and other materials regarding our platform.