1. 28

This actually uses the Lobsters codebase as the example!

  1.  

  2. 10

    Hey @mtnygard, I’m thrilled to see the Lobsters codebase used to help teach, thanks for writing this up.

    One thing I don’t love in the Lobsters codebase is that it’s very relaxed about RESTfulness. I’ve specifically considered reworking the hat code to separate hats from hat requests, each with the standard REST verbs. I’ll have to read some more of your blog posts, because I can’t make it down to Florida for your workshop. :)

    1. 7

      Alas, the Florida workshop didn’t happen. Somehow I couldn’t convince enough people to come to Florida in March when it was still blizzards and nor’easters up north.

      I’ll have more to come on the topic of hats, but take it with a grain of salt. My audience is people who’ve already decided that microservices make sense for them. I really don’t know that the added complexity and operational expense would be right for Lobste.rs.

      I picked this code base because I think it’s good for teaching. It is a well structured monolith in a domain with which most people will be familiar.

      1. 4

        It is a well structured monolith in a domain with which most people will be familiar.

        I really wish more people were comfortable with the idea of such things. Thank you for mentioning it!

        1. 3

          Ah, too bad. Good luck in the future, and please share your blog posts (especially those that happen to use our codebase).