강의

멘토링

커뮤니티

Programming

/

Back-end

gRPC made easy with Python!

gRPC is all the rage these days! Let's learn it with easy Python, instead of the unfamiliar Go!

  • baekoblin
3시간 만에 완강할 수 있는 강의 ⏰
통신
프로토콜
grpc
Python

学習した受講者のレビュー

こんなことが学べます

  • gRPC

  • backend

  • Python

gRPCは何ですか? 🤔

gRPCは簡単に言えば、コンピュータ間でお互いに話し合い、データをやり取りする方法です。まるで私たちが友達とメッセージを送受信しているようです! Googleで作られた技術なのに、スピードも速く効率的だから最近人気が多いです。特に複雑なシステムでは、複数のプログラムが互いに協力する必要がある場合に非常に便利です。

gRPCはマイクロサービスアーキテクチャと呼ばれる方法でよく使用されていますが、これは大きなプログラムを小さなプログラムに分割して管理することです。 gRPCのおかげで、これらの小さなプログラムは互いに簡単にコミュニケーションをとり、協力することができます!


gRPCはGo言語でのみ学ぶべきですか?

grpcはさまざまなプログラミング言語をサポートしているため、Go言語に必ずしもこだわる必要はありません。 Java、 Python 、C ++、Node.jsなど、さまざまな言語でもgRPCを使用して効率的な通信システムを構築できます。

どの言語を選択しても、gRPCの重要な概念と原理を理解することが重要です。 gRPCはProtocol Buffersというデータ型を使用してメッセージを定義し、それによって異なる言語で書かれたシステム間でシームレスな通信を可能にします。

したがって、自分に慣れている言語やプロジェクトに適した言語を選択してgRPCを学び、活用するだけです。

私たちは? Pythonで学びましょう!


この講義の特徴

📌簡単なPython言語と直感的なgRPCの組み合わせで簡単に学ぶ!

📌コンセプトから様々なストリーミングパターンを実際に作ってみましょう。

📌通信に必要なさまざまなテクニックも含まれています!

📌継承やジェネレーターは難しい方がいらっしゃるので、Pythonの中級以上の文法は説明を入れておきました!

こんな方におすすめです

バックエンド開発でレベルアップしたいです。

Pythonの勉強を終えてバックエンドアーキテクチャを勉強したい方! gRPCという新しい武器を装備しよう!

RESTful API開発者
gRPCはRESTfulとは異なる強みを持っています!二人を知れば知識が倍増!

gRPCを学びたいのにGo言語は学びたくない!
APIアーキテクチャを学ぶために新しい言語を学ぶ?とても大変でしょう!知っていることを学びましょう!

受講後は

  • gRPCの概念と文法を学ぶことができます。

  • さまざまな通信パターンを学び、実際のサービスを作成できます

  • さまざまな通信技術により、信頼性が高く効率的な通信サーバーを構築できます。

このような内容を学びます。

gRPCの概念と特徴!

gRPCの基本概念から特徴!様々なメリットまで調べましょう! gRPCならではの味がわかります!

様々なストリーミングパターン!

gRPCがサポートするさまざまなストリーミングパターンを実践することで、自分が望むサービスを作成するのに役立ちます。

Protocol Buffers!

簡単で強力なインターフェイス定義言語(IDL)プロトコルバッファ!とても良いですが、勉強資料がありません!簡単に学びましょう!

様々な通信技術!

サーバーとクライアントで利用可能なさまざまな通信技術を学びます! gRPCをもっと知ってください!

この講義を作った人

  • 2019〜2023年:ソウル大学修士課程

  • 2023~2024:トップティアスタートアップでAI研究とAIバックエンド開発!

  • 2024~: Inflearnインストラクター

  • 2024〜:sコーディングクラブマシンラーニングディープラーニングオンラインチューター

受講前の注意

練習環境

  • 講義はMacOSで説明します。 Windowsも説明するので心配しなくてもいいです!

  • Python

選手の知識と注意事項

  • 基本的なPython文法

こんな方に
おすすめです

学習対象は
誰でしょう?

  • Backend candidate who has finished studying Python syntax!

  • RESTful developer

  • Someone who wants to learn the backend framework gRPC

  • For those who want to learn gRPC with Python, not Go!

前提知識、
必要でしょうか?

  • Python

こんにちは
です。

253

受講生

17

受講レビュー

17

回答

4.1

講座評価

2

講座

:)

カリキュラム

全体

23件 ∙ (3時間 32分)

講座掲載日: 
最終更新日: 

受講レビュー

全体

7件

4.0

7件の受講レビュー

  • szsddd님의 프로필 이미지
    szsddd

    受講レビュー 2

    平均評価 5.0

    5

    17% 受講後に作成

    🙊🙊😃

    • tech2622님의 프로필 이미지
      tech2622

      受講レビュー 1

      平均評価 5.0

      5

      100% 受講後に作成

      The content is good for beginners, but it is annoying that "we" is always expressed as "us". The learners and the instructor are "us", and if there is an instructor and the instructor's staff, that group is "us" from the learners' perspective. I think that grammatical errors in oral speech are a huge risk in online lectures. I believe that you will be able to achieve better results if you improve them. -------------------------- (I will add the content after completing the lecture) I polluted the course review with Dae-heon feedback on parts unrelated to the lecture, but after completing the lecture, I found the entire lecture content very helpful to me. I took this course because I wanted to reorganize the basics and get rid of the amateurish(?) feeling of learning and using gRPC as an attribute out of necessity in the field, but it helped me understand the basic concepts and elements with easy examples better than I expected, and it introduced client concurrency processing and gRPC from an MSA perspective... I'm interested in gRPC but it's vague, or I've only dealt with RESTful APIs, so I didn't really feel like I could really use gRPC, so I think this was a great course to get started on, as it reduced my resistance.

      • baekoblin
        知識共有者

        First, I will tell you that I will answer by referring to the National Institute of the Korean Language and the Standard Korean Dictionary. Hello, this is instructor Baekoblin. I will answer after checking the part you mentioned! If I check the usage examples of the information you provided, it seems that you suggested that we use the expression 'we' if the listener is included, and 'our' if not. This is one of the parts that I had a lot of trouble with when writing the script. In terms of dictionary meaning, grammar, 'we' has the following meanings. 1. "A first-person pronoun that refers to the speaker and the listener, or multiple people including the speaker and the listener" 2. "A first-person pronoun that refers to multiple people including the speaker when the speaker is not higher than them" In terms of dictionary meaning, 'we' is a polite expression for 'we'. In this case, it plays the role of a polite expression for two of the three meanings that 'we' has. When using we, it is said that the listener is honored by lowering the group to which they currently belong. Therefore, it is said that it is natural to use it when the listener is excluded from the group. The cases in which we can be used can be summarized as follows: 1. When the person being addressed is not higher than me. 2. When expressing a close relationship with oneself In the case of online lectures, the use of we and our is said to be somewhat ambiguous. In the case of the current listener, it is not guaranteed that the speaker is not higher than the listener, as in the case of teachers and students, and since an unspecified number of people can take the class, care must be taken when using expressions of equal status, However, using we lowers the group to which the speaker belongs, and since the listener is included in the class, it may not be natural because both honorific and derogatory expressions are included at the same time. However, if we organize this and think about the usage, "we" can be used when using the polite expression "our", and "our" can be used when using a more friendly and informal expression. Especially considering that in most scripts, we are used in abbreviated situations such as "our course" or "our course", it is said that the lowering of "we" is mostly an expression that lowers the course and raises the students. Thank you.

      • In this lecture, it is clearly correct to say "our" because it corresponds to both dictionary grammar 1 and 2. The dictionary explanation is ambiguous, but in order for us to be a polite expression, we need to assume that the listener does not belong to the group to which we belong. In other words, only when the listener does not belong to the group to which we belong and is a person of higher status than us can we use "our" to belittle the group to which we belong. Conversely, even if the listener is a person of higher status than us, if that listener is a person of higher status than us, we can only use "our". A typical example is when Koreans unconditionally refer to their home country as "our country", and since both the listener and the speaker belong to the same country, it becomes "our country" regardless of their status. A foreigner who misunderstood this as a proper noun appeared on TV and told the viewers (higher-ranking people) that his or her home country was "our country". This is an example of how referring to it as "we" can be unintentionally rude. Therefore, since the learners and the instructor are in the same boat called a specific lecture, I can cautiously confirm as one who majored in language that there is no option to be humble and can only refer to it as "we". Somehow, it became a debate on a topic that was not related to the lecture itself, but I did not intend to pick a fight. Since the expression that Koreans most often misuse is "we", which is used indiscriminately in different situations, I am absolutely not trying to point out that Baekoblin is particularly wrong. I just left feedback in the hope that you will correct the wrong expression and do better in the future, so I hope you do not think badly of it.

    • bluaura0929님의 프로필 이미지
      bluaura0929

      受講レビュー 4

      平均評価 5.0

      5

      100% 受講後に作成

      I was curious about gRPC, and I understood it well because it was explained in detail. It seems like the best gRPC lecture. If I had tried Java or other languages just a little bit, I think I would have been more impressed by the microservice architecture and gRPC lecture.

      • tromberx2696님의 프로필 이미지
        tromberx2696

        受講レビュー 1

        平均評価 5.0

        5

        30% 受講後に作成

        • kmkang2281님의 프로필 이미지
          kmkang2281

          受講レビュー 6

          平均評価 4.8

          4

          61% 受講後に作成

          The lecture is good, but I can't find the source code you said you'd upload to GitHub, so I deducted one star.

          ¥3,667

          baekoblinの他の講座

          知識共有者の他の講座を見てみましょう!

          似ている講座

          同じ分野の他の講座を見てみましょう!