Re: Clojure is a good choice for Big Data? Which clojure/Hadoop work to use?

2019-07-04 Thread Thad Guidry
Christian writes really good tools. Sparkling is no exception. I have yet to use it in production myself however, since I haven't had the need to use Clojure directly to solve any "data aggregation" problems. Spark and other tools do that well enough, naturally. As far as using a

Re: Clojure is a good choice for Big Data? Which clojure/Hadoop work to use?

2019-07-04 Thread Chris Nuernberger
Thad, You approach seems very promising to me for a lot of jobs. Spark runs on top of many things. As far as a clojure layer on top, what do you think about sparkling ? On Thu, Jul 4, 2019 at 8:43 AM Thad Guidry wrote: > "Batch" - doing things in

Re: Clojure is a good choice for Big Data? Which clojure/Hadoop work to use?

2019-07-04 Thread orazio
probably as Thad says, for a farsighted choice the tool to use for batch processing is Apache Spark. But I'm worried about its learning curve and the time it takes. I don't have much time to develop my map reduce algorithems. I would like to use a consolidated and fairly used tool in

Re: Clojure is a good choice for Big Data? Which clojure/Hadoop work to use?

2019-07-04 Thread Thad Guidry
"Batch" - doing things in chunks "Processing" - THE WORLD :-) because it means so many different things to so many folks (including your boss) Without a doubt, you will love Apache Spark for your batch processing and writing Spark Programs to conquer any World you are building. Spend time to

Re: core.async: Unbound channels

2019-07-04 Thread Matching Socks
Ernesto, you may be interested in the informative response to this enhancement request, https://clojure.atlassian.net/browse/ASYNC-23, "Support channel buffers of unlimited size". Anyway, if you do not want to think very hard about buffer size, you can specify a size of 1. It does not limit

Re: core.async: Unbound channels

2019-07-04 Thread Ernesto Garcia
Thanks for your response, it is important to know. (Sorry for my lexical typo: *unbound**ed*. I didn't realize it derives from the verb *bound*, not *bind*!) My question on channel boundaries still holds though. Why the enforcement of boundaries *always*? On Wednesday, July 3, 2019 at 5:16:31

Re: Clojure is a good choice for Big Data? Which clojure/Hadoop work to use?

2019-07-04 Thread orazio
Hi @atdixon and Thad, thanks for your help. I provide more details about my project My big data layer is inspired by Lambda architecture. The pipeline include following layers and related tool choosed to address the issue: - *Nifi* for *data ingestion*, and publisinh data/message on kafka

Re: [ANN] Deeto - A Java dynamic proxy factory for interface-typed data transfer objects

2019-07-04 Thread henrik42
Yes! I agree. This is for people how want/must stay with Java for reasons. There are people in the Clojure community who work on Java-Clojure-integration and this is one of man ways to go. I just hope it is useful for someone. It could even be a door opener for Clojure and more people (like