1. 3

  2. 4

    Other thoughts:

    • What benefit do the pictures add to the discussion? They seem entirely superfluous.
    • The code sample is formatted very oddly. Also, if you’re creating raw SQL queries, make sure you are properly escaping everything. (Maybe db.query does that already?)
    • What do MVC and ORMs have to do with microservices?
    • “Design Patterns are relevant for a code base that is already big and in the next 6-12 months is going to be bigger, your usual monolith.” This seems like a very dubious assertion.
    1. 1
      • Well the pictures do break up the page and improve readability.
      • The code is formatted oddly.
      • I imagine some people try to write a microservice to have a model, view and controller, they also add an ORM.
      • Try to use design patterns in a script that is under a hundred lines, and I think you’ll better understand what the author intended.
    2. 3

      Few thoughts:

      1. At least on Android Firefox, the code sample is extremely difficult to read. In particular it requires a lot of scrolling and is not monospaced for some reason.
      2. The code snippet would have been considerably cleaner and smaller with an ORM :p I get the value of avoiding them, but a simple “filter query” is like the perfect use case for them.
      3. This seems like it’s missing the forest for the trees. If you’re writing 1k line microservices, you’re going to have much, much bigger design challenges than local overengineering. I think most people want “microservices” when they actually need “services” or “modules”.
      1. 1

        “Code in code” has terrible support in most languages and editors. I also agree with point 3, mostly.

      2. 1

        FYI, uMatrix blocks your codeblock (external reference from gist.github.com).