To combat this concurrent work, you would need a system to synchronize fetching or rendering of the data. Fortunately, there is a golang library called groupcache which can be used to resolve the thundering herd issue and improve on the remote cache implications mentioned above.
Since my internet foo failed me, and the only workable example of an H2C client I can find was in the actual go test suite, I’m going to lay out what I discovered about H2C support in golang here.
At Mailgun we have numerous systems generating a ton of events every hour of the day. It’s a number so large that it’s impossible for a team of people to sort through ElasticSearch results and expect consistent results or for the team to maintain their sanity.
In this tutorial, I will demonstrate how you can send HTML emails with embedded images with mailgun-go. Before we dive into the code, lets first define the problem space and how we can use Mailgun to enhance the user experience of our application.
A few months ago we released automatic IP Warm Up, but we never got to talk about how it’s implemented. Today, we’re going to peek under the hood and try to understand what makes our IP warm up tick. We’re going to start with some context, and then we’ll dive into the interesting technical details later in the post.
We use Go for a lot of our server development here at Mailgun, and it’s great. Coming from Python, though, there is one thing I really missed:
Today, we’re happy to announce the general availability of our Mailgun-Go SDK. Now you can send messages through Mailgun using Go! Mailgun-Go allows you to easily interact with our API by greatly reducing the amount of boiler-plate code you need to maintain.
1 - 7 out of 7 items
