Posted on

Awesome AWS go api sdk

So I took on a task do some AWS RDS work updating instances and found the examples in the api sdk really useful. I also found the benefit of adding a go function and just compiling and deploying and testing was awesome. One concern was what if I wanted to create some common code and create two binaries to do different types of work, like a server and client binary but in my case two different utilities that would use common AWS api functions.  I guess this can be done with folders, but still working on learning golang and but I’m liking it.

The other benefit (if you look at it this way) is locking down development to locally, in the past I could just vim a python file on the server to change the script, this force me to develop and compile locally and have a single source. This way I don’t lose changes I made directly on the server because it might not be in source control since I was hacking on the server.

ref link to the go sdk api
https://docs.aws.amazon.com/sdk-for-go/api/

Posted on

gonorthwest.io

Attended gonorthwest.io where I had the idea for gomonger.io in between sessions.   The talks I enjoyed the most where the following:

Jayapriya Surendran Probabilistic Data Structures Using Go, I liked the Bloom filter, Count–min sketch and HyperLogLog.  I could see these a good tool for malicious traffic.  I could also see these data structures as a good tool for caching.

Sam Kreter’s – Introduction to Modern Data Science with Go, it was interesting to see how data could be versioned with a git like tool to rolled back data changes and the pipeline auto update based on roll back of the data.

David Crawshaw’s – SQLite and Go was a fun talk because it made you think about tools and keeping things simple and working with tools you know.  I liked the thought behind the talk because we are limited when working on our own to what resources we can have access to, scale could just be throwing more hardware at the problem or creating more machines that could agritate the data.