---
title: "Comment by For sell Mx on \"Amazon Bedrock: A Practical Guide for Developers and DevOps Engineers\" | Hashnode"
description: "Great practical breakdown of the dev experience with Bedrock. One thing I'm curious about: how does the latency and cost of invoking third-party models via Bedr"
url: "https://hashnode.com/posts/amazon-bedrock-a-practical-guide-for-developers-and-devops-engineers/67e172db7e8e429374a7dd26/comment/69f89ba3393f48da863d38c6"
---

[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)

[For sell Mx](https://hashnode.com/@mxsell)

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

Great practical breakdown of the dev experience with Bedrock. One thing I'm curious about: how does the latency and cost of invoking third-party models via Bedrock compare to calling them directly through their native APIs, especially for high-throughput production workloads?
