Scope ruby gem to a single class

I came across a useful trick of explicitly requiring ruby gems in each classes. In the Gemfile, set the gem require to false. Then you will have to explicitly require that gem in each class.

I am using it to encapsulate interaction with a 3rd party gems through an interface class. All calls made to the 3rd party service through this gem has to be through the interface class.

Example: https://stackoverflow.com/questions/18267849/require-a-gem-only-in-the-context-of-a-single-class-in-ruby

Interface Class with 3rd party gem

I finished creating an interface class to interact with a 3rd party gem. It is only used by a single class for now; however, establishing a good pattern early on is critical. Having a single class that interacts with the 3rd party gem allows me to create an integration tests that actually make network calls. Since it makes network calls to an external service, the integration spec will only run if you manually specify it on the command line. I do not include this as part of the continuous integration tests as I do not want to overload the external service. It is useful when developing as I can invoke an automated integration test after completing a feature. Right now, I have to run the commands and test it manually anyways; this integration tests automates it.
One issue I noticed is proper encapsulation is hard. That means I want ALL interaction with a 3rd party gem to go through this interface class but it is hard to encapsulate that fully. For example, the interface makes a request to an external service and return that as an object. Now, the class using the interface has a handle on that object and may invoke method calls or modify it. I need to freeze the returned object so you cannot invoke any methods or modify it.
A 3rd party integration spec is useful as it allows you to run a suite of tests when you finish with a feature.
Proper encapsulation of the interface class is difficult.

Big Data Tools Cheat Sheet

Datamania has a good technology landscape cheat sheet. Attached below is the cheat sheet.

Big-Data-Technology-Landscape-CheatSheet
Big-Data-Technology-Landscape-CheatSheet

What surprised me is that Looker is not on here. “Looker is a business intelligence software and big data analytics platform that helps you explore, analyze and share real-time business analytics easily.”

Also, ELT is also not represented in the graph. ELT stands for Extract, Load, Transform. Instead of having a data engineering team extract the data, transform it and load it into a data warehouse, the team extracts and loads the raw data into a data warehouse. Then, analytics tool such as Looker can transform the data on the fly and analyze it straight from the data warehouse. I deal with complex data transformations so I am most curious to hear how Looker or other tools can handle complex transformations.

I hear a lot of ELT and how ETL is dead. However, I did a google trend comparison between ETL and ELT and they both seem to have been stable for the past five years.

Finally, with so many tools and terminologies available, it is crucial to know when to use what. Factors include the data size, the skills, security, infrastructure, etc. There is so many exciting developments in this field!