Measuring the performance of a website from multiple locations around the world is crucial with the current global scale of the internet. In most cases, your visitors are not only based in your home country but from all other countries too. From Canada to Australia, from Chile to Russia, your website is being visited by more people than you think. There are a number of paid services that allow you to constantly monitor your website performance from multiple locations around the world. But maybe you're a geek and you want to do it yourself?
By default, acme/autocert stores provisioned certificates on local disk for long-term caching. What happens is that the next time an user visits the same page, this package will fetch the certificate from the local disk instead of provisioning a new one. But what if your service is deployed across multiple machines? How do you ensure that all services are using the same cache? Come along and see how to solve this problem.
We have been working on reducing the amount of bytes that we send to all Fider users. Being a web application built with React, we have focused on JS and CSS. On this post we share our learnings, some concepts and suggestions on how you can do the same with your web application.
React 16.6 has been released and it's now easier than ever to do code split within our React applications by using lazy and Suspense. After a few days monitoring a production application that is using lazy, I noticed a couple of client-side errors when downloading asynchronous modules. Learn how to mitigate this.
HTTPS has become a must nowadays. Not only for its security purpose, but also because search engines like Google are giving better rank to websites that run on a secure protocol over those using plain HTTP. It's 2017 and gone are the days that we could use the price as an excuse to not have HTTPS our our websites. Learn here how to generate SSL Certificates fully automated and free on Go web applications.
There is a particular pattern that is very common on these languages that is hard to find any mentions about in the Go community. The pattern is called Session per Request and is particularly useful to decouple business components from database transaction management. This post will drive you through what it is, how to implement, pros/cons and some examples written in Go.
Go is fast and everyone knows that. But how can we make it ever faster when running web applications on it? On this post I'll try to cover how can we achieve an even better response time for web applications using server side cache, because you know, performance IS a feature and I don't know anyone who enjoys spinning wheels.
On the last post of this series we finished a simple, but fully working web app written in Go using only the standard library. During this post you’ll learn how package management works in Go by adding a very famous third-party package.
Today I’m starting a new blog series on how to build your first web application using Go. I’ll do it by following a baby steps approach, so you can expect a long blog series covering everything you need (or should) do/use to build a web application, like Go tools, GOPATH, test, mock, vendoring, database and, of course, hosting in the cloud.
See the archive for more posts.