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

Turning Python Scripts into Working Web Apps Quickly with Streamlit

 I just realized that I am using Streamlit since almost one year now, posted about in Twitter or LinkedIn several times, but never wrote a blog post about it before. Communication in Data Science and Machine Learning is the key. Being able to showcase work in progress and share results with the business makes the difference. Verbal and non-verbal communication skills are important. Having some tool that could support you in this kind of conversation with a mixed audience that couldn't have a technical background or would like to hear in terms of results and business value would be of great help. I found that Streamlit fits well this scenario. Streamlit is an Open Source (Apache License 2.0) Python framework that turns data or ML scripts into shareable web apps in minutes (no kidding). Python only: no front‑end experience required. To start with Streamlit, just install it through pip (it is available in Anaconda too): pip install streamlit and you are ready to execute the working de...

jOOQ: code generation in Eclipse

jOOQ allows code generation from a database schema through ANT tasks, Maven and shell command tools. But if you're working with Eclipse it's easier to create a new Run Configuration to perform this operation. First of all you have to write the usual XML configuration file for the code generation starting from the database: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <configuration xmlns="http://www.jooq.org/xsd/jooq-codegen-2.0.4.xsd">   <jdbc>     <driver>oracle.jdbc.driver.OracleDriver</driver>     <url>jdbc:oracle:thin:@dbhost:1700:DBSID</url>     <user>DB_FTRS</user>     <password>password</password>   </jdbc>   <generator>     <name>org.jooq.util.DefaultGenerator</name>     <database>       <name>org.jooq.util.oracle.OracleDatabase</name>     ...

Load testing MongoDB using JMeter

Apache JMeter ( http://jmeter.apache.org/ ) added support for MongoDB since its 2.10 release. In this post I am referring to the latest JMeter release (2.13). A preliminary JMeter setup is needed before starting your first test plan for MongoDB. It uses Groovy as scripting reference language, so Groovy needs to be set up for our favorite load testing tool. Follow these steps to complete the set up: Download Groovy from the official website ( http://www.groovy-lang.org/download.html ). In this post I am referring to the Groovy release 2.4.4, but using later versions is fine. Copy the groovy-all-2.4.4.jar to the $JMETER_HOME/lib folder. Restart JMeter if it was running while adding the Groovy JAR file. Now you can start creating a test plan for MongoDB load testing. From the UI select the MongoDB template ( File -> Templates... ). The new test plan has a MongoDB Source Config element. Here you have to setup the connection details for the database to be tested: The Threa...