Comments by "Brent Jacobs" (@br3nto) on "NDC Conferences" channel.

  1. 37:29 this isn’t how you’d write caching code? Why not? It’s like every single example ever given on the web. I lol when people say “this isn’t production ready code”… ok, well just show the production ready code instead of the simplified “never use this in production” code so we can all see what production code actually looks like and what we should be doing instead. Don’t perpetuate what we shouldn’t be doing in prod.
    7
  2. What did you want to see?
    3
  3. Great observation! This is where we’re at with some of my companies apps. There is an http layer around a MediatR layer which interacts with an ORM layer. It does provide a level of abstraction so we can independently change the public API from the internals, and the http layer only provides http specific mappings to internal API calls, but it’s just become another N-tier app based on these newer concepts.
    2
  4. 34:22 with problem number 2 with the example of creating a room in an admin module and service subscribe to that and create their own room record… when a new service is added, what is the corresponding way of populating the existing rooms for that service?
    2
  5.  @GeorgianGrec  could send a message to request the full list, I guess.
    2
  6. I dunno…. Sounds like it all belongs together
    2
  7. 18:35 yes!! This!
    1
  8. 5:37 “select is the last thing to run… with declarative we are not concerned with the order of operations” whoever put SELECT first in an SQL statement was an idiot, and therefore SELECT is a terrible example of declarative programming… or a good example of how it can be bad.
    1
  9. 14:25 add a db record with the minus amount with effective date set 1 week in the future
    1
  10. Or the service could request the room details at the time it needs it
    1
  11. 35:10 wait… why do we want immutability? Are there scenarios we need to be aware of where we are making trade offs for something else? Eg performance?
    1