Do you think your code is Perfect? Well, Think again.

Anmol SarnaJune 26, 2018June 26, 2018Java, Scala, software, TestingBest Practices, Clean code, java, programming, scala, Unit Testing

“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” – Martin Fowler “I can code.” I always say to myself. But do others think the same? Is my code good enough for people to understand? Do other people think “Damn I wish I could write such code.?” – that’s the main question I always had in Continue Reading

SOLID Principles: Basic building block of the software system

Ayush TiwariMay 24, 2018August 9, 2018ArchitectureBest Practices, Clean code, solid principles

“Good software system begins with clean code” and by “clean code”, I mean it is code that is easy to understand and easy to change. This is the point where there is a need to know about SOLID Principles which helps us in writing the clean code as the code is like humour. “When you have to explain it, it’s bad.” The SOLID PRINCIPLES tell Continue Reading

Is Shifting to Domain Driven Design worth your Efforts?

Anmol SarnaMay 1, 2018May 1, 2018Java, Microservices, ScalaBest Practices, DDD approach, Design, domain, good design, Microservice architecture design, scala

In our earlier blog, we explored a bit about Microservices. But let’s take a step back and look into how microservices can be effectively designed. Yes, you guessed it right. We will be talking about the Domain Driven Design or what we call the DDD approach. But before jumping into the concepts of Domain Driven Design, let’s understand 2 basic terminologies : Domain: A domain is the sphere Continue Reading

Scala Trait and Mixin – Points to Remember

Harmeet Singh(Taara)March 26, 2017August 13, 2018Functional Programming, ScalaBest Practices, desgins, mixin, mixing, opensource, points, remember, scala, scalamixin, scalamixing, ScalaTraits, technology, tips, Traits

Scala Trait and Mixin – Points to Remember Trait can be viewed not only as interfaces in other languages, but also as classes with only parameterless constructor. Whenever there is some code in trait, the trait is called mixin. trait Alarm { def trigger(): String } In scala trait, If we create simple class and pass parameter in constructor, without any val or var, it Continue Reading

Partition-Aware Data Loading in Spark SQL

Himanshu GuptaFebruary 9, 2017July 20, 2018Scala, SparkApache Spark, Best Practices, Big Data, Spark SQL

Data loading, in Spark SQL, means loading data in memory/cache of Spark worker nodes. For which we use to write following code: val connectionProperties = new Properties() connectionProperties.put(“user”, “username”) connectionProperties.put(“password”, “password”) val jdbcDF = spark.read .jdbc(“jdbc:postgresql:dbserver”, “schema.table”, connectionProperties) In here we are using jdbc function of DataFrameReader API of Spark SQL to load the data from table into Spark Executor’s memory, no matter how many rows are Continue Reading

And you thought you were doing Microservices

Vikas HazratiMay 8, 2016May 8, 2016Microservices, ScalaBest Practices

If you have been in the software industry for some time you would have heard things like. Yes we do Scrum but …we do not have timeboxed sprints. Yes, we write automated user acceptance tests but … as a part of the Sprint planning we decide whether we would write automated test for a story or do ad-hoc manual testing. Oh, and our test coverage Continue Reading

Expression Oriented Programming

Vikas HazratiMarch 31, 2016ScalaBest Practices

In a conversation with one of the lead architects of a large publishing company, we were discussing around the coding standards and suddenly the term EOP brought the discussion to a standstill. Ok, just for a few seconds. Once I explained it, it was like “Ah, is that it ?” If you are doing Scala, you can be assured that you are good with it Continue Reading

Fundamentals of eXtreme Programming

Himanshu GuptaJanuary 11, 2016August 14, 2018AgileAgile, Best Practices, knolx

The term Extreme Programming (XP) was coined by Kent Beck, in late 1990s. The purpose behind inventing XP was to find a way to deliver high quality software, developed by small teams, and to keep up with the changing requirements of customer. Although, XP is more than a decade old now, it is still being practiced by a lot of developers around the world. The following slide deck and Continue Reading

Best Practices