Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
How we built an AI code reviewer with serverles...
Search
Yan Cui
February 12, 2025
Technology
0
89
How we built an AI code reviewer with serverless and Bedrock
Slides for my talk at the Serverless London meetup on 12-Feb-2025
Yan Cui
February 12, 2025
Tweet
Share
More Decks by Yan Cui
See All by Yan Cui
Money-saving tips for the frugal serverless developer (AWS Community Summit)
theburningmonk
1
160
Money-saving tips for the frugal serverless developer
theburningmonk
1
740
Why the fuzz about serverless (with CompassDigital)
theburningmonk
0
100
Money-saving tips for the frugal serverless developer
theburningmonk
0
98
Efficient patterns for serverless development (AWS Summit London)
theburningmonk
0
130
7 ways to solve Lambda cold starts
theburningmonk
0
58
Saving Money on Serverless: Common Mistakes and How to Avoid Them
theburningmonk
0
53
3 Ways to Improve Serverless Performance
theburningmonk
0
42
Smart and efficient ways to test serverless architectures
theburningmonk
1
280
Other Decks in Technology
See All in Technology
ワールドカフェI /チューターを改良する / World Café I and Improving the Tutors
ks91
PRO
0
140
AIにおけるソフトウェアテスト_ver1.00
fumisuke
1
270
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
5.4k
PagerDuty×ポストモーテムで築く障害対応文化/Building a culture of incident response with PagerDuty and postmortems
aeonpeople
3
460
Writing Ruby Scripts with TypeProf
mame
0
420
バクラクの認証基盤の成長と現在地 / bakuraku-authn-platform
convto
4
780
10ヶ月かけてstyled-components v4からv5にアップデートした話
uhyo
5
390
Classmethod AI Talks(CATs) #21 司会進行スライド(2025.04.17) / classmethod-ai-talks-aka-cats_moderator-slides_vol21_2025-04-17
shinyaa31
0
630
CodeRabbitと過ごした1ヶ月 ─ AIコードレビュー導入で実感したチーム開発の進化
mitohato14
0
100
Perl歴約10年のエンジニアがフルスタックTypeScriptに出会ってみた
papix
1
210
より良い開発者体験を実現するために~開発初心者が感じた生成AIの可能性~
masakiokuda
0
220
2025-04-14 Data & Analytics 井戸端会議 Multi tenant log platform with Iceberg
kamijin_fanta
0
120
Featured
See All Featured
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.8k
Why Our Code Smells
bkeepers
PRO
336
57k
Side Projects
sachag
453
42k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
656
60k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
49k
Build your cross-platform service in a week with App Engine
jlugia
230
18k
BBQ
matthewcrist
88
9.6k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
357
30k
Six Lessons from altMBA
skipperchong
28
3.7k
Done Done
chrislema
184
16k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Intergalactic Javascript Robots from Outer Space
tanoku
270
27k
Transcript
How we built an AI Code Reviewer with Serverless and
Bedrock
Yan Cui http://theburningmonk.com @theburningmonk AWS user since 2010
Yan Cui http://theburningmonk.com @theburningmonk running serverless in production since 2016
Developer Advocate @ Yan Cui http://theburningmonk.com @theburningmonk
Yan Cui http://theburningmonk.com @theburningmonk independent consultant
None
evolua.io Demo
Architecture
API Gateway EventBridge Webhook
API Gateway DynamoDB Bedrock EventBridge Webhook
API Gateway DynamoDB Bedrock EventBridge Webhook
API Gateway DynamoDB Bedrock EventBridge Webhook evolua.io
None
API Gateway DynamoDB Bedrock EventBridge Webhook AppSync evolua.io
API Gateway DynamoDB Bedrock EventBridge Webhook AppSync evolua.io
None
API Gateway DynamoDB Bedrock EventBridge Webhook AppSync evolua.io Authoriser
API Gateway DynamoDB Bedrock EventBridge Webhook AppSync evolua.io Authoriser
API Gateway DynamoDB Bedrock EventBridge Webhook AppSync evolua.io Authoriser
API Gateway DynamoDB Bedrock EventBridge Webhook AppSync evolua.io Authoriser
API Gateway DynamoDB Bedrock EventBridge Webhook AppSync evolua.io Authoriser
Challenges (for an AI code reviewer) Handling sensitive data for
customers
Challenges (for an AI code reviewer) Large fi les. Large
PRs with many fi les. Handling sensitive data for customers
Why Bedrock?
Security
Security Data is encrypted at rest.
www.wiz.io/blog/wiz-research-uncovers-exposed-deepseek-database-leak
aws.amazon.com/bedrock/faqs
Security Data is encrypted at rest. Inputs & Outputs are
not shared with model providers. Inputs & Outputs are not used to train other models.
API Gateway DynamoDB Bedrock EventBridge Webhook AppSync evolua.io Authoriser Fallback
Primary
privacy.anthropic.com/en/articles/7996885-how-do-you-use-personal-data-in-model-training
Serverless
Serverless Usage-based AND provisioned throughput pricing
None
None
1M Input Tokens 1M Output Tokens $0.14 v3 r1 $0.28
$0.55 $2.19 Sonnet $3.75 $15.0 Haiku $0.80 $4.00
Very cost ef fi cient!
Very cost ef fi cient! Data is stored in China.
Very cost ef fi cient! Data is stored in China.
Data might be used to train other models.
www.wiz.io/blog/wiz-research-uncovers-exposed-deepseek-database-leak
Very cost ef fi cient! Data is stored in China.
Data might be used to train other models. Operationally immature.
None
No token-based pricing yet
No token-based pricing yet “GPU-based instance type like ml.p5e.48xlarge is
recommended”
ml.p5e.48xlarge 💰💰💰💰💰💰💰💰💰💰 💰💰💰💰💰💰💰💰💰💰 💰💰💰💰💰💰💰💰💰💰 💰💰💰💰💰💰💰💰💰💰 💰💰💰💰💰💰💰💰
Other capabilities Guardrails Knowledge base (managed RAG) Agents Cross-region inference
Model evaluations
None
None
None
API Gateway DynamoDB Bedrock EventBridge Webhook AppSync evolua.io Authoriser Fallback
Primary
Lessons
Webhook
Webhook Analyse changes
Webhook Analyse changes Feedback
Condensed view…
None
Lambda timed out after 15 mins
Succeeded on automatic retry
Webhook Analyse changes Feedback LLM limits GitHub limits AWS limits
Lesson: AI is 10% of the problem
None
Reasoning ability
Context window Max response tokens API rate limit Reasoning ability
Context window Max response tokens API rate limit Reasoning ability
Cost Performance
Context window Max response tokens API rate limit Reasoning ability
Cost Performance Important selection criteria for LLMs
Doing cool AI stuff! Working around AI limits
Doing cool AI stuff! Working around AI limits Stop playing
with my bowl…
Context window Max response tokens API rate limit Reasoning ability
Cost Performance
Claude 3.5 Sonnet’s default throughput is 50 per minute
Claude 3.5 Sonnet’s default throughput is 50 per minute Can
be raised to 1,000 per minute
Claude 3.5 Sonnet’s default throughput is 50 per minute Can
be raised to 1,000 per minute Bedrock has cross- region inference
Mitigate API rate limit Raise account limits. Use Bedrock cross-region
inference.
Mitigate API rate limit Raise account limits. Use Bedrock cross-region
inference. Limit no. of parallel requests per PR.
Mitigate API rate limit Raise account limits. Use Bedrock cross-region
inference. Limit no. of parallel requests per PR. Fallback to Anthropic & less powerful models (Claude 3 Sonnet, Claude 3.5 Haiku)
Future work: incorporate other models (Nova, DeepSeek, etc.)
Future work: incorporate other models (Nova, DeepSeek, etc.) Also good
for cost control!
Lesson: LLMs are still quite expensive
None
Dif fi cult to build a sustainable and competitive business
Cost control Only analyse changed lines.
Cost control Only analyse changed lines. Good for cost control
Good for UX
Cost control Only analyse changed lines. Limit free users to
few PRs per month.
API Gateway DynamoDB Bedrock EventBridge Webhook
API Gateway DynamoDB Bedrock EventBridge Webhook Built-in retries & DLQ
Lambda timed out after 15 mins
Lambda timed out after 15 mins Reprocess fi les on
retry…
Lambda timed out after 15 mins Reprocess fi les on
retry… Duplicated side- effects (e.g. Github comments)
Cost control Only analyse changed lines. Limit free users to
few PRs per month. Use checkpoints to avoid re-processing fi les on retries
const issues = await executeIdempotently( `${event-id}-${filename}-analyze`, () => analyzeFile(file) );
... await executeIdempotently( `${event-id}-${filename}-add-gh-comment`, () => addReviewComment(filename, comment) );
Webhook Analyse changes Feedback Why not Step Functions?
Webhook Analyse changes Feedback Why not Step Functions? Checkpoints is
just easier 🤷
Lesson: Latency is a challenge
Models take 10s of seconds to analyse each fi le
Wasted CPU cycles in Lambda
Future work: try other models
Future work: make use of these CPU cycles
Lesson: Be ware of hallucinations
“Give me JSON in this format”
None
“Give me JSON in this format” “Nope!”
None
Non-existent codes, invalid URLs
Non-existent line numbers
Future works
Go to evolua.io to try it out. We’d love your
feedback!
Questions?