---
title: "Comment by Franck Ardisson on \"Amazon Bedrock: A Practical Guide for Developers and DevOps Engineers\" | Hashnode"
description: "Great read! One practical tip for teams getting started: define a clear fallback chain of models in your app logic—start with a smaller, faster Bedrock model fo"
url: "https://hashnode.com/posts/amazon-bedrock-a-practical-guide-for-developers-and-devops-engineers/67e172db7e8e429374a7dd26/comment/69ea0c1d55e26221537725c5"
---

[Discussion](https://hashnode.com/posts/amazon-bedrock-a-practical-guide-for-developers-and-devops-engineers/67e172db7e8e429374a7dd26)

Comment [Amazon Bedrock: A Practical Guide for Developers and DevOps Engineers](https://hashnode.com/posts/amazon-bedrock-a-practical-guide-for-developers-and-devops-engineers/67e172db7e8e429374a7dd26)

[Franck Ardisson](https://hashnode.com/@franckkk)

[Apr 23](https://hashnode.com/posts/amazon-bedrock-a-practical-guide-for-developers-and-devops-engineers/67e172db7e8e429374a7dd26/comment/69ea0c1d55e26221537725c5)

Great read! One practical tip for teams getting started: define a clear fallback chain of models in your app logic—start with a smaller, faster Bedrock model for simple queries and escalate to a more powerful one only when needed, which keeps both costs and latency predictable.
