Press: For payment system, who is TOP1? - Ali, a more accurate point Alipay! Research system, we must first study the industry TOP.
Alipay is a pacesetter Chinese payments industry, whether operational capacity of product innovation are leader in China pay the forefront of the industry, as the basis for the system to pay business complexity and stability is fundamental if the payment service timely fast and secure processing of paper collected Alipay system architecture diagram includes: liquidation, customer service, processing, financing, financial companies and so on for other payment reference!
This collection of network information, transferred from [pay] circle, the latest system architecture information, although not part of Alipay but as the leading payment industry, the system architecture is still worth learning!
Alipay System Architecture Overview
Typical treatment default
Funds processing platform
Financial Accounting
Payment Clearing
Accounting center
transaction
Flexible Affairs
Alipay open source distributed messaging middleware --Metamorphosis (MetaQ)
Metamorphosis (MetaQ) is a high-performance, highly available, scalable, distributed message middleware, like LinkedIn, Kafka, with sequential write message storage, throughput and large local and XA transaction support and other characteristics, suitable for high throughput, order message, broadcast and log data transmission and other scenes, in Taobao and Alipay has a wide range of applications, it is now open source.
Metamorphosis is a Java Taobao open source messaging middleware. About messaging middleware, you should have heard the JMS specification, and some open source implementation, such as ActiveMQ and HornetQ and so on. Metamorphosis is one of them.
Metamorphosis is the origin of my open source MQ-- from now on linkedin transferred to the apache kafka start learning, which is a very unique design of the MQ system, which uses a pull mechanism, rather than the general MQ-push model, which use a lot of a zookeeper do service discovery and offset storage, built on the idea I really appreciate and agree with, it is strongly recommended that you read the design document, on the whole metamorphosis of design is saying is exactly the same. But why do you need meta it?
Under brief summary of reasons for me to re-write the meta:
-
Kafka is the scala write, I am not familiar with the scala, and the development of the entire community kafka too slow.
-
有一些功能是kakfa没有实现，但是我们却需要：事务、多种offset存储、高可用方案(HA)等
Meta相对于kafka特有的一些功能：
-
文本协议设计，非常透明，支持类似memcached stats的协议来监控broker
-
纯Java实现，从通讯到存储，从client到server都是重新实现。
-
提供事务支持，包括本地事务和XA分布式事务
-
支持HA复制，包括异步复制和同步复制，保证消息的可靠性
-
支持异步发送消息
-
消费消息失败，支持本地恢复
-
多种offset存储支持，数据库、磁盘、zookeeper，可自定义实现
-
支持group commit，提升数据可靠性和吞吐量。
-
支持消息广播模式
-
一系列配套项目：python客户端、twitter storm的spout、tail4j等。
因此meta相比于kafka的提升是巨大的。meta在淘宝和支付宝都得到了广泛应用，现在每天支付宝每天经由meta路由的消息达到120亿，淘宝也有每天也有上亿的消息量。
Meta适合的应用：
-
日志传输，高吞吐量的日志传输本来就是kafka的强项
-
消息广播功能，如广播缓存配置失效。
-
数据的顺序同步功能，如mysql binlog复制
-
分布式环境下（broker,producer,consumer都为集群）的消息路由，对顺序和可靠性有极高要求的场景。
-
作为一般MQ来使用的其他功能
总体结构：
内部结构：
