Some problems about large-scale high concurrent Web site architecture and database cluster

June 11, 2014, is in the process of turnover, the future career planning into a number of difficulties, want to specialize in management work, but during the tenure of the management work is only belong to team leader level, away from the project managers feel the ability to have a gap. On the technical side, there is always a hard-to-restrain enthusiasm, many years of enterprise application development, exercise the ability to translate requirements into procedural logic. Can be more popular in the current large Web site architecture and database clustering technology, very little contact. This also let me always have the heart to have the grudge, always want to explore in this direction. I think if you want to be a good architect, these things if you do not contact, you are embarrassed to tell people that you will do the system architecture.

It feels like this, you always want to be a manager, and it is impossible to become a manager, you need to use your technical ability to touch the management work, to exercise, then you may be a management staff. It's a bit embarrassing, not only that, but you also feel that sometimes you can't control the enthusiasm to study new technology.

6 years in business, awkward and difficult to choose. But think of the technology on the road to go on, after all, this to their own access to the most easy to solve the problem.

Start today and record my architect's path to growth

Today, I received a technical interview call from a company, mainly asked about the high concurrent server architecture and some problems with the database cluster.

10 million users, how do you need to architecture server to meet?

I think this question, I have not yet understood the scope, then I would like to first ask myself a few questions:

11,000 what is the number of concurrent users that may be caused?

2. What services do you use to run this Web program?

31,000 user-caused concurrency, do you need to consider the problem of server bandwidth? What should the bandwidth be if needed?

4. Do I need to load balance the server? How many servers do I need to be able to withstand the concurrency brought by 10 million of users?

5. Database cluster processing, how should I deal with, how to ensure the efficiency of access?

6. Does the Java program need to design some software architectures that deal with high concurrency based on this concurrency situation?

7. If you give me a server, how can I infer if I can complete such a server deployment?

I think that if you want to be an architect, these questions should be thoroughly understood and resolved once. You never know what's going to happen without your hands.

These 7 questions, which are recorded today, will find the answer one at a. The first step towards becoming an architect