remove demo story code since that's outdated

Author: foxish

src/checkoutservice/README.md

@@ -93,14 +93,3 @@ Setting orderid into Baggage
 	bags, _ = bags.SetMember(orderIDMember)
 	ctx = baggage.ContextWithBaggage(ctx, bags)
 ```
-
-## Demo Story code
-
-In order to produce an effective demo story, this service includes additional functionality.
-This service will grow an internal cache with each request.
-Eventually, the cache size will grow large enough to cause an out of memory (OOM) error and crash the service.
-The cache size is exposed via an internal call, so the frontend can properly assign a problematic userid when a cache size threshold is reached.
-When an order is placed, an additional delay through `getDiscounts` may be introduced.
-In this function, if a random chance exists to call the `loadDiscountFromDatabase` function, which will introduce a synthetic delay based on cache size.
-The synthetic delay is manifested as a series of spans making mock database calls.
-User "20109", whom should only show up when cache size is high, will have a higher likelihood to exhibit the delay.

src/frontend/README.md

@@ -111,10 +111,3 @@ The userid and requestid will be available to all downstream spans.
 
 Baggage is propagated to downstream services, but by default it is not exported to your telemetry backend.
 A Span Processor that explicitly exports Baggage is required to export this data to a telemetry backend like Honeycomb.
-
-## Demo Story code
-
-In order to produce an effective demo story, this service includes additional functionality.
-The `ensureSessionID` function in `middleware.go` assigns user ids in a random fashion, which may be affected under other random condition, when the cache size from the checkout service exceeds a threshold.
-The application will enter a degraded state of performance when cache size climbs.
-The checkout service has code to continuously grow a cache, until memory is exhausted and the service crashes with an out of memory (OOM) error.