...

1. VXLAN/EVPN fabric between core/dist (leaf/spine) devices, IPv4 routed/L3 point-to-point links between core/dist
2. Deploy dist switches in pairs, with access switches connected redundantly to two dist switches
3. Core devices are only used for connecting distribution switches, external connectivity, firewalls etc are all connected to dist switches (possibly dedicated border dist)
4. Each dist/core device has two loopbacks, one in global/main VRF used for EVPN peering ("infra loopback") and one loopback in a dedicated management VRF ("management loopback")
5. Core devices are only used for connecting distribution switches. External connectivity, firewalls etc are all connected to dist switches (possibly dedicated border dist)
6. Deploy dist switches in pairs, with access switches connected redundantly to two dist switches
7. Mature API for management and monitoring (Netconf, SNMP etc)

...

• Arista EOS: 7050X, 7280 running EOS v4.24 for ESI with routing/IRB. "FLX Lite" license
• Cisco NX-OS: Nexus9000, Nexus3000 running NX-OS version ?
• Cisco IOS-XR: NCS5000 running version ?
• Cisco IOS-XE: Catalyst9000 running version 17.3 for EVPN?
• Juniper JunOS: MX or QFX running version ?

Special considerations for non-standard design:

If using JunOS with only two dist switches (no core layer) you should disable isolation to get working redundancy: https://www.juniper.net/documentation/us/en/software/junos/evpn-vxlan/topics/concept/evpn-vxlan-core-isolation-disabling.html