The algorithm for generating Mendix IDs does increment only in an ascending order. However, I think the ID column has a similar issue to the createDate. Mendix runtimes pre-reserve a set of IDs ahead of time for each entity, so if you have more than 1 runtime (horizontal scaling) then IDs could potentially be committed out of order.
You should not rely on the ID, especially if you run multi-instance. Each runtime caches 100 ids, and them assigns them as needed. This means that the following record ids can be inserted into your entities in this sequence: 1,2,100,101,3,4,102,104. Now, if halfway you query the new records by selecting everything above 101, you will never receive id 3 & 4.