New roadmap proposal: Integration Engineer

未关闭
  • 哪里不对？
#10,436 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 小时 16 分钟
30 天内合并 PR
99

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

nilbuild/developer-roadmap 的其他 Issue

查看 nilbuild/developer-roadmap 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。