In the application I'm working on we started by serving the angular files my a mvc controller. While that worked ok, we are in the process of putting the static files in cloud by putting the entire application behind an amazon cloudfront where we reverse proxy /api to on-prem and the rest from a s3 bucket.

In our case the amount of static files leaving our datacenter was 80G/day which was more than we expected. When we put that in AWS the price will be 7$/day which I consider extremely cheap.

Puttingthe application behind a CDN you also have the benefit of caching if any of your APIs have a cache header, they will be cached in the CDN and you save some on-prem bandwidth.

So I will recommend option 3:

Google cloud CDN and reverse proxy /api to on-prem and the static files served from a google cloud storage bucket

(I assume google cloud CDN have the same feature as amazon cloudfront which I'm more familar with. I use google in this answer. It might as well be AWS)

In the application I'm working on we started by serving the angular files by a mvc controller. While that worked ok, we are in the process of putting the static files in cloud by putting the entire application behind an amazon cloudfront where we reverse proxy /api to on-prem and the rest from a s3 bucket.

In our case the amount of static files leaving our datacenter was 80G/day which was more than we expected. When we put that in AWS the price will be 7$/day which I consider extremely cheap.

Putting the application behind a CDN you also have the benefit of caching if any of your APIs have a cache header, they will be cached in the CDN and you save some on-prem bandwidth.

So I will recommend option 3:

Google cloud CDN and reverse proxy /api to on-prem and the static files served from a google cloud storage bucket

(I assume google cloud CDN have the same feature as amazon cloudfront which I'm more familar with. I use google in this answer. It might as well be AWS)