New roadmap proposal: Integration Engineer

オープン
  • 何か問題がありますか？
#10,436 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
content

調査の方向性

Start by reading contributing.md and reviewing existing roadmap formats; the proposal says the roadmap would be built in the roadmap editor at draw.roadmap.sh, with topic content and project briefs. Determine whether the team accepts the proposed scope, then create the roadmap and supporting content in the accepted format. Done means the roadmap covers the proposed integration topics and projects and follows the repository's contribution format.

索引モデルが issue の本文から書いたものです。

説明

Why an Integration Engineer roadmap?

Most production software is glue: payments, CRMs, Git hosts, messaging, data
warehouses and, more and more, LLM APIs. "Integration engineer" is a common
job title (and a big part of many back-end, platform and solutions-engineer
roles), but there is no roadmap that teaches the skills specific to it:
consuming third-party APIs reliably, handling webhooks and events, syncing
data between systems that disagree, and running all of that safely in
production.

Who is it for?

Beginner to intermediate developers who already know one programming
language and want to build integrations that hold up in production, plus
back-end developers moving into integration, platform or solutions roles.

How is it different from existing roadmaps?

  • API Design is about designing and publishing APIs. This roadmap is
    about consuming other people's APIs: pagination styles, rate limits,
    retries, idempotency, version changes you don't control.
  • Back-end covers building a service. This roadmap focuses on what
    happens between services: webhooks, queues, delivery guarantees, data
    mapping and synchronization.
  • AI Engineer covers building with models. The AI section here is narrow
    on purpose: wiring LLM APIs into existing systems (streaming, tool calling,
    structured outputs, retries and cost).

It links to Back-end and API Design as prerequisites/related roadmaps rather
than repeating them.

Textual roadmap

Textual version of the proposed Integration Engineer roadmap

  • Prerequisites (link to other roadmaps)
    • One programming language
    • Git and the command line
    • Back-end roadmap basics
  • Fundamentals
    • Networking Basics
    • HTTP and HTTPS
    • HTTP Status Codes
    • Request / Response Structure
    • Data Formats
      • JSON
      • XML
    • REST APIs
  • Authentication and Authorization
    • API Keys
    • OAuth 2.0
    • JWT
    • Access and Refresh Tokens
    • Token Expiry and Renewal
    • Scopes and Permissions
  • Consuming APIs Reliably
    • Pagination
    • Rate Limiting
    • Retries and Timeouts
    • Error Handling
    • API Versioning
    • Idempotency Keys
    • SDKs and API Clients
  • Event-Driven Integration
    • Webhooks
    • Message Queues
    • Event-Driven Architecture
    • Asynchronous Processing
    • Delivery Guarantees
    • Duplicate Event Handling
    • Dead-Letter Queues
  • Data Integration
    • Data Mapping
    • Data Transformation
    • Schema and Data Validation
    • Handling Inconsistent Data
    • ETL Fundamentals
    • Data Synchronization
    • Incremental Synchronization
  • AI Integrations
    • LLM APIs
    • Streaming Responses
    • Tool / Function Calling
    • Structured Outputs
    • AI Workflow Integration
    • Connecting AI to External APIs
    • AI API Errors and Retries
    • Token Usage and Cost
  • Reliability and Security
    • Secrets and Credential Storage
    • Webhook Signature Verification
    • Logging, Monitoring and Observability
    • Integration Testing
    • Circuit Breakers
    • Failure Recovery
    • Production Deployment
  • Projects
    • Payment Gateway Integration
    • GitHub Webhook Automation
    • Multi-API Aggregation Service
    • AI-Powered Integration Service
    • Event-Driven Notification System
    • Data Synchronization Service

I'm happy to build this in the roadmap editor (draw.roadmap.sh), write
topic content, and write the project briefs in the format from
contributing.md if the team is interested.

主要言語
TypeScript
スター
371k
フォーク
45.3k
平均マージ
6時間 51分
マージ済み PR（30日）
96

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nilbuild/developer-roadmap のほかの issue

nilbuild/developer-roadmap の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。