扩展工厂级别是一种反模式吗？

Question

Let's say that there is a CarFactory class and it is extended by classes like FerrariFactory and VolvoFactory . Each class has a List<Car> build(List<CarPart>) method

Now a requirement comes up that for any given List<CarPart> the optimal list of Cars must be returned.

Would it be an anti-pattern to put the logic in CarFactory.build ?

CarFactory
    List<Car> build(List<CarPart>)
        split car part list into optimal car part sub-lists for each factory
        instantiate car factories and pass in the sub-list of car parts
        return collection of cars

Or would it be better to have another class like a CarBuilder class does this?. Is there a typical design pattern I can use to solve this problem?

Answer 1

I think, any logic in builder is anti pattern, because, instantiate new object should be very fast and quite. I mean, that maximum code in builder - only one operator new ClassName(params...) . if you need any logic - move it to new small class, which solve this:

List <Car> CarFactory.build (params...) {
  return new CarLogicSolver(params).list();
}

you can see great examples in java.util.stream.Collectors.toSet, .toList, toMap etc.