Answer the question
In order to leave comments, you need to log in
Experience in high-loaded projects: where to get it?
In almost all large companies, when applying for a job, a mandatory item is something like "development experience in large and loaded Internet projects."
The question is: where to get this experience? Do employers think that a new employee must have their own well-developed website with a heavy load? Let's suppose that I'm tired of working as an ENI in a small company and I want to go to something more promising - how will small companies have a big load on an Internet project?
Answer the question
In order to leave comments, you need to log in
Write a project and send traffic to it. Traffic is bought in shit affiliates for cheap. Of course, you can't become a guru here, but you will learn a lot about programming and caching technologies.
The next phase is to buy DDoS on the server. Here you will already learn how to optimize the network subsystem.
The budget of the whole event is 200-300 dollars plus free personal time.
A couple of options:
- Make your own high-load project.
— Join an existing open high-load project.
Or get a job in a company where there are such projects, but for a simpler position, and then “grow up”.
Make your own project, publish it on habré and catch the habr effect :)
Many of the methods described above (a site under habroeffect, under a DDOS attack or shitty traffic) do not work, because. a person gets a job, and the employer checks how long the site has been at its peak. It is highly unlikely that you will be taken in by idiots or that a habroeffect and DDoS attack will last for months.
Work in technical support of a hosting (large) company, watch, listen, shake your head.
Six months later, go to senior engineers, this is already DDoS and the load on your own skin, and so on. etc. At the same time, being friends with system administrators is an invaluable experience.
As they say, experience is acquired, but unfortunately, simply sending traffic to a site or ordering a DDoS on it is a synthetic high load and real application performance problems will be hidden under a heavy load on the I / O systems.
Performance problems are usually divided into the following:
- Problems with the I / O system (network subsystem, disk subsystem, including the http server itself, etc.)
- Problems with the application architecture.
In my experience, performance issues with an individual application are specific to that application, and diagnosing these issues requires a great deal of experience and understanding of the underlying foundations of that application.
Definitely, it is better to gain experience in a team that is already working on a highly loaded application, but to get there you will have to have a good command of the tools that are used in this application.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question