このページはAIで翻訳されています。コミュニティによるレビューはまだ行われていません。 英語で読む

Beam Me Up, Codey! Serialization and Deserialization: The Star Trek Transporters of Integrations (in English)

Updated 2026-11-07
Published 2023-09-04 · update checked 2026-11-07 · Watch on YouTube

What's changed since the video

Each change is dated and checked against Salesforce's own documentation.

  • Little has changed in the platform here. JSON is still the usual format for new APIs, and the ideas are the same.
  • Matching is the rule, the exception has a reason. The course says the request and the answer match nearly every time, and treats a different answer format as a deliberate design, not something to expect (chapter 3, modules 3 and 4). Not a platform change.

Still right

  • The transporter: one side turns its data into a format for the wire (serialization), and the other side turns it back into its own (deserialization).
  • The formats: XML, JSON, fixed length and binary, each still in use somewhere.
  • The answer can come back in a different format from the request, for a reason: a form in, a generated document back; a document in, a receipt back.

All videos in this series: 統合アーキテクチャ

動画は、クリックしたときにだけ YouTube から読み込まれます。