Event-driven design with Log Events and RabbitMQ in Golang
The adoption of event-driven architecture is on the rise as teams pursue more adaptable, scalable, and agile solutions to meet the requirements of contemporary applications. Event-driven architectures support real-time updates and streamline integration across different systems by enabling communication through standardized and structured events.
In a previous blog post, I discussed how webhooks in Auth0 can transmit events, thereby leveraging these events to initiate logic execution. In this article, I will delve into the technical aspects of this architecture and demonstrate how Go (Golang) can be utilized to construct such a system.
Main components:
Let's first have a look at the main components that drive this system.
Log Events:
Auth0 has log events associated with every activity at a tenant level. These events can be used for monitoring or audit purposes. The codes for each event can be checked out here
Webhooks:
We use auth0 webhooks to deliver filtered events to our producer. We filter these events since we are interested in only a handful.
RabbitMQ
RabbitMQ supports multiple messaging protocols, and the one we use to route messages is the Advanced Messaging Queueing Protocol (AMQP). AMQP has three main entities – Queues, Exchanges and Bindings.
Behind the scenes
When an event is triggered in Auth0, it's immediately sent via webhook to our publisher, which then publishes it based on the event type. Once published, the event goes to an exchange. The exchange directs the message to connected queues, where consumers receive it. To enable this process, we establish a channel. This channel allows us to publish messages to exchange and declare queues for subscription.
To create a new queue, we utilize the QueueDeclare function provided by the package on the channel, specifying our desired queue properties. With the queue created, we can use the channel's Publish function to send a message.
Next, we create a consumer that connects to our RabbitMQ and establishes a channel for communication. Using this channel, we can consume messages using the Consume method defined for it.
Groundwork
We use golang-auth0 management package to work on the log events and for the queue actions we use github.com/rabbitmq/amqp091-go.
Given below are the snippets:
Publishing:
A detailed structure of the log can be found here
for _, auth0log := range payload.Logs {
switch auth0log.Data.Type {
case "slo":
_, err = c.Publish(ctx, PublishRequest{
---your logic---
})
case "ss":
_, err = c.Publish(ctx,PublishRequest{
-- your logic -----
})
}
}
Exchange:
if consumeOptions.BindingExchange != "" {
for _, routingKey := range routingKeys {
err = consumer.chManager.channel.QueueBind(
queue,
routingKey,
consumeOptions.BindingExchange,
consumeOptions.BindingNoWait,
tableToAMQPTable(consumeOptions.BindingArgs),
)
if err != nil {
return err
}
}
}
Consuming:
func (c *Client) Consume() {
err := c.consumer.StartConsuming(
func(ctx context.Context, d queue.Delivery) bool {
err := c.processMessages(ctx, d.Body, d.Exchange)
if err != nil {
c.log.Error().Ctx(ctx).Err(err).Str("exchange", d.Exchange).Msg("failed publishing")
return nack // send to dlx
}
return ack // message acknowledged
},
c.queueName,
[]string{c.queueRoutingKey},
func(opts *queue.ConsumeOptions) {
opts.BindingExchange = c.queueBidingExchange
opts.QueueDurable = true
opts.QueueArgs = map[string]interface{}{
"x-dead-letter-exchange": c.queueBidingExchangeDlx,
}
},
)
if err != nil {
c.log.Fatal().Err(err).Msg("consumer: Failed to StartConsuming")
}
// block main thread so consumers run forever
forever := make(chan struct{})
<-forever
}
Thus, by leveraging webhooks in Auth0 to trigger events and employing RabbitMQ for reliable message queuing and delivery, we can build scalable and responsive applications. This approach not only enhances flexibility but also supports seamless event processing, enabling efficient handling of asynchronous operations.
I hope this article was helpful and can prove to be beneficial in your event-driven journey.
Happy coding :)
The above is the detailed content of Event-driven design with Log Events and RabbitMQ in Golang. For more information, please follow other related articles on the PHP Chinese website!
Hot AI Tools
Undress AI Tool
Undress images for free
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
How to build a web server in Go
Jul 15, 2025 am 03:05 AM
It is not difficult to build a web server written in Go. The core lies in using the net/http package to implement basic services. 1. Use net/http to start the simplest server: register processing functions and listen to ports through a few lines of code; 2. Routing management: Use ServeMux to organize multiple interface paths for easy structured management; 3. Common practices: group routing by functional modules, and use third-party libraries to support complex matching; 4. Static file service: provide HTML, CSS and JS files through http.FileServer; 5. Performance and security: enable HTTPS, limit the size of the request body, and set timeout to improve security and performance. After mastering these key points, it will be easier to expand functionality.
Go for Audio/Video Processing
Jul 20, 2025 am 04:14 AM
The core of audio and video processing lies in understanding the basic process and optimization methods. 1. The basic process includes acquisition, encoding, transmission, decoding and playback, and each link has technical difficulties; 2. Common problems such as audio and video aberration, lag delay, sound noise, blurred picture, etc. can be solved through synchronous adjustment, coding optimization, noise reduction module, parameter adjustment, etc.; 3. It is recommended to use FFmpeg, OpenCV, WebRTC, GStreamer and other tools to achieve functions; 4. In terms of performance management, we should pay attention to hardware acceleration, reasonable setting of resolution frame rates, control concurrency and memory leakage problems. Mastering these key points will help improve development efficiency and user experience.
Go select with default case
Jul 14, 2025 am 02:54 AM
The purpose of select plus default is to allow select to perform default behavior when no other branches are ready to avoid program blocking. 1. When receiving data from the channel without blocking, if the channel is empty, it will directly enter the default branch; 2. In combination with time. After or ticker, try to send data regularly. If the channel is full, it will not block and skip; 3. Prevent deadlocks, avoid program stuck when uncertain whether the channel is closed; when using it, please note that the default branch will be executed immediately and cannot be abused, and default and case are mutually exclusive and will not be executed at the same time.
Developing Kubernetes Operators in Go
Jul 25, 2025 am 02:38 AM
The most efficient way to write a KubernetesOperator is to use Go to combine Kubebuilder and controller-runtime. 1. Understand the Operator pattern: define custom resources through CRD, write a controller to listen for resource changes and perform reconciliation loops to maintain the expected state. 2. Use Kubebuilder to initialize the project and create APIs to automatically generate CRDs, controllers and configuration files. 3. Define the Spec and Status structure of CRD in api/v1/myapp_types.go, and run makemanifests to generate CRDYAML. 4. Reconcil in the controller
Go REST API example
Jul 14, 2025 am 03:01 AM
How to quickly implement a RESTAPI example written in Go? The answer is to use the net/http standard library, which can be completed in accordance with the following three steps: 1. Set up the project structure and initialize the module; 2. Define the data structure and processing functions, including obtaining all data, obtaining single data based on the ID, and creating new data; 3. Register the route in the main function and start the server. The entire process does not require a third-party library. The basic RESTAPI function can be realized through the standard library and can be tested through the browser or Postman.
How to get code coverage for golang tests
Jul 12, 2025 am 02:58 AM
Use the getest built-in command to generate coverage data: run getest-cover./... to display the coverage percentage of each package, or use getest-coverprofile=coverage.out./... to generate a detailed report and view the specific uncovered lines of code through gotoolcover-html=coverage.out-ocoverage.html. Integrate coverage report in CI: create a coverage.out file, and upload analysis through third-party tools such as codecov or coveralls, for example, using curl--data-binary@coverage.o
How to set up golangci-lint for a project
Jul 12, 2025 am 03:06 AM
The installation steps of golangci-lint are: 1. Install using binary installation or Goinstall command; 2. Verify whether the installation is successful; the configuration methods include: 3. Create a .golangci.yml file to enable/disable linters, set an exclusion path, etc.; the integration methods are: 4. Add lint steps in CI/CD (such as GitHubActions) to ensure that lint checks are automatically run for each submission and PR.
How to avoid heap allocations in a performance-critical golang function
Jul 13, 2025 am 03:06 AM
To reduce the heap allocation of critical path functions in Go, four methods can be taken: 1. Use stack variables to avoid escape; 2. Pre-allocate and reuse objects; 3. Avoid implicit escape writing; 4. Use tools to verify escape. Specifically, it includes avoiding returning local variable pointers, using value types to reduce escape, pre-allocate slice capacity, using sync.Pool to cache objects, avoiding closures to capture large structures, not assign interface types, and checking escape points through -gcflags=-m, thereby reducing GC pressure and improving performance.
