A very completed introduction about the internal of Apache Spark. Highly recommended!
It is a full day workshop (almost 6 hour long video), so you can use following checkpoint to start with the section you are interested in. The section I find most interesting is to reveal how they won 2014 100TB sorting challenge, watch from 4:49:00 Next Gen Shuffle.
Youtube : Advanced Apache Spark Training - Sameer Farooqui (Databricks)
Slides : Devops Advanced Class
This is the short research I did back to web development course in 2016. It will give you a brief overview how online advertiser track the user and few tips about how can you protect yourself from tracking. Hope you enjoy!
A discussion for one type of dynamic programming problems - MinMax Game: Predict the Winner.
Given an array of scores that are non-negative integers. Player 1 picks one of the numbers from either end of the array followed by the player 2 and then player 1 and so on. Each time a player picks a number, that number will not be available for the next player. This continues until all the scores have been chosen. The player with the maximum score wins.
Given an array of scores, predict whether player 1 is the winner. You can assume each player plays to maximize his score.
I am reading a book recently called Re-Engineering Legacy Software from Chris Birchall , and find many interesting insights.
The chapter 4 to 6 discussed different types of re-engineering from small scope to large : Refactoring, Re-Architecting and The Big Rewrite. The author also discuss some real examples.
For example, in chapter 5, he discussed how to break a monolithic application (a log management app) into modules, by defining interfaces and iterative development to reduce risk.
He also discuss an example to re-architect a huge monolithic legacy ecommerce web app to Service-Oriented Architecture and what the challenges will it be.
4/5 Star, Recommended.
Feel the same pain with shared database for development and I am looking for some potential solutions. Source control for Database is definetly helpful and Database Continuous Integration also seems promising. But to what extend and how to keep consistency if you used seprate database are still not that clear.
Blog reading:
Top 4 Reasons Why a Shared Development Database is Evil. by Ben Day
The unnecessary evil of the shared development database by Troy Hunt
Database Continuous Integration 101 in Atlanssian Blog
Stackoverflow discussion :
Should we have separate database instance for each developer?