Design Patterns

An anti-pattern is a common response to a recurring problem that is usually ineffective and risks being highly counterproductive ( wikipedia). 

Strategy :  This pattern allows selecting an algorithm/concrete implementation at runtime.  Decouples implementation/algorithm from the context/client.   Normally Strategy pattern is used in combination with Factory patten.

Initialization On Demand Holder : This pattern takes care of thread-safety issues in singleton.  In Singleton, unless we synchronize the part where you create the instance, there is still a chance that multiple instance might get created.   See the example code in Reference below

Builder: This pattern is used for complex objects creations.  This decouples the complex object creation process from the object representation.

Chain of Responsibility ( COR ) or Chain of Command:  This pattern allows breaking down a complex operation into a sequence of small steps, thus making  the code simpler in the process.

Template Method:  Java provides abstract methods for this purpose.  This pattern defines a method template which can be implemented later in various ways.

Observer : One to many ( subject ->observers).  Used for modeling Publish-Subscribe scenarios. So there is a scenario where change in state of one object needs to be notified to multiple objects, this pattern can be used.  This will help keeping the code clean.

Adapter : When you need to use objects of  one interface and fit it into some other interface, this pattern can be used. Very good example is the phone adaptors for various types of  outlets.  Adaptor pattern allows two incompatible interfaces to work together.

State : This patten encapsulates various states of an entity and how it transitions from one state to another.

Reference : http://www.thedevpiece.com/design-patterns-that-every-developer-should-know/

Comments

Post a Comment

Popular posts from this blog

SQL

Joins - Not always very obvious ( Following example uses Hive ). create table x_temp ( name string, p_date int  ) insert into x_temp(name,p_date) values ('x1',20181025),('x2', 20181026), ('x3',20181027) create table y_temp ( name string, s_date int  ) insert into y_temp(name,s_date) values ('x1',20181025),('x2', 20181026), ('x3',20181027) create table z_temp ( name string, p_date int, s_date int ) insert into z_temp(name,p_date,s_date) values ('z1','20181025','20181025') select x.*, y.* from x_temp x, y_temp y, z_temp z  where x.p_date != z.p_date and  y.s_date != z.s_date) generates 4 records... x.name,x.p_date,y.name,y.s_date x2, 20181026, x2, 20181026 x3, 20181027, x2, 20181026 x2, 20181026, x3, 20181027 x3, 20181027, x3, 20181027 select x.*, y.* from x_temp x, y_temp y, z_temp z  where x.p_date != z.p_date or  y.s_date != z.s_date) generates 8 records x.name,x.p_date,y.
Read more

Analytics

Types of Analytics ( Notes from AWS Course )  Descriptive - What happened ?  hindsight  Diagnostic - Why did it  happen?  hindsight & insight  Predictive  - What will happen ? insight & foresight  Prescriptive - What should I do ? foresight  Cognitive & AI  - What are recommended actions ? foresight & hypothesis input  Popular BI Tools:  https://www.cio.com/article/3284415/10-bi-tools-for-data-visualization.html
Read more

HIVE

1. When doing multi table joins, except the last ( right most ) table, other tables are buffered in the reducers. So to have less memory footprint on reducers, largest tables should be the last one as it is not buffered but streamed to reducers.   For Impala , it is different. 2.  You can filter the unwanted records within the join itself. SELECT  a.*,   b. * FROM a LEFT OUTER JOIN b ON ( a.key=b.key  AND  b.name= 'Tim'   AND a .name= 'Kim' ) 3. Joins are left associative. So execution happens from left to right and the result of joins is  fed into next join operation. 4. To find the value of variable     set hive.execution.engine 5. To find values of all variables set  6. If you want to pass different hive configuration settings in hive shell, you can use --hiveconf. For example hive --hiveconf hivi.optimize.sort.dynamic.partition=true --hiveconf hive.exec.dynamic.partition.mode=nonstrict 7.  In case you accidentally drop the p
Read more