Luke Hegarty's Avatar

Luke Hegarty

@lheg

πŸ’» Senior Software Engineer @ Kraken.tech πŸ… AWS Solutions Architect Associate Certified πŸ… Terraform Associate Certified

52
Followers
170
Following
16
Posts
06.12.2024
Joined
Posts Following

Latest posts by Luke Hegarty @lheg

Post image Post image

AWS London Summit tomorrow! I must give a shoutout to VIL216 and UNH303 presented by my colleagues at Kraken. #aws #awssummit #awssummitlondon

29.04.2025 22:05 πŸ‘ 1 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

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.

10.01.2025 08:26 πŸ‘ 2 πŸ” 2 πŸ’¬ 1 πŸ“Œ 0
Post image

Stop wasting money on CORS preflight requests.

Here's a quick tip for reducing API Gateway costs. πŸ‘‡

10.01.2025 08:26 πŸ‘ 9 πŸ” 1 πŸ’¬ 1 πŸ“Œ 1
Preview
Octopus Energy’s software platform is emerging from parent’s shadow Kraken now has more than 60mn accounts and forecasts that it will win tens of millions more

I’m pleased to share that I’m starting a new role at Kraken as a senior software engineer, promoting the adoption of clean energy.

If you’re not familiar with Kraken or its 60 million customers, check out this Financial Times article from yesterday.

www.ft.com/content/475c...

Kraken.tech

09.01.2025 09:45 πŸ‘ 0 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

#spotify #backstage #platform #devops

16.12.2024 20:55 πŸ‘ 1 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0
Preview
Platform Takes The Pain - CoRecursive Podcast How did Spotify scale from 10 engineers to 100s to 1000s ...without slowing down? Without becoming corporate? Facing an IPO deadline, Pia Nilsson worked with 300 teams to transform how Spotify built s...

corecursive.com/platform-tak...

How do you retain autonomy, empower teams and provide consistency in over 300 paths to production in under 6 months for IPO?

A great story from Pia Nilsson on how the platform at Spotify created Backstage.

16.12.2024 20:55 πŸ‘ 1 πŸ” 1 πŸ’¬ 1 πŸ“Œ 0

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!

12.12.2024 21:54 πŸ‘ 1 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

@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.

11.12.2024 00:49 πŸ‘ 1 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

If you are using #AWS or just interested in solid technical advice, you should listen to the Heroes: bsky.app/profile/did:... #listentotheheroes

10.12.2024 09:31 πŸ‘ 126 πŸ” 36 πŸ’¬ 4 πŸ“Œ 2

@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

10.12.2024 09:39 πŸ‘ 6 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0
Preview
Terraform 1.10 improves handling secrets in state with ephemeral values Terraform 1.10 is generally available, and it includes ephemeral values along with improvements to plan and apply performances.

A week late however .. Terraform v1.10 now supports ephemeral values πŸŽ‰πŸŽ‰

This is going to simplify workflows massively. #terraform #hashicorp #iac

www.hashicorp.com/blog/terrafo...

09.12.2024 11:11 πŸ‘ 0 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0
Preview
Single table design for DynamoDB: The reality Consider the downsides of single table design before committing your developers

..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...

08.12.2024 22:49 πŸ‘ 0 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

As a follow up to the post I made yesterday re:DynamoDb concurrent updates..

There is an excellent post from last year written by @pete-naylor.bsky.social discussing why you probably don’t want to implement such a single table pattern as it not only locks you into configuration inflexibility..

08.12.2024 22:49 πŸ‘ 0 πŸ” 0 πŸ’¬ 2 πŸ“Œ 0
AWS re:Invent 2018: Amazon DynamoDB Under the Hood: How We Built a Hyper-Scale Database (DAT321)
AWS re:Invent 2018: Amazon DynamoDB Under the Hood: How We Built a Hyper-Scale Database (DAT321) YouTube video by Amazon Web Services

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...

07.12.2024 17:59 πŸ‘ 1 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

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.

07.12.2024 17:59 πŸ‘ 1 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0

An interesting characteristic of DynamoDb that I learnt recently is that due to its internal β€œLeader model”, concurrent updates to the same record do not cause any concurrency issues as long as each update modifies a different attribute on the record.

07.12.2024 17:59 πŸ‘ 1 πŸ” 1 πŸ’¬ 2 πŸ“Œ 0
Preview
AWS re:Invent re:Cap with Corey Quinn Podcast Episode Β· AWS Developers Podcast Β· 06/12/2024 Β· 29m

Throughly enjoyed @quinnypig.com’s re:Invent roundup this morning. His sarcastic perspective on very valid issues in the AWS eco-system resonated with my northern British pessimism on a gloomy/stormy day.

podcasts.apple.com/gb/podcast/a...

07.12.2024 13:44 πŸ‘ 16 πŸ” 4 πŸ’¬ 1 πŸ“Œ 0
Considerations when using zero-ETL integrations with Amazon Redshift - Amazon RedshiftConsiderations when using zero-ETL integrations with Amazon Redshift - Amazon Redshift The following considerations apply to zero-ETL integrations with Amazon Redshift.

docs.aws.amazon.com/redshift/lat...

06.12.2024 23:16 πŸ‘ 0 πŸ” 0 πŸ’¬ 0 πŸ“Œ 0

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.”

06.12.2024 23:16 πŸ‘ 1 πŸ” 0 πŸ’¬ 1 πŸ“Œ 0