-
- Private work.
- Chess24 went down, nginx 404.
- Updated next rise garden subscription box (feb). All seeds, no nutrients/ph.
- Distilled water, refilled 8sleep, primed.
- Repositioned IRA into large cap growth.
- Pinpoint split the SMS interface into a new app: https://us-east-1.console.aws.amazon.com/sms-voice/home
- Actually not too worried about the cognito elements (I think it was SES? Or pinpoint? Or SMS?) being in diff regions. Where possible, everything is us-west-1. Pinpoint (I think) didn’t support us-west-1, so it’s in east.
- Crazy how anti-elon bb and nyt are. Hard to read.
- https://openai.com/blog/openai-announces-leadership-transition
- “Mr. Altman’s departure follows a deliberative review process by the board, which concluded that he was not consistently candid in his communications with the board, hindering its ability to exercise its responsibilities. The board no longer has confidence in his ability to continue leading OpenAI.”
- MVL dominated blitz today. 9 final rounds tomorrow and he has a 2pt lead.
- Remember GPT-4 Turbo is up to April 2023.
- Supercontest.
- Some planning for the big changes coming next.
- ElastiCache.
- Redis and memcached.
- Control size, charged for storage.
- Like RDS, it’s $X/hr. There are on-demand and reserved instances.
- It’s $16/mo for the smallest cache, on-demand. 3yr RI for the same is a little over $8/mo.
- Note that RIs = not fully serverless/scalable. They’re locks. Each one you add makes the whole stack a little less flexible.
- SQS.
- Remember common uses: data buffer btw applications, batching tasks, storing notifications.
- Created a queue.
- Can do standard (at least once, not ordered) or FIFO (exactly once, ordered).
- Configs: msg expiration (up to 14 days), max size (up to 256KB), more.
- Remember dead-letter-queues (DLQs) temporarily stored failed/unprocessable messages (alongside main queue). Also called a redrive policy.
- Messages can have a generic body, whatever you want. And then structured metadata – field:value as desired.
- You can manually send msgs, and manually receive msgs (just poll and inspect them).
- Then they can be deleted after they’ve been accessed. If you don’t, all other consumers will see the message (and likely try to process it).
- Inputs: ALL sorts of services can write to an SQS queue. A popular one is SNS – if a topic on the SNS gets a message, you can forward it to SQS.
- Outputs: When a new msg appears in the queue, you can trigger all sorts of other services. A popular one is Lambda – receive an SQS message -> run a lambda. You can also pipe to eventbridge.
- Note too; if your use case is purely for notifications, SNS is better. It has its own topics, producers, subscriptions, etc.
supercontest-alarms currently does this; cloudwatch sends events to an SNS topic (FIFO, exactly once), then my personal gmail is a subscriber to that topic.
- Thought through an event-driven rewrite of some pieces of the app. Will use SQS for scores and picks.
- Thought a bit about about the 5 BIG changes: Amplify, Lambda, API Gateway, Cognito, and SES/SNS.
- I wish there was a way to chunk it up? But I’ll probably just do it all in one fell swoop. Linked the tickets.
- The lambda change will probably come first (although created from amplify). API will switch to just data-returns (the app will handle the formatting / other logic).
- API gateway will front each of these (again, managed by amplify). This should be a pretty simple change.
- Then cognito will auth each of them (again, managed by amplify).
- Then I’ll go back to the app and rewrite it all in tsx/react. This will be fun.
- At that point, everything will be fully deployable with amplify.
- And then at the end, you can plug into SES/SNS for the current email functionality swapout (and new text).
