broker

README

broker

消息队列抽象接口设计
常用的消息队列支持一下几种模式

• 点对点模式:一个消息只能由一个消费者处理,可以有一个或多个消费者竞争处理

• Pub/Sub模式:一个消息可以被所有的消费者处理

• 复合模式:先是Pub/Sub，然后再分组，这样可以增加并发处理能力

• 有些支持消息路由

• 有些消息队列支持事务,但是大部分是不支持的

• API设计上如何支持多个订阅?是需要每个订阅一个goroutine么

• 应用场景:https://www.alibabacloud.com/help/zh/doc-detail/112010.htm?spm=a2c63.p38356.879954.22.18fefc6curWPID

• https://www.alibabacloud.com/help/zh/doc-detail/29532.htm?spm=a2c63.p38356.b99.2.5b906513XS0aJR

• https://www.cnblogs.com/hzmark/p/orderly_message.html

Documentation

Index

• type Broker
• type Option
• type Options
• type PublishOption
• type PublishOptions
• type SubscribeOption
• type SubscribeOptions

Types

type Broker

type Broker interface {
}

Pub/Sub接口

type Option

type Option func(*Options)

type Options

type Options struct {
	Addrs     []string
	Secure    bool
	TLSConfig *tls.Config
	// Other options for implementations of the interface
	// can be stored in a context
	Context context.Context
}

type PublishOption

type PublishOption func(*PublishOptions)

type PublishOptions

type PublishOptions struct {
	// Other options for implementations of the interface
	// can be stored in a context
	Context context.Context
}

type SubscribeOption

type SubscribeOption func(*SubscribeOptions)

type SubscribeOptions

type SubscribeOptions struct {
	// AutoAck defaults to true. When a handler returns
	// with a nil error the message is acked.
	AutoAck bool
	// Subscribers with the same queue name
	// will create a shared subscription where each
	// receives a subset of messages.
	Queue string

	// Other options for implementations of the interface
	// can be stored in a context
	Context context.Context
}