Many teams adopting Infrastructure as Code end up with monolithic infrastructure. But many of the principles for microservices software architecture apply just as well to infrastructure: small, focused capabilities that can be delivered independently. This talk explores how team structures and microservices principles apply to infrastructure, and describes some patterns and anti-patterns. These are applicable whatever tools are used, whether it's Terraform, CloudFormation, Puppet, Chef, Ansible, or others. It also applies to all infrastructure platforms, whether it's an IaaS cloud like AWS or OpenStack, a virtualized platform, or even physical hardware.