[throwaway38375]

I agree with your requirement to avoid lock in, but there's nothing wrong with using the big three if you make sure you use open source technologies.

I'm going to use the LAMP stack for example, because everyone is familiar with it.

For example, if you choose MySQL (rather than AWS Aurora) you can:

1. Run that locally during development

2. Install it yourself on a VPS

3. Or migrate to any of the big clouds quite easily

Same goes for your stack. Rather than using PHP with AWS Lambda, provision VMs and install PHP yourself (probably using some sort of shell script).

All cloud providers offer a VM in one form or another, so you're free to swap to another one when you choose.

[throwaway38375]

The only exception I have to this is S3. There are so many S3 compatible providers that I don't see any problem with using S3. There's even MinIO for self hosting and local development!

Some more suggestions for open source components:

Redis for caching and queueing SMTP for mail Nginx for load balancing Cron for scheduling

[4lun]

> The only exception I have to this is S3. There are so many S3 compatible providers that I don't see any problem with using S3.

I've strongly held this view in the past but after recently being on a project where we trialed using other providers, there's a lot missing compared to the AWS S3 offering that has made me rethink this stance a bit

Permissions being a big one, many providers offer little to no fine grained control. With Digital Ocean for example it's all or nothing, you can only generate access keys that gives full access to all buckets[0]

[0] https://news.ycombinator.com/item?id=37724393

[throwaway38375]

A fair point. :)