Author: Jashan Goyal

ScalaGeek-Why Reactive Architecture?

Reading Time: 5 minutes In my previous blog. I discussed some In-build functionalities of ScalaGeek that makes it unique and flexible. Now In this blog, I will discuss the architecture and the tech stack that is used in ScalaGeek. Technology Stack In the ScalaGeek we have used five primary technologies for Back-end and two are used for front-end:1. Scala2. Akka3. Kafka4. Real-time database5. Firestore6. Angular 87. IonicNow I will Continue Reading

Scalageek- What makes it Unique

Reading Time: 4 minutes In my previous blog, I talked about some features of ScalaGeek. To achieve those feature a lot of has been done that I will cover in coming blogs. In this blog, I will talk about some in-build features of ScalaGeek that makes it flexible.  MetaData  This is the complete metaData of ScalaGeek. This is in the form of JSON. Basically, it is the structure of Continue Reading

ScalaGeek: Are you ready for the Challenge?

Reading Time: 4 minutes ScalaGeek is an application which promotes Scala concepts with a twist of gaming. It has been published with minimum features or challenges for the users, however, there will be more challenges added later on. The game is divided into Levels and stages. Every stage will have actions which the user need to perform. Once all the actions have been performed on the basis of time taken for it. Although one Continue Reading

Take a deep dive into Kafka – Producer API

Reading Time: 4 minutes I am going to start a series of blogs on Kafka API. This blog is a part of the series. In the series of blogs In this blog, we are going to learn about Producer-API. If you are new to Kafka then I will recommend you to first get some basic idea about Kafka Quickstart from kafka-quickstart . There are many reasons an application might Continue Reading

Executor and Execution Context objects in Scala

Reading Time: 3 minutes You have come here that means you know about Threads and concurrency. If you have doubts regarding this then you can read the blog on concurrency. As Thread and Runnable have been there for long as the very first generation of concurrent execution approaches in Scala. Creating a new Thread takes less computational time compared to creating a new JVM process. we cannot afford to Continue Reading