1. 4

Just a little utility service for dealing with ARNs

  1.  

  2. 2

    If I’m understanding this correctly, it’s a utility to build ARNs from components or break ARNs into their constituent components. Out of curiosity, why is this a service and not a library? Is it just to make it (more) accessible to other languages?

    1. 2

      Correct, that’s what it does. It’s really just the online version of what is available in the AWS SDK. I like to have small services that I can invoke and compose on the CLI, only having curl as the dependency. Same way that I query my public IP using curl ifconfig.co ;)

      1. 3

        A question I have in this context is: Is the granularity and abstraction you gain worth the overhead in both complexity and performance?

        1. 1

          Worth it? Not sure. What would be the complexity?

          1. 2

            Well, let’s compare and contrast.

            A library call has virtually no overhead. You’re running code on your machine. Full stop.

            Creating a microservice adds the following levels of indirection:

            • TCP/UDP connection from client to server
            • a protocol like HTTP
            • If you layer in https, that’s a whole other layer cake of protocols, TLS, yada yada.
            • payload un-picking / unpacking (Assuming you’re using something like JSON or XML)

            And that’s just off the top.

        2. 2

          Re-reading my responses to this, I have done exactly what I hate to see in other people’s posts. I allowed myself to go off half cocked based on my initial idea of “Why write a service for this when you can just call the SDK?” when there are clearly PLENTY of people who have many uses for this service.

          I can only say that I will try to exhibit the kind of open mindedness I’d like to see in others in my future reactions to posts here.