I've recently developed and API from scratch, which is costing me around $1.00, and I thought I'd share its architecture here in case anyone is still guessing how to do one without spending a lot or is having a hard time on execution.
The architecture lacks in monitoring a little bit, but you can use Sentry to do so initially or CloudWatch with a few tweaks. It also does not contemplate AWS WAF (or Fastly WAF) which I think is costly for something that doesn't even have traffic yet.
Apart from that, the only costs you'll have, while no one is using it, will come from AWS Route53 Hosted Zones, $0.5 for each one and a little bit every month from decrypting your SSM parameter (KMS costs), but you can store a JSON string and parse to avoid having multiple decryption requests and reduce that cost a little bit more.
If you have any doubts or criticism, feel free to comment. I hope it helps you!
Hey, congratulations on the final product. It even feels fun. Some are really hard, but some feel blatantly obvious. I don't know why though. I guess it's just because the way we communicate feels off when compared to AI, some times.
Thanks for checking it out! The obvious ones are (hopefully) weaker models :) but yes my experience has been unless you're engaging with human written content consistently the line really blurs easily.
I've just launched Simple Blog API for people to be able to manage posts, publications articles and similar without hassle, and I'm looking for some tips on how to get my first customer. Care to help? Criticism will help as well xD.
What I have right now is very simple, but I hope to get it somehwere better.
I've recently developed and API from scratch, which is costing me around $1.00, and I thought I'd share its architecture here in case anyone is still guessing how to do one without spending a lot or is having a hard time on execution.
The architecture lacks in monitoring a little bit, but you can use Sentry to do so initially or CloudWatch with a few tweaks. It also does not contemplate AWS WAF (or Fastly WAF) which I think is costly for something that doesn't even have traffic yet.
Apart from that, the only costs you'll have, while no one is using it, will come from AWS Route53 Hosted Zones, $0.5 for each one and a little bit every month from decrypting your SSM parameter (KMS costs), but you can store a JSON string and parse to avoid having multiple decryption requests and reduce that cost a little bit more.
If you have any doubts or criticism, feel free to comment. I hope it helps you!