Matters to be considered in building a large business system

1 things to consider in building a large business system. Remote access. Consider client and server-side connection logic. Including distribution requests, parameter agents and so on. 2. Load Balancing. The client must be connected to the server with the smallest load. If a server-side load is too heavy, because the other server side of the selection. 3. Transaction failed to recover.   If a server-side crash or network crashes, should the client be able to reroute other servers without disrupting the service? If you can, if you do a quick recovery? What is the time you can accept for your business? A second? Or is it a minute? 4. Integrated legacy systems. Code can synthesize legacy systems that already exist and write persistent business data to the database. 5. Transaction. What happens when two clients simultaneously access the same row of the database?   Or what happens when the database crashes? Affairs will free you from these afflictions. 6. Cluster. What is the status of the server container when the server crashes? Are all servers responding to this state, so all clients can use a different service? 7. Dynamic Publishing. How to update the software when the site is running? Do you need to have the machine reset? 8. Smooth stop service. How do I smooth stop a server that a client is using without disrupting the service? 9. Recording. If something goes wrong, is there a record of finding the wrong information? A record is to help us debug problem solving problem 10. System Management. Who will manage the system after a disastrous error? When a disaster occurs, we should use an administrator to manage the system 11. Thread. When there are many clients connected to the server side, this requires the server to be able to process multiple clients while simultaneously requesting. This requires that the server side has the ability to multithreading. 12. Middleware raw information. When the client is loosely coupled to the server, some types of requests have information to communicate. This requires basic information execution. 13. The entity life cycle. When the client grows, eliminates, the entity in the server has the life cycle that produces, destroys. 14. Resource sharing. When a client is no longer using the server, the valuable resources in the server are returned to the resource pool for use by other clients. 15. Safety. Server-side and database need to be protected. Users can only do what they have permission to do. 16. Cache. When there is some data for all clients to share, it is like a public object blue, it is necessary to avoid the server one time from the database to read the data. This data can be temporarily stored in the server-side memory, to avoid network congestion and the number of database samples