Ruby doesn't have "interfaces" - obviously, because it doesn't have types or a type-enforcement. So any design pattern, architecture or concept that relies on

Ruby doesn't have "interfaces" - obviously, because it doesn't have types or a type-enforcement. So any design pattern, architecture or concept that relies on types, or interfaces, are "limited" in that sense. Ports, Adapters, Strategy, for example " require" interfaces in their definition. Their benefits rely on interfaces, so if a language lacks this, you really only get the downsides. Factory, Observer, Decorators, etc mention them, and use them, but can be implemented without them. Maybe "limitations" isn't the best word, because e.g. "an interface" is a deliberate limitation, imposed and designed by the developer.