just looks like request-response model, but it may contains some complicated process behind. Let say about: validation, check data in cache, query in database, or even calling 3rd party service or another internal service. • We may can see log, but reading log generally is hard to see what system’s do in behind.
of embarking on quests related to an activity that she wants to partake of or a place that she wants to go to. • Each episode is based around a series of cyclical events that occur along the way during Dora's travels, along with obstacles that she and Boots are forced to overcome or puzzles that they have to solve relating to riddles, the Spanish language, or counting. To see which route she should take, she always ask to Map:
that: • Dora’s mission is the one API request in server. • Map is the route from user’s request to response. • Obstacle is like a function. So, to finish one mission/travel, Dora may face several obstacles. Dora the Explorer map template. Source: https://commixus.com/dora-the-explorer-map-template-58475/ (accessed at 2 Dec 2018.)
want Dora to report to us what causing her to take the long time and every detail that she may find it good to report. • So, Dora can records the start time and end time of each obstacle, note some additional information when you find it useful to report, etc. Dora will leave a footprint in each of obstacle. Here's the visual: