Social networks creation

When creating social networks on the basis of our platform, a whole "combine" of technologies is used. In fact, a platform is a framework (a set of software solutions) + server infrastructure that serves each individual project (proxy servers, CDNs, cluster storage systems). Speaking about the software part of the platform (about the framework), we can say that these are 1) libraries and solutions in the field of high-loaded projects; 2) libraries and solutions in the field of AI; 3) information security software solutions; 4) functional components of social networks. In the stack of technologies used, solutions based on Go, Phyton, JAVA, nodejs, php, Kotlin, Swift and other languages can be distinguished. We emphasize that our platform is a whole set ("harvester") of open solutions. It is important to note that in the field of DBMS, both SQL and NoSQL solutions are used (in combination and depending on the tasks to be solved), which provide high speed, reliability and scalability of solutions in conditions of processing large data arrays. In addition, we develop our own drivers for the used systems and DBMS, which allow us to handle a number of exceptions and work under high loads and reliability requirements.

For such highly loaded projects as social networks, we organize a whole network of CDN and storage servers. Together with partners and clients, we agree on the topology of the project, taking into account its characteristics, as well as a set of requirements - 1) in the field of reliability and safety of the project; 2) in the field of legal requirements of the countries, the users of which should have access to the project. The most important thing is that we can not only create the appropriate infrastructure for any such project, but also lease our infrastructure. Decisions in one case or another are made based on economic feasibility and ease of support. At the moment we are creating a distributed infrastructure, the platform servers are located in highly reliable data centers in countries such as the USA, Russia, Singapore, Germany, the Netherlands, Finland. The infrastructure for each project is allocated in such a way as to ensure high reliability and speed of the project applications in the conditions of audience access from around the world.

The important thing to remember here is that we are creating horizontal-scalable projects. This means, among other things, that there is no need to reserve capacities for an audience that will not be there in 1-2 months. We can quickly scale the infrastructure in accordance with the dynamics of the project's growth. Taking into account the excellent optimization of the software used and data storage methods, on average, 1 project cluster requires 3 servers. On average, you need 2 + 1 clusters for every ten millions of the project's daily audience (each user generates on average more than 100 requests to the backend). The cost of renting 1 cluster is about 1000 US dollars per month. In addition, there is the option of renting our cloud infrastructure, which may be cheaper than using your own clusters, due to synergy with other projects. In any case, technical expenses are more than compensated for on such projects - both through advertising monetization and through the monetization of internal services. The larger the audience of the project, the lower the cost of its technical operation.

Fundamentally and theoretically - "YES". All our solutions are Open Source. But in practice, this is not always beneficial for our partners, because for this it is necessary to have highly qualified specialists in the field of highly loaded projects and the technology stack used. Nevertheless, there are two options for cooperation - 1) we train and form a separate team to work with the project; 2) we continue to serve and develop the project together with you (the last option is the most profitable from the point of view of "synergy", because our solutions are developing and the cost of service may be more profitable than maintaining a separate team).

Our platform is equipped with several layers and mechanisms of protection and security, including:

• Protection of personal data:
  1) Personal data is stored in encrypted form;
  2) OWASP standards are strictly followed;
  3) Access device analysis + two-factor authentication.
• The internal pages of projects within the platform are protected from automated systems for parsing, searching and copying information - try to write a data parser, for example, from this site, and see for yourself;
• Registration of bots in the system is excluded (artificial intelligence technologies are used to analyze behavioral activity);
• If malicious activity is detected, the system automatically generates "abuses-letters" and sends them to the data centers and Internet providers participating in the attack.

This is more of an organizational than a technical issue. As for the technical side of the issue, the access to the DBMS is strictly delimited from the developers' access to the program code. Usually, developers within our platform do not have access to the nodes of the database management system. As for the organizational and technical part, for these purposes, engineers certified in the field of information security are used. As a rule, such people are the chief engineers of the project and are responsible for the most critically vulnerable part. Access to such parts of the project is highly regulated and legally protected.

Let's give an example. When you create a game in a programming language, the game itself becomes an object of intellectual property, and not the programming language in which it is written. However, in the license agreement for the game, it is necessary to indicate the objects of intellectual property that were used when creating it. For example, visual objects, programming languages, libraries released under the Apache license or the GPL. Despite the fact that the platform itself, on the basis of which social networks are created, belongs to us, the ultimate object of intellectual property is the social network itself, which has unique characteristics. This intellectual property will already belong to you. But your network license agreement must list the software you use to build it, including our platform. We will help you correctly draw up a license agreement and register your intellectual property object.

In response to the previous question, we indicated that we will help you correctly compose a product description (your social network), draw up a license agreement for users, and also go through the procedure for registering an intellectual property object. In different countries, different departments are responsible for this. For example, in Russia Rospatent is engaged in this. In the USA - the US Library of Congress. It doesn't matter where you register your intellectual property. The important thing is that such registration has legal protection in all countries.

At the end of the development and upon the delivery of the project, we transfer the access to the project infrastructure and the description for the customer's specialists. All our solutions are open source. In addition, if it is economically beneficial for the Parties, then we can continue the maintenance and development of your project together with you. There are different options for your choice.

The answer is simple:
1. QSNE is not a ready-made social network, but a framework used to create high-load projects. A set of libraries, "cubes" from which each individual social network is built;
2. Each social network is unique and has unique characteristics. All this is agreed initially and depends on the paradigm and idea put into the project. In addition, each social network has its own GUI, its own unique style - all this requires a significant amount of time to develop;
3. A social network consists of a number of components that are not developed in parallel, but strictly sequentially. For example, web part, API and backend, applications.

Of course not. Developing a social network is a multi-step process. When developing such high-load projects, a certain stack of technologies is used and a whole "combine" of solutions is used. It all depends not only on the complexity of the project, but on its component parts - for example, some projects need video streams, some do not, some projects use different applications, and some repeat the adaptive part of the project. On average, the development of a social network takes from 3 (for very simple projects) to 18 months.