Infrastructure is about (visualized) hardware, network management, storage, failover/load balancing, backups, etc. They are the things that you software runs on but which is not explicitly part of the software. Generally you can switch infrastructure without changing the software.
Middleware is basically every supporting software you use. Like, memory cache servers, message bus, API gateways, authentication servers. Things your software explicitly interacts with. You often cannot change these without also changing your software.
Infrastructure is about (visualized) hardware, network management, storage, failover/load balancing, backups, etc. They are the things that you software runs on but which is not explicitly part of the software. Generally you can switch infrastructure without changing the software.
Middleware is basically every supporting software you use. Like, memory cache servers, message bus, API gateways, authentication servers. Things your software explicitly interacts with. You often cannot change these without also changing your software.
There are no rules for what a full-stack developer should, hence this article. It's a misunderstood term.