Home  >  Article  >  Backend Development  >  A brief discussion on two architectures and core architecture design

A brief discussion on two architectures and core architecture design

巴扎黑
巴扎黑Original
2017-06-12 16:06:474027browse

1. Architecture design 11. The master and slave servers can use different storage engines. InnoDB is used on the Master, taking advantage of advanced features such as transactions and row-level locks. MyISAM is used on the Slave, which has better read performance, saves memory, and is easy to back up. You can also use different data types respectively, such as varchar on the Master and char on the Slave. This not only saves space, but also makes use of the static table features of MyISAM. 2. In the M-S-Muti Slave solution, the relay slave can also use the BlackHole storage engine. The BlackHole storage engine only records logs and does not write data. Using this feature can greatly improve the performance of relay logs. However, this solution does not support Replication under GTIDs, because BlackHole can only be used with binary logs in StateMent format, and both Row and Mixed formats are not available. 3. In the design of separation of reading and writing, the master-slave server can adopt different indexing schemes. Master can only retain indexes such as primary keys or unique indexes that guarantee data relationships. Salve does index optimization for queries.

1. MySQL-Concrete analysis of two architectural methods to improve Replication performance

A brief discussion on two architectures and core architecture design

##Introduction: 1. Architecture design 11. The master and slave servers can use different storage engines. InnoDB is used on the Master, taking advantage of advanced features such as transactions and row-level locks. MyISAM is used on the Slave, which has better read performance, saves memory, and is easy to back up. You can also use different data types respectively, such as varchar on the Master and char on the Slave. This not only saves space, but also makes use of the static table features of MyISAM. 2. In the M-S-Muti Slave solution, the relay Slave can also use BlackHol

2. Analysis of the differences, advantages and disadvantages of C/S and B/S architecture, architecture _PHP Tutorial

A brief discussion on two architectures and core architecture design

Introduction: Analysis of the differences and advantages and disadvantages of C/S and B/S architectures , architecture. Analysis of the differences, advantages and disadvantages of C/S and B/S architectures. Architecture 1. C/S architecture 1. Concept C/S architecture is a typical two-layer architecture. The whole process is Client/Server, that is, client server. Terminal frame

3. Analysis of the differences, advantages and disadvantages of C/S and B/S architecture, architecture

Introduction: Analysis of the differences, advantages and disadvantages of C/S and B/S architectures, architecture. Analysis of the differences, advantages and disadvantages of C/S and B/S architectures. Architecture 1. C/S architecture 1. Concept C/S architecture is a typical two-layer architecture. The whole process is Client/Server, that is, client server. End frame

4. Analysis of the differences, advantages and disadvantages of C/S and B/S architecture_php example

Introduction: C/S and B/S are two very common software architecture methods. Both can perform the same business processing, and can even use the same method. implement a common logic. That being the case, why distinguish one from another? Then let’s take a look at the differences and connections between the two.

5. Innodb_flush_log_at_trx_commit and sync_binlog parameters under MySQL HA architecture

##Introduction: HeartBeat + DRBD and MySQL replication are many A method commonly used by enterprises. For data integrity and consistency issues, these two architectures need to consider 2 things

6.

mongodb distributed read and write operations (1)

A brief discussion on two architectures and core architecture design

#Introduction: The mongodb shared cluster and replica set architectures are widely used. In the production environment, these two architectures are increasingly put on the agenda with the growth of business volume, data volume and high availability requirements. The system architecture is slowly shifting from a single machine to a cluster architecture, and all underlying facilities are clustered. 1. Distributed read operation introduces how sharded clusters and replica sets affect reading

7.

Analysis of the differences, advantages and disadvantages of C/S and B/S architectures

A brief discussion on two architectures and core architecture design

Introduction: C/S and B/S are two very common software architecture methods. Both can perform the same business processing and can even implement common logic in the same way. That being the case, why distinguish one from another? Then let’s take a look at

8. innodb_flush_log_at_trx_commit and sync_binlog parameters _MySQL

Introduction: HeartBeat + DRBD and MySQL replication are commonly used methods by many enterprises. For data integrity and consistency issues, these two architectures need to consider two important parameters innodb_flush_log_at_trx_commit and sync_binlog parameters.

9. Analysis of the differences, advantages and disadvantages of C/S and B/S architecture_PHP

A brief discussion on two architectures and core architecture design

Introduction: C/S and B/S are two common software architecture methods. Both can perform the same business processing, and can even use the same method. implement a common logic. That being the case, why distinguish one from another? Then let’s take a look at the differences and connections between the two.

[Related Q&A recommendations]:

android - Some confusions about APP architecture design

The above is the detailed content of A brief discussion on two architectures and core architecture design. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn