A customer reported a frustration: Their requests were timing out for the last two weeks. But when investigated, they found their slowest request to them was 4.7 seconds.
The problem? It was the network. There was a bad hop along the way from the USA. They fixed it with a load…
Geocodio
organization
G
Geocodio
@GeocodioOrganization
Hassle-free geocoding
- Arlington, VA
- www.geocod.io
- github.com/Geocodio
4followers
Fri, Nov 6
The DATABASE is usually the slowest part of any request, and the part you need to scale up first. Put cache in front to reduce your dependency on the database.
Mathias Hansen (@MiniCodeMonkey) from @Geocodio at #LaraconAU @Laravel
Are you at the point where you never need to SSH into your servers?
Mathias Hansen (@MiniCodeMonkey) from @Geocodio at #LaraconAU @Laravel
Treat your servers like cattle, not pets.
Are you fine with killing one and spinning up another one at a moment's notice? Not if it's a pet 🙀
Mathias Hansen (@MiniCodeMonkey) from @Geocodio at #LaraconAU @Laravel
How many 9s of availability are you offering?
Do you meet that level?
Mathias Hansen (@MiniCodeMonkey) from @Geocodio at #LaraconAU @Laravel
Up next is Mathias Hansen (@MiniCodeMonkey) from @Geocodio to tell us why our app is fine, it's everything else that is the problem! #LaraconAU @LaraconAU
That's the first commit mentioning @Geocodio.