yogsototh/dimisit
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

typos

Browse source
This commit is contained in:
Yann Esposito 2015-11-07 19:48:05 +01:00
parent 2d379d777f
commit c7d0e6f4c0
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
articles/Two_years_with_clojure.md
View file

@ -177,7 +177,7 @@ Further more, dealing with realtime processing at that time was all about java e
There was Storm, Kafka, Zookeeper, etc...
So using a language which could use all the java libraries seemed very important to us.
With that in mind we simply had t choose between Scala and Clojure.
With that in mind we simply had to choose between Scala and Clojure.
Looking at scala, it was clear that it will be to Java what C++ is to C.
While Clojure being a descendant from the LISP family, we found that everything was simple, easier to read and understand.
Clojure community sounded great.
@ -185,7 +185,7 @@ Clojure community sounded great.
Furthermore Storm was first written in Clojure.
So go go go!
t was during summer that most technical choices were made.
It was during summer that most technical choices were made.
1. We wanted to deploy using Mesos / Marathon,
2. Use Kafka and Storm,
@ -199,7 +199,7 @@ Each choice was balanced.
In the end some of those choices were changed throught practice.
For instance, we discarded Storm.
The power of core.async was more than enough efficiently exploit all the juice of our machines,
The power of `core.async` was more than enough efficiently exploit all the juice of our machines,
Storm added some unnecessary latency and complexity.
Today you can see a result here: