ChallengeModifying execution approaches

time to read 5 min | 968 words

In RavenDB, we had this piece of code:

internal T[] LoadInternal<T>(string[] ids, string[] includes)
        {
            if(ids.Length == 0)
                return new T[0];

            IncrementRequestCount();
            Debug.WriteLine(string.Format("Bulk loading ids [{0}] from {1}", string.Join(", ", ids), StoreIdentifier));
            MultiLoadResult multiLoadResult;
            JsonDocument[] includeResults;
            JsonDocument[] results;
#if !SILVERLIGHT
            var sp = Stopwatch.StartNew();
#else
            var startTime = DateTime.Now;
#endif
            bool firstRequest = true;
            do
            {
                IDisposable disposable = null;
                if (firstRequest == false) // if this is a repeated request, we mustn't use the cached result, but have to re-query the server
                    disposable = DatabaseCommands.DisableAllCaching();
                using (disposable)
                    multiLoadResult = DatabaseCommands.Get(ids, includes);

                firstRequest = false;
                includeResults = SerializationHelper.RavenJObjectsToJsonDocuments(multiLoadResult.Includes).ToArray();
                results = SerializationHelper.RavenJObjectsToJsonDocuments(multiLoadResult.Results).ToArray();
            } while (
                AllowNonAuthoritiveInformation == false &&
                results.Any(x => x.NonAuthoritiveInformation ?? false) &&
#if !SILVERLIGHT
                sp.Elapsed < NonAuthoritiveInformationTimeout
#else 
                (DateTime.Now - startTime) < NonAuthoritiveInformationTimeout
#endif
                );

            foreach (var include in includeResults)
            {
                TrackEntity<object>(include);
            }

            return results
                .Select(TrackEntity<T>)
                .ToArray();
        }

And we needed to take this same piece of code and execute it in:

  • Async fashion
  • As part of a batch of queries (sending multiple requests to RavenDB in a single HTTP call).

Everything else is the same, but in each case the marked line is completely different.

When we had only one additional option, I choose the direct approach, and implement it using;

public Task<T[]> LoadAsync<T>(string[] ids)
{
    IncrementRequestCount();
    return AsyncDatabaseCommands.MultiGetAsync(ids)
        .ContinueWith(task => task.Result.Select(TrackEntity<T>).ToArray());
}

You might notice a few differences between those approaches. The implementation behave, most of the time, the same, but all the behavior for edge cases is wrong. The reason for that, by the way, is that initially the Load and LoadAsync impl was functionality the same, but the Load behavior kept getting more sophisticated, and I kept forgetting to also update the LoadAsync behavior.

When I started building support for batches, this really stumped me. The last thing that I wanted to do is to either try to maintain complex logic in three different location or have different behaviors depending if you were using a direct call, a batch or async call. Just trying to document that gave me a headache.

How would you approach solving this problem?

More posts in "Challenge" series:

  1. (26 Jul 2016) The race condition in the TCP stack, answer
  2. (25 Jul 2016) The race condition in the TCP stack
  3. (28 Apr 2015) What is the meaning of this change?
  4. (26 Sep 2013) Spot the bug
  5. (27 May 2013) The problem of locking down tasks…
  6. (17 Oct 2011) Minimum number of round trips
  7. (23 Aug 2011) Recent Comments with Future Posts
  8. (02 Aug 2011) Modifying execution approaches
  9. (29 Apr 2011) Stop the leaks
  10. (23 Dec 2010) This code should never hit production
  11. (17 Dec 2010) Your own ThreadLocal
  12. (03 Dec 2010) Querying relative information with RavenDB
  13. (29 Jun 2010) Find the bug
  14. (23 Jun 2010) Dynamically dynamic
  15. (28 Apr 2010) What killed the application?
  16. (19 Mar 2010) What does this code do?
  17. (04 Mar 2010) Robust enumeration over external code
  18. (16 Feb 2010) Premature optimization, and all of that…
  19. (12 Feb 2010) Efficient querying
  20. (10 Feb 2010) Find the resource leak
  21. (21 Oct 2009) Can you spot the bug?
  22. (18 Oct 2009) Why is this wrong?
  23. (17 Oct 2009) Write the check in comment
  24. (15 Sep 2009) NH Prof Exporting Reports
  25. (02 Sep 2009) The lazy loaded inheritance many to one association OR/M conundrum
  26. (01 Sep 2009) Why isn’t select broken?
  27. (06 Aug 2009) Find the bug fixes
  28. (26 May 2009) Find the bug
  29. (14 May 2009) multi threaded test failure
  30. (11 May 2009) The regex that doesn’t match
  31. (24 Mar 2009) probability based selection
  32. (13 Mar 2009) C# Rewriting
  33. (18 Feb 2009) write a self extracting program
  34. (04 Sep 2008) Don't stop with the first DSL abstraction
  35. (02 Aug 2008) What is the problem?
  36. (28 Jul 2008) What does this code do?
  37. (26 Jul 2008) Find the bug fix
  38. (05 Jul 2008) Find the deadlock
  39. (03 Jul 2008) Find the bug
  40. (02 Jul 2008) What is wrong with this code
  41. (05 Jun 2008) why did the tests fail?
  42. (27 May 2008) Striving for better syntax
  43. (13 Apr 2008) calling generics without the generic type
  44. (12 Apr 2008) The directory tree
  45. (24 Mar 2008) Find the version
  46. (21 Jan 2008) Strongly typing weakly typed code
  47. (28 Jun 2007) Windsor Null Object Dependency Facility