Skip to main content

DataWorks Summit 2018, Berlin Edition: come to attend my talk.

AI, Machine Learning and Deep Learning are getting an hype nowadays even if most part of the algorithms and models at their core are around since long time:

1805 Least Squares
1812 Bayes' Theorem
1913 Markov Chains
1950 Turing's Learning Machine
1957 Perceptron
1967 Nearest Neighbor
1970 Automatic Differentiation
1972 TF-IDF
1980 Neocognitron
1981 Explanation Based Learning
1982 Recurrent Neural Network
1970 Back Propagation
1989 Reinforcement Learning
1995 Random Forest Algorithm
1995 Support Vector Machines
1997 LSTM

So what are the reasons that speed up and accelerated the implementation and made possible today for the theory to become reality?
There are several factors:
 - Cheaper computation: in the past hardware was a constraining factor for AI/ML/DL. Late advance in hardware (coupled with improved tools and software
frameworks) and new computational models (in particular around GPUs) have accelerated AI/ML/DL adoption.
 - Cheaper storage: the increased number of available data means more space needed for storage. Advance in hardware, cost reduction and improved performance made possible the implementation of new storage systems without the typical limitations of relational databases.
 - More advanced algorithms: less expensive compute and storage enable development and training of more advanced algorithms. As a result, DL is nowsolving specific problems like image classification or fraud detection with astonishing accuracy (and more sophisticated algorithms will continue to improve the state of the art).
 - More and bigger investments: investment in AI is no longer confined to universities or research institutes, but is done from many other entities such as tech giants, governments, startups and large enterprises across almost every industry sector.
 - Bigger data availability: AI/ML/DL need a huge amount of data to learn. The digital transformation of society is providing tons of raw material to fuel their advances. Big data coming from diverse sources such as IoT sensors, social and mobile computing, healthcare and many more new applications can be used to train models.
But often just getting data from any possible data source, in particular from the edge, requires moving mountains. Please attend my talk at the DataWorks Summit in Berlin on April 18th if you want to learn how to make edge data ingestion and analytics easier using a single tool, StreamSets Data Collector Edge, which is an ultralight, platform independent and small-footprint Open Source solution written in Go for streaming data from resource-constrained sensors and personal devices (like medical equipment or smartphones) to Apache Kafka, HDFS, Elastic Search and many other destinations.

Comments

Popular posts from this blog

Streamsets Data Collector log shipping and analysis using ElasticSearch, Kibana and... the Streamsets Data Collector

One common use case scenario for the Streamsets Data Collector (SDC) is the log shipping to some system, like ElasticSearch, for real-time analysis. To build a pipeline for this particular purpose in SDC is really simple and fast and doesn't require coding at all. For this quick tutorial I will use the SDC logs as example. The log data will be shipped to Elasticsearch and then visualized through a Kibana dashboard. Basic knowledge of SDC, Elasticsearch and Kibana is required for a better understanding of this post. These are the releases I am referring to for each system involved in this tutorial: JDK 8 Streamsets Data Collector 1.4.0 ElasticSearch 2.3.3 Kibana 4.5.1 Elasticsearch and Kibana installation You should have your Elasticsearch cluster installed and configured and a Kibana instance pointing to that cluster in order to go on with this tutorial. Please refer to the official documentation for these two products in order to complete their installation (if you do

Exporting InfluxDB data to a CVS file

Sometimes you would need to export a sample of the data from an InfluxDB table to a CSV file (for example to allow a data scientist to do some offline analysis using a tool like Jupyter, Zeppelin or Spark Notebook). It is possible to perform this operation through the influx command line client. This is the general syntax: sudo /usr/bin/influx -database '<database_name>' -host '<hostname>' -username '<username>'  -password '<password>' -execute 'select_statement' -format '<format>' > <file_path>/<file_name>.csv where the format could be csv , json or column . Example: sudo /usr/bin/influx -database 'telegraf' -host 'localhost' -username 'admin'  -password '123456789' -execute 'select * from mem' -format 'csv' > /home/googlielmo/influxdb-export/mem-export.csv

Using Rapids cuDF in a Colab notebook

During last Spark+AI Summit Europe 2019 I had a chance to attend a talk from Miguel Martinez  who was presenting Rapids , the new Open Source framework from NVIDIA for GPU accelerated end-to-end Data Science and Analytics. Fig. 1 - Overview of the Rapids eco-system Rapids is a suite of Open Source libraries: cuDF cuML cuGraph cuXFilter I enjoied the presentation and liked the idea of this initiative, so I wanted to start playing with the Rapids libraries in Python on Colab , starting from cuDF, but the first attempt came with an issue that I eventually solved. So in this post I am going to share how I fixed it, with the hope it would be useful to someone else running into the same blocker. I am assuming here you are already familiar with Google Colab. I am using Python 3.x as Python 2 isn't supported by Rapids. Once you have created a new notebook in Colab, you need to check if the runtime for it is set to use Python 3 and uses a GPU as hardware accelerator. You