One of the tenets of modern framework-based web development is the management of your database state in code. Rather like infrastructure-as-code, it means there is an immutable history of the state of the application database at any point in time, which can be re-applied or rolled back as necessary. In addition, the desired state of […]
Author: Resolver Engineering
Ask any developer the quickest and hackiest way of locking unauthorised users out of your website and they will probably mention HTTP Basic Auth. As an extremely simple method of authentication that is built-in to the HTTP protocol standard and supported by every web browser, it’s the universal, go-to method of setting up a username […]
There was a time when asset storage was one of the problems facing web app developers – maybe you stored assets on the web server (easy if you only have one, more difficult if you need to sync them up between multiple servers), or maybe you had a shared disk mounted using NFS. In any […]
A common issue for developers and operations staff when it comes to domain names is whether to choose the apex domain (e.g. example.com) or the www subdomain (e.g. www.example.com) as their primary domain, and then how to redirect one to the other. Choosing to use www over the apex At Resolver, we use AWS for […]
Welcome to the blog for the Resolver Engineering team. We spend our time building and maintaining the applications that power Resolver.co.uk as well as both SaaS and bespoke products for regulators, ombudsmen and alternative dispute resolution providers. Over the course of building these products, we have developed our ways of working, found tips and tricks […]