Rename Enumerable to Stream

[sam-goodwin]

Fixes #25

• Rename Enumerable to Stream
• Move services into their own namespace:
  • Glue
  • DynamoDB
  • SNS
  • SQS
  • Kinesis
  • S3
  • Lambda
• Update Examples
• Update README

[sam-goodwin]

Any thoughts on toKinesis vs toKinesisStream? I.e. should I include the resource type as a suffix?

• toSQS or toSQSQueue
• toSNS or toSNSTopic
• toKinesis or toKinesisStream
• toS3DeliveryStream or toFirehose
• toGlue or toGlueTable (note: it's already toGlueTable, so we need to change it for consistency reasons)

[pocesar]

it makes sense just to be a little more verbose to where it's going to, LGTM.

to{Service}{Resource} is a good convention, makes it easier to reason. thinking about those services such as SageMaker that have a lot of underlying resources (although couldn't visualize a toSageMaker{Resource} from the top of my head)

[sam-goodwin]

Yeah, I think this is a good convention. Updated to reflect that.

I'm not that happy with toS3DeliveryStream. Could have gone with toFirehoseDeliveryStream, but how to differentiate between destinations (Redshift, ElasticSearch, Splunk, etc.) Created #31 to follow up.

[sam-goodwin]

While we're namespacing all the things, should Function => Lambda.Function?

[sam-goodwin]

This was a neat trick!

[pocesar]

While we're namespacing all the things, should Function => Lambda.Function?

yeah, Function is a global constructor for function, would be good to go ahead and namespace that as well, and make it obvious it's a Lambda Function (and even sounds cooler haha)