I once did a big migration of an old Subversion (SVN) repository to a new Git repository, migrating all of the version history. This post is about how to do that.

Whenever a webpage have links to pre-compiled frontend files, we as developers can make the web browsers, as well as proxy servers, cache (save) the files for a very long time. But what happens when you make changes to one of those files on the server? How can we do both extremely long caching and invalidate the cache at any time?

In all the projects I have worked on for various clients, we had to load, cache and make use of a user's profile data in the application. How to do that in a very efficient and scalable way, is something I care for a lot. Here are my thoughts and ideas about that topic.