akos-kri

3 ms·

1. 1.▲
   by akos-kri 5y ago

   If you do plan to be hosting 1TB of data in EBS for each developer then yes, this approach is probably not right for you and you should adapt it! It's not a one-size fits all approach.
2. 2.▲
   by akos-kri 5y ago

   Hey, author of the post here. Apologies if the wording wasn't clear, but these are our developer AWS accounts, i.e. not production workloads. I was just highlighting that everyone runs a copy of the production infrastructure and since
3. 3.▲
   by akos-kri 5y ago

   Hey, author of the post here! A website doesn't need a server! You can host your website assets on a CDN and all of it's then loaded without hitting any of your servers. Our architecture roughly looks like this: - React applicatio
4. 4.▲
   by akos-kri 5y ago

   Hey, author of the post here! Thanks for your comment. Yes, you hit the nail on the head :) 99% of our code actually lives in domain packages that are infrastructure agnostic. Our lambda handlers are very lightweight adapters that take the
5. 5.▲
   by akos-kri 5y ago

   Hey, author of the post here! To manage our AWS accounts we use: - AWS SSO hooked up to our Google Workspace: so no AWS access keys exist, everyone has only short-lived credentials (e.g. 24 hours) to access their AWS account. - AWS Organiza
6. 6.▲
   A *magical* AWS serverless developer experience(journal.plain.com)

   8 points by akos-kri 5y ago|0 comments