Mark Canlas, Engineer – @markcanlasnyc: At Tapad, we love Scala. We write it, we bathe in it, and sometimes we sprinkle it on our breakfast cereal. We love it so much that we decided to pack our bits and journey west to the city of Philadelphia for the 2016 Northeast Scala Symposium – the original Scala community-based conference.
NE Scala is a two-day Scala conference in the Northeast of the US. It’s a great opportunity to reconnect with former colleagues and rub shoulders with luminaries in the Scala community. Is that my favorite library author at the watercooler? Why yes it is! And shout out Tapad engineering crew who came out in full force. Couldn’t make it to the 6th annual event? No worries, check out the highlights below.
NE Scala Day One Takeaways
The first day of NE Scala was a single track series of presentations. From Runar O Bjarnason, we were introduced to Scalaz’s Task and Stream libraries which let you describe your data processing pipeline without actually running it. With more fine-grained control, you can choose when tasks get run or how they compose with other tasks. From Brian Clapper, we learned about the evolution of Apache Spark’s API and the importance of type safety and declarative APIs. Throughout the day we discovered different ways that Scala could improve our workflows, even at build and compilation time!
Though the topics were varied, a pattern was clear: Scala engineers process a lot of data. Some from a database, some from flat files, but most often in a real-time, distributed environment. To tame that complexity, we need a scalable architecture. Good news for Scala programmers – the functional patterns we use every day are very much alive and well at all layers of the stack, including real-time processing. Have you met our friends map, flatMap, and filter?
NE Scala Day Two Takeaways
On the second day, NE Scala hosted an “unconference.” Given a spreadsheet of rooms and time slots, the attendees self-organized a voluntary, multi-track conference day of their choosing. Tapad Engineering took advantage of the opportunity to present an introduction on transducers and how they mirror functional patterns mentioned in the day prior.
Bottom line? Scala, I choose you!
Tasks, streams, transducers…Is there anything that the Scala beast can’t handle? Based on our experience at NE Scala, maybe not!Scala is a bit of a chameleon, you see. It can adapt to your environment, being as object-oriented or as functional as you see fit. But at NE Scala, we’re seeing functional patterns picking up steam as reliable ways to tackle problems at scale and navigate the complexity of real-time systems.
Big thanks to Tapad’s own Oleksii Iepishkin – and the other volunteers – for organizing another successful NE Scala!
If you’re up for the Scala challenge and you’d like to join a team that works smart, plays hard and drives real tech change then check out Tapad’s careers page or connect with us at firstname.lastname@example.org.