Ruby AWS Lambdas And The DRY Principle Is Misunderstood

button-icon-arrow-right
button-icon-arrow-left

button-icon-arrow-leftBack

Event

Ruby AWS Lambdas and The DRY Principle Is Misunderstood

11 June 2019

New York

Added 30-Oct-2019

Lets Make a Ruby Microservice via AWS Lambda

This past November AWS added a Ruby 2.5 environment for the lambda platform and is now on its 3rd version of its Ruby SDK that came out in 2011. We will be going through the steps of deploying a Ruby Microservice on AWS.

The items to be covered:

General microservice architecture.
How to observe/monitor events that can set to trigger our Ruby function.
Where do the logs go?
Continuous Integration & Continuous Development Strategies for AWS Lambda.
How to communicate with other services?
Security groups and secure users.
Testing our lambda function.

Michael Garrigan

The DRY Principle Is Misunderstood

The Don’t Repeat Yourself Principle has swept the world, it is often the first thing new engineers are taught. It has probably affected your current code base in a big way. However, despite your code being “DRY”, your code is hard to change. The same files have to be changed over and over for seemingly unrelated reasons, and code brittleness due to tight coupling abound. You might ask yourself, “Why is this happening?”

In this talk I will teach listeners that the DRY Principle is actually about eliminating duplicate representations of ideas not duplicate code. Duplicate code is often misidentified as part of this principle, and attempts to clean it up are made. The end result is lots of divergent change (one place changes for many reasons), yielding tons of pain for the development team, and eventually a clamor for a complete rewrite of the system.

Top