| Setup Database | |
| create database [db-name]; | |
| revoke all on schema public from public; | |
| create schema [schema-name]; | |
| create table [schema-name].[table-name]( | |
| ... | |
| ) | |
| /* Purpose of ShardIndexRecord is to store/correlate connectionString for a particular shardId. | |
| This allows one to find database server connection specific to a given shard */ | |
| case class ShardIndexRecord(shardId: String, connectionString: String, status: Boolean, createdDate: Long) |
| /* Purpose of UserShardRecord is to store/correlate shardId for a particular userId */ | |
| case class UserShardRecord(userId: String, shardId: String) |
| /* Purpose of DomainShardRecord is to store/correlate Domain Partition for a particular userId. | |
| To surpass the max column width limitation with RDBMs, you can implement additional case classes for other Entities. */ | |
| case class DomainShardRecord(userId: String, password: String, userName: String) |
| /* Consider the following table...*/ | |
| create table data ( | |
| id integer primary key, | |
| status char(1) not null, | |
| data1 varchar2(10) not null, | |
| data2 varchar2(10) not null); | |
| /* You can split via most frequent vs rarely used table columns */ | |
| create table data_main ( |
| #!/usr/bin/env ruby | |
| require 'gli' | |
| include GLI::App | |
| program_desc 'Implementing Command Suite Application for Git' | |
| version Git::VERSION | |
| subcommand_option_handling :normal | |
| arguments :strict |
Since starting to teach Computer Science at Pasadena Community College, I've often wondered what advice I would give to my previous self 15 years ago when I first embarked on this journey to become a software engineer.
####Best career advice I ever got
####Be a Craftsman
| class InterviewQuestions | |
| def initialize(count=0) | |
| @count = 0 | |
| end | |
| def count_duplicates(arr) | |
| arr.sort! # your favorite sorting algo (n log n) | |
| arr.each_with_index {|index| | |
| if (index + 1 < arr.length) | |
| if (arr[index+1]==arr[index]) |
So I hear business is going well...customers are flocking to your site/app...people just can't get enough? Congratulations, this is a huge step most companies don't reach.
What now? Well, business analysts, modelers, engineers, customer support and marketing want to access an authoritative, consistent, timely access to your organization's data. Perhaps we can build some beautiful dashboards to visualize KPIs for executive management.
You're in need of a Data Warehouse? Maybe a Data Lake? Where do you start? What sort of considerations & alternatives should you think about.
Turns out there are a variety of things you must take into consideration depending on your requirements. A good place to start is to interview & establish a relationship with team leads to better understand their needs. As you're going through the discovery process, here's an algorithm of the types of things you'll need to consider in your discovery phase.
| configure the python2.7 environment: | |
| conda create -n py27 python=2.7 | |
| source activate py27 | |
| conda install notebook ipykernel | |
| ipython kernel install | |
| configure the python3.5 environment: |