lheg.bsky.social
💻 Senior Software Engineer @ Kraken.tech
🏅 AWS Solutions Architect Associate Certified
🏅 Terraform Associate Certified
16 posts
47 followers
169 following
Getting Started
Conversation Starter
comment in response to
post
Every time the browser makes a cross-origin request, it first makes a preflight request to make sure it can actually send the request.
Since API Gateway charges per request, you’re billed for both the preflight and the main request.
comment in response to
post
#spotify #backstage #platform #devops
comment in response to
post
Thank you @pete-naylor.bsky.social for your sharing your thoughts. My primary experience with AWS DB services has been with DynamoDB so far so I appreciate the insight, particularly into hot key contention as that is not something I have really considered before. One for the future!
comment in response to
post
@leeroyhannigan.bsky.social thanks for the context mate. Unfortunately I can’t amend my initial post to add this additional information 😬 but appreciate you responding.
comment in response to
post
@werner.social It’s fantastic the recognition you are giving to those who tirelessly support and inspire the AWS community. Whenever I’m scratching my head on a problem, 9 times out of 10 I’ll end up using a solution from an #AWS hero. #listentotheheroes
comment in response to
post
..but the pattern was a relic of its time pre on-demand / auto-scaling etc.
What I’m trying to figure out now is when you’d use DynamoDb over the new Aurora DSQL? #AWS #DynamoDb #AuroraDSQL #re:Invent
blog.highbar.solutions/single-table...
aws.amazon.com/rds/aurora/d...
comment in response to
post
Updates with conflicting attributes however, it’s likely better to have a single service aggregating the writes of the artefacts and using versioning/optimistic locking so that writes can be rejected if obsolete.
www.youtube.com/watch?v=yvBR...
docs.aws.amazon.com/amazondynamo...
comment in response to
post
This nullifies any issues with the order in which update was received as you are not going to conflict on attributes. An example could be multiple microservices that make up a larger bounded context writing their own specific artefact i.e a product price , inventory to a record.
comment in response to
post
docs.aws.amazon.com/redshift/lat...
comment in response to
post
All I could find in the docs is:
“Zero-ETL integration does not support transformations while replicating the data from transactional data stores to Amazon Redshift. Data is replicated as-is from the source data base. However, you can apply transformations on the replicated data in Amazon Redshift.”