anchor.diff:  ----
           CloudBalance unsolvedCloudBalance = new CloudBalancingGenerator().createCloudBalance(400, 1200);
   ----
  -* Solve the problem.
  +
  +. Solve the problem.
   +
   
   [source,java,options="nowrap"]
   ----
           CloudBalance solvedCloudBalance = solver.solve(unsolvedCloudBalance);
   ----
  -* Display the result.
  +
  +. Display the result.
   +
   
   [source,java,options="nowrap"]
  
positive.code: Of course, Planner needs to be told about these domain-specific score constraints.
  There are several ways to implement such a score function:
  
  * Easy Java
  * Incremental Java
  * Drools
  
  Let's take a look at two different implementations:
  
  
  [[cloudBalancingEasyJavaScoreConfiguration]]
  
negative.code:     <!--<scoreDrl>org/optaplanner/examples/cloudbalancing/solver/cloudBalancingScoreRules.drl</scoreDrl>-->
    </scoreDirectorFactory>
  ----
  . **Optimization algorithms configuration** 
  How should Planner optimize it?::
  +
  In this case, we use the default <<optimizationAlgorithms,optimization algorithms>> (because no explicit optimization algorithms are configured) for 30 seconds:
  +
  