Spark Structured Streaming (Apache Spark 2.2+)
Welcome to Spark Structured Streaming gitbook!
I’m Jacek Laskowski, an independent consultant, software engineer and trainer focusing exclusively on Apache Spark and Apache Kafka (with Scala and sbt, and as much as necessary with Apache Mesos, Hadoop YARN, and DC/OS). I lead the Warsaw Scala Enthusiasts and Warsaw Spark meetups in Warsaw, Poland.
Contact me at firstname.lastname@example.org or @jaceklaskowski to discuss Apache Spark or Apache Kafka opportunities, e.g. customized trainings, workshops, mentoring, code reviews, performance tuning or application development services.
If you like the gitbook you should seriously consider participating in my own, very hands-on, in-depth Apache Spark Workshops and Webinars and in particular brand new and shiny Spark Structured Streaming (Apache Spark 2.2) Workshop.
If you’d like to participate in Spark Structured Streaming (Apache Spark 2.2) Workshop go to the tweet and like it. That’s how I figure the interest in the workshop.
Spark Structured Streaming gitbook serves as the ultimate place of mine to collect all the nuts and bolts of using Spark Structured Streaming in the most effective way. The notes aim to help me designing and developing better products with Apache Spark. It is also a viable proof of my current understanding of Apache Spark. I do eventually want to reach the highest level of mastery in Apache Spark (as do you!)
The collection of notes serves as the study material for my trainings, workshops, videos and courses about Apache Spark. Follow me on twitter @jaceklaskowski for up to date news and to learn about the upcoming events about Apache Spark.
|I’m also writing Mastering Apache Spark 2 (Spark 2.2+) and Mastering Apache Kafka (Kafka 0.11.0.0+).|
Expect text and code snippets from Spark’s mailing lists, the official documentation of Apache Spark, StackOverflow, blog posts, books from O’Reilly (and other publishers), press releases, conferences, YouTube or Vimeo videos, Quora, the source code of Apache Spark, etc. Attribution follows whenever possible.