“Rest APIs are REST-in-Peace APIs. Long Live GraphQL.” is yet another look at REST vs. GraphQL for the API implementation.
I’m involved with developing quite a bit of REST APIs at work, but for now we are just trying to buy us some time. I want to take a really long and good look at GraphQL, but I don’t think this will happen this year. In the meantime, if you have any good GraphQL resources, please do send them my way.
“Passwords Evolved: Authentication Guidance for the Modern Era” is a good collection of guidelines and concerns for password management in the modern day.
Here’s the bigger picture of what all this guidance from governments and tech companies alike is recognising: security is increasingly about a composition of controls which when combined, improve the overall security posture of a service. What you’ll see across this post is a collection of recommendations which all help contribute to a more robust solution by virtue of complimenting one and other. That may mean that individual recommendations such as dropping complexity requirements look odd, but when you consider the way humans tended to deal with that (they’d just choose bad passwords with a combination of character types) alongside guidance such as blocking previously breached passwords, things start to make a lot more sense.
Now there’s just one more thing: as good as all this guidance is, practically implementing it can be somewhat trickier.
“How to defend your website with ZIP bombs” has been making rounds on the Internet for the last few weeks. It’s both sad, that we have to resolve to such measures, and funny as to how tongue-in-cheek this approach is.
Whether you are going to implement it for your web host or not, it’s well worth reading, for a better understanding of what’s going on online, in places, that you are probably not looking at.
As someone who went through a whole pile of trying and error with Amazon AWS, I strongly recommend reading anything you can on the subject before you start moving your business to the cloud (not even necessarily Amazon, but any vendor), and while you have it running there. “The AWS spend of a SaaS side-business” is a good one in that category.
I’ve been called many a name in my days. But ‘Default Value’ is the first one for me. I’m not sure if that’s a good thing, or not so much.
As sent by the otherwise awesome people at Elastix. :)