Was well received by the team even if some of it we’re doing now on the app level… but interesting to see it applied to servers as well.
I’ve had a bunch of articles in draft form for a while and Jira outage has inspired me to actually finish one off – here are my patterns for sensible unit testing. I have more to write on this on future as I’ve really only covered some very basics at this point.
Comments are very welcome!
Today I ran a lunch’n’learn around MassTransit and event driven architecture. In addition to some demo code, we watched the video below. It covers things quite nicely, not a lot of detail in the demonstration but as it’s MassTransit 2.x (not 3.x) that was OK. Quality is good, speaker is a little drone-y so a bit of snooze-danger if you’ve had too much pizza!
A little while ago we did a RESTful API lunch’n’learn session. These are the videos that we used.
This video from Stormpath covers a lot from basics to good patterns to use – it’s also good quality and as a speaker he’s quite animated so this kept our attention:
For those people who’ve used more SOAP services this video has been good to help compare approaches – however it does seem as if the presenter prefers SOAP (what else would you expect from Oracle?) so you have to apply your own salt:
Here’s a quick overview of the properties of the HTTP verbs (this applies to more than just REST APIs!):
GET – Safe, Idempotent
PUT – Idempotent
DELETE – Idempotent
HEAD – Safe, Idempotent
POST – (none of these)
Safe: Makes no change to the server / performs no action. For e.g. reading an entity is a safe, incrementing a counter or sending an e-mail is not.
Idempotent: Doing this multiple times is the same as it doing it just once. For e.g. “a = 1” is idempotent. “a += 1” is not.