HN user

mluggy

153 karma
Posts15
Comments42
View on HN

How is this different/more scalable than running google tag manager as async, with the rest of the scripts as defer/async as well.

Not so long ago I side-project fassttt.com and thought the biggest issues are server-side, with bad images and improper caching. Ended up creating a complete minifier/compressor/cdn-enabler.

I since realized the problems are mostly client-side. Cumbersome styling framework and JS rendering engines that are dynamic and VERY hard to optimize.

BTW, if people only care about site-speed score, see https://nitropack.io/ which almost always give you a 100 score.

Hi guys, quarantine 3 project 3 (2 previous were fassttt.com and searchiiing.com).

Trying to simplify how experts communicate with clients.

Expert set a weekly price and an alias email to interact. I only forward emails from paying clients and automatically bill the others.

Stack is AWS (Lambda, SES, DynamoDB, API Gateway, S3 and CloudFront) with Bluesnap for payment.

Are you an expert/consultant? What are you currently using to manage clients? How do you bill them?

S3 is $0.023/GB (still x4 higher), plus $0.004 per 10K requests CloudFront is $0.085/GB, plus $0.0075-$0.01 per 10K requests) GCP is $0.08-0.12/GB (same for all services), plus $5 per 1M requests) And who says most of the bandwidth goes towards static assets? 99% of our requests are dynamic (thus the NodeJS frontends)

You do get additional 2-3TB per instance which alone is a couple hundred $$ in bandwidth savings. Will it cover the price of these extra instances? Obviously if you need 8 SSDs DO isn't for you. But the real question is - could GCP be more lean back and still provide the same level of service? I think so.

are you adding custom claims to the core firebase user or as a custom jwt/additional user object? can you have a user signed in with facebook and assign a "experiment1=b" claim to it?

yes, since you don't trust your users you have to get sensitive processes (like promotions, unlocks, rewards) on a separate server process or cloud function. this kinda defeats the purpose of serverless.