Switching to Middleware Development: Is It Too Late? A Veteran’s Guide

Recently I often interact with internship candidates, and the most common question is "What does a middleware team do?" I also get asked whether it’s still possible to switch to middleware development, so I wrote this article to share my experiences.

What is Middleware Development?

During my senior‑year internship I first encountered middleware when the architect introduced the open‑source RPC framework Motan, which helped us quickly build a micro‑service based internal e‑commerce system. Later we added ActiveMQ, so I was using middleware but not yet developing it.

After graduation I joined a company with a few hundred engineers; the leader, noticing my interest, placed me in the infrastructure team where I became a middleware developer. My work involved customizing open‑source projects such as Kong and Dubbo for internal use, learning Docker, Neo4j, and deepening my understanding of RPC frameworks.

Now I work at Alibaba Cloud’s cloud‑native middleware division. In large internet companies each middleware product may have a dedicated team of several to dozens of engineers, and the middleware department has clear boundaries from business teams. The responsibilities can be divided into three directions:

Providing customized solutions for internal business teams (often called “self‑developed” middleware such as HSF, Diamond).

Contributing to open‑source projects and improving performance and influence (e.g., Dubbo, Spring Cloud Alibaba, RocketMQ, Nacos).

Delivering commercial cloud products with higher SLA and richer features (e.g., MSE, RocketMQ, ARMS).

These three experiences illustrate how companies of different scales have different middleware needs. Small companies let business developers maintain RPC, MQ, cache, etc., while larger teams build dedicated middleware groups or adopt cloud‑provider solutions.

Differences Between Middleware Development and Business Development

In my view there is no hierarchy between the two; it’s like choosing a class in a game—some become mages (middleware) and others warriors (business). Business developers spread their skills across many areas, while middleware developers focus deeply on a specific domain.

If a small company is about to form a middleware team, the likely candidates are those with solid fundamentals, a strong interest in middleware, and experience reading source code. The boundary is not fixed, so anyone with passion and code‑level knowledge can transition.

Qualities Required for Middleware Developers

In larger organizations responsibilities are more vertical, and a developer may spend years specializing in one area. Common middleware directions include:

Micro‑service governance (RPC frameworks, service registries, config centers, rate limiting, tracing). Open‑source examples: Dubbo, Spring Cloud, Nacos, Zookeeper, Sentinel, Hystrix, Zipkin.

Message queues (asynchronous communication). Open‑source examples: RocketMQ, Kafka.

Storage middleware such as caches and databases (MySQL, Redis). In Alibaba these are considered on par with middleware.

Storage proxies, e.g., ShardingSphere.

Gateways like Spring Cloud Gateway, Kong, Nginx.

Service mesh (Envoy, Istio).

Beyond domain knowledge, a middleware engineer should master:

Programming fundamentals in Java: collections, concurrency, JVM, common utilities.

Operating‑system concepts: file I/O (page cache, mmap, direct I/O), processes and threads (green threads, coroutines), memory/CPU (cgroup, cache line, bound core).

Network fundamentals: TCP, HTTP, NIO, Netty, gRPC, HttpClient.

Distributed‑system theory: CAP, Paxos, Raft, Zab, 2PC/3PC, BASE.

Source‑code reading ability to learn design patterns from open‑source middleware.

Continuous technical enthusiasm and ability to adapt to changes, such as cloud‑native trends and Kubernetes concepts (pod, service, deployment, StatefulSet, operator).

How to Become a Middleware Developer

Although the requirements may seem daunting, they are comparable to learning Java fundamentals. Practical steps include:

Contribute to open‑source middleware projects by solving issues and studying the code.

Hands‑on experiments, such as building a simple RPC framework, implementing a Raft POC, or benchmarking FileChannel vs. mmap.

Participate in middleware performance contests hosted by companies like Alibaba or Huawei.

For further reading, the author recommends several accessible articles covering topics such as configuration‑center long‑polling, off‑heap memory monitoring, heartbeat design, TCP long connections, file I/O best practices, and contributing to Dubbo.

Middleware Welcomes You

If you are a business developer considering a move to middleware, the best time is right after graduation—or now. Why not give it a try?