シャドーイング練習: Top 5 AI Gateway Use Cases | Solo.io - 動画で英語スピーキングを学ぶ

練習モードを選ぶ

各モードは全画面の練習ルームで開きます。

159 文

文が短すぎたり長すぎる場合は、Editをタップして調整してください。

Continuing on the theme of AI related connectivity, let's talk about AI gateways.

A really common question we get is, why do I need an AI gateway?

And maybe I'll just build one myself or use my existing API gateway for that functionality.

So let's examine the top five use cases we see in customers adopting an AI gateway.

The first one involves credential management.

So without an AI gateway, a very common pattern you see is I'll create a key here in my LLM provider,

and then I'll go ahead and take that key and distribute it to the application teams,

the teams writing agents, and anyone maybe that they're using an agentic IDE and they need an API key there as well, and you can distribute it in all those locations.

Functionally this works.

The problem is when any one of these developers that has seen

that key maybe leaves the company or accidentally checks it into a public GitHub repository,

the blast radius of that is this entire infrastructure, including your account in the ALM provider.

One thing that an AI gateway helps out with immediately is

that I can have safe and secure storage for my API keys that only my AI gateway has access to.

The AI gateway then can, if we want, go ahead and issue individual keys for specific use cases for specific user groups.

Or I can also integrate with existing authentication mechanisms I have in my organization.

Like if an agent is presenting a JWT, I can use that and map it to the API key I'm providing to the provider.

This is critical just in terms of the blast radius limitation of like, hey, a key is exfiltrated,

or someone has hacked a certain piece of code and gained access to a certain piece of code.

I know exactly how to contain that threat.

And by containing it, I'm not impacting any of the use cases I have for that LLM provider.

I would say that credential management also plays a key role in the other use cases we're about to talk about now.

So let's talk about rate limiting.

Why is rate limiting important?

So maybe you've already seen this in your existing applications where let's say you have,

this app is sending five requests with a token size of let's just say 20K tokens, right?

And over here, this IDE is sending 20 requests with a token size, like a 45k token window,

like every minute or so, right?

Now you end up with turning an agent on and the agent goes bananas.

And all of a sudden it sends, you know, 20,000 requests and a massive context window that it's dumping in.

And it's got like a million tokens, let's say, just in a very short period of time, like in less than a minute.

Now in

that scenario, what's going to happen is the LLM provider is going to rate limit not only based on request count, but also by token count.

So those are both variables in that equation and evaluation.

And when you get shut off, you're going to get shut off, not just for the use case that's abusing it, but account wide, and you're going to get a backoff.

That means maybe this agent, I'm just testing around or it's an evaluation,

but I brought my entire account down and that's all API keys for that account across all the other use cases.

It's impacting developers, it's impacting my production apps that may be customer facing as well.

We have to find a better way to deal with this problem.

And the answer is with an AI gateway to actually support rate limiting

and token rate and rate limiting in particular directly in the gateway.

And that means when I have this same traffic here where I'm coming over and this is the bad actor.

I have our IDE friends over here.

This agent, since it's interacting with the AI gateway first,

the AI gateway can shut off that agent directly while allowing traffic from all other consumers to continue.

That means I have no production or service interruptions from the app or the IDE, and the agent gets really gentle back pressure

and gets turned off for a period of time and then gets opened up again.

It'll be very obvious to that team that they're getting rate limited locally, and then they can fix that problem and address it and come back online.

Or maybe it was a periodic or ephemeral issue with flooding a bunch of traffic, and as soon as they exceed the rate limiting window, then they'll come back online.

But the key thing in any gateway and why API gateways, traditional API gateways are not sufficient to handle this requirement is you need both request rate limiting,

but also token weighted rate limiting.

So I can compute the amount of tokens that are allowed given a certain time window in seconds, minutes, hours or days.

All right.

Use case number three, usage reporting.

So maybe this is familiar to you as you're consuming more and more of provider services.

end of the day you get a nice bill from your provide your LLM provider

and it's a million dollars okay okay who has actually spending

that money okay you may be lucky enough to have multiple API keys

so you get maybe some subdivision of that but again

if you're sharing API keys across the clients

that are using it then you're gonna that's gonna get washed

out more importantly you're not gonna have the very specific details of the identities the groups that are consuming it, the model and the provider used in

that internal detail of how you're actually going to show chargeback or showback to the teams consuming.

So what we want is the ability that we'll get the same million dollar bill over here.

Okay.

But in this scenario, every request that's going through the AI gateway is actually earmarked

or watermarked with the client actually consuming it.

That's how we're doing rate limiting.

And that's why we implement credential management in this layer as well, which means that when I get this $1 million bill,

the access logging and reporting here can actually tell me that this particular app is actually responsible for 50K

and this IDE is responsible for 50K.

Or in like, you know, the token count, it'll report the token counts and you can extrapolate the value there.

And then our friend, the agent that was acting up in terms of rate limiting, their token contribution was around 900K, right?

This is a very, very key attribute to like once you're trying to justify

that AI budget and who's consuming you're trying to even

if you're not charging back those teams you're trying to show

who's consuming consumption reporting in the gateway is a key feature

you'd certainly don't want to you don't have the right details in a traditional API management solution

or API gateway to basically track providers and clients

and token counts to show that charge back

but then also you won't have the granularity to isolate it to given teams all right number four for guardrails.

So for guardrails, what we're going to protect against is a number of things.

The request that's going in, this can be a hijack request, it could be a phishing prompt, it can be anything.

This is your attack surface area of what's going in via natural language prompt.

And they're going to be a common attack vectors that you're going to want to protect against.

Certain prompts that if they contain keywords or they're structured in a certain way, you always want to prevent.

Or perhaps you want to append a system prompt to every request that goes through.

So you can use some semantic guardrails there in line with the request.

Likewise, even if it wasn't a malicious request on the response path, I always have a danger here of data exfiltration, right?

So if I'm asking a very innocent question that's not a phishing attack or trying to be a Trojan horse, I still might get back some customer data,

account information, social security number, this type of thing that I don't want to expose to clients.

And in that case, I have no way of protecting against either of these.

The only thing I can rely on is the actual LLM providers' moderation services, which are definitely valuable but on the request path, I'm never limited.

Like any data can go all the way to the LLM provider here.

So that's actually leaving my network and is out on like open internet and available to the provider.

And I might not want that data even escaping my network, right?

Likewise, there could be very specific requirements I have where maybe the obvious things like credit card numbers and social security numbers,

you can pattern match on those and the provider services can filter those.

But what if I have very unique constraints of what I consider PII for my customer base, or I have intellectual property that I don't want to escape my network,

100

I don't want developers accidentally putting in key bits of code

101

or other IP materials that actually might throw to an LLM provider, that I need to be able to instrument for advanced guardrails as well.

102

So let's look at how an API or an AI gateway solves for that.

103

In the AI gateway, you actually have three controls available.

104

So you have basic guardrails.

105

And what basic guardrails do is the first use case I said, that acting directly on the prompt and the response, it can introspect the request, it can identify keywords, identify patterns,

106

and reject those and reject that request to not allow it to flow through to the upstream LLM provider.

107

Likewise, in the response path, it can inspect the data and it can either reject

108

that outright or it can mask that data as it comes back to the client.

109

The key value there is that I don't have to implement it all of the client apps, these guardrails.

110

I have a centralized point of control.

111

This becomes very important if after going to production, you discover that some key data is being exfiltrated, or you're open to some attack vector.

112

What is the fastest path to remediating that exposure?

113

And it's not rolling out new updates to all the apps you've deployed, and it's not working with your upstream LLM provider to add that to their moderation endpoint.

114

that's actually implementing that in the AI gateway and getting it pushed to production in minutes.

115

The next feature I'll mention is moderation endpoint integration.

116

So again, this is a key feature that the upstream LLM providers all offer, but why would I want to wait necessarily for the full request to go to the LLM

117

and then catch that in the processing path?

118

What I really want to do is inside my network, basically contact the moderation point, and if there's any problem with that request,

119

I want that to actually be cut off in my network and not go farther downstream.

120

A key principle here is trying to eliminate any threats or any potential data exfiltration as soon as you can detect it.

121

And this is a key aspect of that.

122

And then finally, we support what we call advanced guardrails.

123

And really what that is, as an example, is if you wanted to train a small language model, maybe you take like an 8 billion parameter model

124

and you fine-tune it with maybe 500 examples of various types of data

125

that you don't want to see in a request or different types of prompts that you don't want to see,

126

that can be very, very useful to execute inline in the request path as more of a semantic guardrail.

127

So you're not even matching on specific data patterns or data signatures.

128

you're doing semantic controls of, is this suggestive of this, or is this like these other things?

129

And that can be done with a small language model that can be integrated directly with the AI gateway.

130

The last point I want to make is around abstraction.

131

So in this case, we have individual apps, agents, and IDEs going directly against the LLM provider.

132

The impact of that means that they are binding to the very specific API of that provider and also they are actually,

133

if you look behind the scenes, most customers, while they may be consuming the public endpoint,

134

the generalized endpoint for OpenAI, for example, that we all use when we use it, but it's quite likely for sensitive information or for their enterprise use cases,

135

you're consuming a private endpoint there.

136

So you've isolated that LLM in specific infrastructure for your company, and you need to access that endpoint or a specific model.

137

And in that scenario, now the app is going to go to that specific endpoint.

138

There are definitely cases where there can be endpoint availability issues

139

there for a very specific endpoint where it's unavailable for a certain period of time.

140

Now in that case, if that's tied to a production experience, so like a chat bot or any customer facing functionality,

141

then that customer channel is down in that period.

142

Another potential exposure here is if you get rate limited in a given model, or even availability of a given model is down,

143

then you might want to fall back or fail over to another model.

144

But it is very hard to instrument for this.

145

You actually have to build that logic directly into each application agent

146

and you're hoping your IDE supports it that you're using up here, but with an AI gateway we can do that seamlessly.

147

If a given endpoint, private endpoint is down, the LLM will seamlessly fall over based on your configuration to a backup endpoint

148

and this can cascade down to multiple end points, multiple models, and even multiple providers.

149

When we talk about abstraction, if your AI gateway supports a canonical API as we do in Agent gateway,

150

all of your clients can just talk OpenAI's API, and that can be mapped to any provider underneath the cover,

151

whether that's Claude or Vertex or Bedrock or OpenAI itself.

152

It can scale to all of these models while presenting a single canonical and consistent API to the consumers, which makes it much easier as you start to exchange models,

153

whether it's hosted providers or you're starting to run LAMA or another model, open source model internally.

154

you still don't impact the consumers of that because you're keeping that API abstraction the same.

155

So hopefully this was useful in terms of discussing the key use cases

156

and the key value we see with customers in adopting an AI gateway

157

and gives you a good idea of how daunting this task is

158

if you were gonna embark on the path of implementing it on your own.

159

Check out Agent Gateway today.

アプリをダウンロード

流暢に話すために必要なすべて

AI発音採点文ごとに採点

IPA練習すべての音をマスター

単語学習自分の単語帳を作る

単語ゲーム遊びながら覚える

QRをスキャン

Download on theApp Store Get it onGoogle Play

FOR YOU

このレッスンの語彙とスピーキングのポイント

このC1レベルのスピーキングレッスンは、動画「Top 5 AI Gateway Use Cases」を教材にしています。繰り返し出てくる語は次のとおりです：gateway, key, provider, request, Api。この動画には、シャドーイング用の文が159文、単語が2518語あります。音声の長さは13:37です。話す速さは速く、1分あたり約185語です。音のつながりや弱く発音される音が多くなります。英語の頻出3,000語に含まれる単語は80%だけなので、語彙は難しめです。

この動画の重要語彙

動画の中で特に難しい単語15語を、発音と意味つきで紹介します。

単語	発音	意味
token 名詞	/ˈtoʊkən/	トークン
guardrail 名詞	/ˈɡɑɹdˌɹeɪl/	ガードレール
consume 動詞	/kənˈsum/	消費する, 消耗する
credential 名詞	/kɹɪˈdɛnʃəl/	証明書
semantic 形容詞	/sɪˈmæntɪk/	意味的な
upstream 形容詞	/ʌpˈstɹiːm/	川上
likewise 副詞	/ˈlaɪkˌwaɪz/	同様に
canonical 形容詞	/kəˈnɒn.ɪ.kəl/	カノン的な
keyword 名詞	/ˈkiː.wɜːd/	キーワード
phishing 名詞	/ˈfɪʃɪŋ/	フィッシング, フィッシング詐欺
isolate 動詞	/ˈaɪ.sə.leɪt/	切り離す, 隔絶する
functionality 名詞		機能性
distribute 動詞	/dɪˈstɹɪbjuːt/	分ける
radius 名詞	/ˈɹeɪ.di.əs/	橈骨
vector 名詞	/ˈvɛktɚ/	ベクトル

動画に出てくる句動詞

単語	発音	意味
come back 動詞		戻る, 帰る
go ahead 動詞	/ˌɡoʊ əˈhɛd/	どうぞお先に
check out 動詞		試験する, 検査する
come over 動詞		遣って来る

この動画の文法

話し手がよく使っている文型を、動画の実際の表現とともに紹介します。

文型	動画での表現
受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる	is exfiltrated · are allowed · is actually earmarked
現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係している	has seen · has hacked · you've already seen
関係詞節 who / which + 節 — 人や物について情報を加える	well, which means · services, which are · consumers, which makes

注意したい発音

話し手はyou're, don't, I'mなど、短縮形や弱形を60回使っています。聞こえたとおりの短い形で発音しましょう。

「th」の音: authentication /ɔːˌθɛntɪˈkeɪʃn̩/, underneath /ˌʌndɚˈniθ/
「sh」と「zh」の音: moderation /ˌmɑdəˈɹeɪʃən/, abstraction /æbˈstɹæk.ʃn̩/, credential /kɹɪˈdɛnʃəl/, phishing /ˈfɪʃɪŋ/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/
長い単語（アクセントの位置に注意）: moderation /ˌmɑdəˈɹeɪʃən/, canonical /kəˈnɒn.ɪ.kəl/, authentication /ɔːˌθɛntɪˈkeɪʃn̩/, ephemeral /ɛˈfɛ.mə.ɹəl/, extrapolate /ɛkˈstɹæp.əˌleɪt/

日本語話者が苦手な音：

/r/ と /l/ の区別 — /l/ は舌先を歯茎につけ、/r/ はどこにもつけない: guardrail /ˈɡɑɹdˌɹeɪl/, credential /kɹɪˈdɛnʃəl/, exfiltrate /ˈɛksfɪltɹeɪt/, centralize /ˈsɛntɹəlaɪz/, ephemeral /ɛˈfɛ.mə.ɹəl/
/v/ — /b/ にならないように、上の歯を下唇に当てる: vector /ˈvɛktɚ/, suggestive /sə(ɡ)ˈd͡ʒɛs.tɪv/, unavailable /ˌʌnəˈveɪləbəl/, subdivision /ˈsʌbdɪvɪʒən/
/f/ — 「フ」ではなく、上の歯と下唇で出す: exfiltrate /ˈɛksfɪltɹeɪt/, phishing /ˈfɪʃɪŋ/, ephemeral /ɛˈfɛ.mə.ɹəl/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/

この動画での練習方法

まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
まず0.75倍速で一文ずつシャドーイングし、慣れてきたら通常の速度に戻します。
自分の声を録音して元の音声と比べます。token, guardrail, consumeなどの単語に特に注意しましょう。

シャドーイングとは？英語上達に効果的な理由

シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。

シャドーイングのやり方: ステップ別の完全ガイドを読む →

シャドーイング練習: Top 5 AI Gateway Use Cases | Solo.io - 動画で英語スピーキングを学ぶ

練習モードを選ぶ

アプリをダウンロード

おすすめ動画

Agentic AI Frameworks Explained: Workflows, Multi-Agent, & Production

Rate Limiter System Design in Under 60 Seconds #techprep #programming #systemdesign

BGP Overview

How To Solve The App Onboarding Paradox

Armchair Architects: Resiliency in the Cloud – Core Patterns

it’s boring, but it’s what bursts the ai bubble

Azure App Service and Virtual Network Integration Options

I Tried PewDiePie's Odysseus AI So You Don't Have To

Data Ingestion Best Practices! How to Ingest Data Efficiently at Enterprise Scale!

AI Governance Explained: Ethical, Transparent & Accountable AI for the Future

Harnessing generative AI in architecture, engineering & construction

Next.js 16.3 got good (if you care)