Yeah, you are right, that’s your feature - jumping to conclusions based on your imagination only.
You call imagination the fact that i can see with my eyes 3 different subnets on the provided photo ?
Really ? 
I ve seen many times as well enginneers not seeing the obvious… no offense too…
since you use VLANs with different subnets in some point of time for some reason you will need a L3 isolation… so yes am a step ahead.. in time zone too…
So i am twice ahead
There is no doubt about 3 different subnets, but this fact does not imply in any way that you need to take any special measures to isolate them from one another if you use VLAN-aware switches instead of routers on the picture. The L3 isolation is automatically provided by the “L2.5” isolation, i.e. the VLANs: as the tagging and untagging is provided by the switches and only one VLAN is permitted on each port except the trunk one facing towards the remote switch, there is no way how the three L3 subnets could talk to each other even if some device connected to one of the access ports was clever enough to handle tagged frames.
In fact, in such a setup you need a router to allow communication between the VLANs, not to block it.
I always thought Moscow time was ahead of Athens time (at least during winter).
@richard_s, for me, “programming” means expressing algorithms (something like if condition then action_x else action_y). Stay assured that you don’t need programming in this sense to obtain your goal. Speaking in hardware language, as a frame is being received from the wire via a switch port which is configured as an access one to a VLAN, four bytes (a VLAN tag) get inserted into its header if the destination port isn’t an access one to the same VLAN; in the mirror scenario, if the received frame contains a VLAN tag whose VLAN ID part matches the one of the destination port, the four bytes of the tag get removed. So on the cable between the two sites, frames belonging to each VLAN are sent with tags, and on the access port to each VLAN the tags are added/removed so the connected equipment doesn’t know anything about their existence. The only difference as compared to three separate cables is that the VLANs share (in other words, compete for) the common bandwidth of the interconnecting link.
If you have a device with at least an 8237 switch chip (when talking about the Mikrotik production), such as hAP ac², you can set it up so that the VLAN tagging and untagging really happened in hardware, so the CPU wouldn’t have to touch the frames at all.
Yup… That right there. If no switch is layer 3 or a router… You are not getting from one subnet to the others.
And like xvo posted…
I see managed switches when I see this diagram.
Whatever.
You can continue to pretend that you still don’t understand in what context me and others are talking about not needing routers in the provided picture.
Obviously you do understand, so I don’t see a point to continue arguing about it.
Thanks all for your input I have been looking at it the wrong way (the hard one) it is looking simpler than I thought. Will set up on the bench and get working then deploy.