Not necessarily for Kafka, but you can definitely google “Java vs. Scala” and find a variety of reasons . I did a study for a client and ultimately here are the major reasons I found :
1. Functional programming language which leads itself to stateless systems 2. Better / easier to use stream processing syntax (then at that time in Java 8) 3. REPL available to quickly test functionality interactively. 4. Case classes which can be inferred with or without strongly typed cases. 5. Abilty to quickly create DSLs that seem natural to developers 6. Awesome partial function syntax 7. My personal favorite — as I was using parboiled2 to build a parser — libraries like shapeless Best -- Rahul Singh rahul.si...@anant.us Anant Corporation On Jul 23, 2018, 8:40 AM -0400, M. Manna <manme...@gmail.com>, wrote: > Hello, > > Is anyone aware of any links or website where I can find information/case > study etc. to why Scala was the best choice for kafka design? I hope this > is not too much of a "Naive" question since I have had a very humble > introduction to Scala. > > I understand that Scala is considered where distributed/scalable systems > need to be designed. Also, in some cases it reduces multiple complex > statements to be formed using a single complex statements i.e. reduce > incremental verbosity. > > So, as a person who has background in Java, but relatively novice in Scala, > I wanted to understand whether a study document exists to document the > choice? > > Regards,
