Database selection of "large ticketing system" and "physical e-commerce system"

Source: Internet
Author: User

Discussion please move to:

Related articles:

Have you got the tickets today? --On the "Mass Transaction fast Processing" system of the e-commerce site from the Ministry of Railways site

Cannot simply apply "physical e-commerce system" to "large ticketing system" to do demand analysis

"Large ticketing system" and "physical e-commerce system" have great differences in the impact on consumers when they are unable to provide goods (services)

Differences and linkages between system boundaries of "large ticketing system" and "physical e-commerce system"

"Large ticketing system" and "physical e-commerce system" analyze various business forms according to the system boundary

Differences and linkages between "large ticketing system" and "physical e-commerce system" in payment

Difference and connection between "large ticketing system" and "physical e-commerce system" in malicious orders

Security problems of username and password in large ticketing system

Security problems introduced by the characteristics of large ticketing system

Big difference between "large ticketing system" and "physical e-commerce system" in "inventory" calculation

Differences in access management between "large ticketing system" and "physical e-commerce system"

Relationship and misunderstanding between "large ticketing system" and "physical e-commerce system" in relation to other departments of enterprises

The impact of "large ticketing system" and "physical e-commerce system" and other departments ' Dependencies on project management

The handling of machine malicious access in the "large ticketing system"--Verification code

The handling of malicious access in the "Large Ticketing system" section

Database selection (or persistent storage selection of structured data) is a problem that almost all information systems need to consider.

An information system in the development process from small to large, at different stages of development needs of the database is also different.

When the information system is in the smaller 0 basic stage. The database is usually selected according to the characteristics of care. The assumption is that CMS, Web 1.0, Web 2.0 and other applications with low quality of database services, can choose to Mariasql (MySQL was acquired, by the community development of the new version number) represented by the open source free database. The assumption is that the OA system for the database service quality requirements of the application, you need to consider the adoption of enterprise-class commercial database. Not only the database program itself can provide a richer function, can guarantee a higher quality of service, at the same time and the implementation of the hardware has a good match (such as in disaster tolerance, fault tolerance).

However, enterprise-grade commercial database with the growth of the system size, will gradually expose the shortcomings, this is not to say that enterprise-grade commercial database has any innate defects, but with the scale of growth, those dependent on the enterprise-class commercial database itself characteristics. Will gradually be unable to meet the requirements, at this time need to develop their own system of corresponding functions. As more and more functions are replaced. Enterprise-grade commercial databases are only being left with purely structured data storage.

The price/performance ratio of enterprise-grade commercial database is too low at this time. When the system developed to this stage. will have to replace enterprise-grade commercial databases, which, of course, will pay a corresponding price. In detail, the so-called "go to the IoE".

So for large systems. When considering what database to use, you should first consider which features are self-developed and which feature depends on the database. The database is then selected according to the combination of attributes that depend on the database.

(Go to the IOE concept of a matter of opinion.) This article is used only to illustrate the issues discussed in this article, not to expand this)

Contact QQ 443089607:huzhenghui
Product Manager Please add QQ Group 189763636 Group 07 period axure7pm Interaction

Database selection of "large ticketing system" and "physical e-commerce system"

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.