ETE 2015

Philly ETE 2015 – Stuart Halloway – Enhancing Datalog for Datomic

Datalog has been a signature feature of Datomic since day one, and the 2015 releases of Datomic add additional expressiveness for hierarchical selection, disjunction, and negation. In this talk, we will cover the basics of Datomic Datalog, and then dive into the latest enhancements, both in the core language and in how Datalog fits into application code.

Philly ETE 2015 – Helena Edelson – Streaming Big Data with Spark, Spark Streaming, Kafka, Cassandra and Akka

This talk presents Apache Spark, Spark Streaming, Apache Kafka, Apache Cassandra and Akka as supporting Lambda architecture in the context of a fault tolerant, streaming big data pipeline. We will walk through the Fault Tolerance story with these technologies to build applications, and how to easily implement and integrate them in a Scala Akka application for real-time delivery of meaning at high velocity, in highly distributed and concurrent environments.

Philly ETE 2015 – Todd Montgomery – The Changing Face of Communications: IoT, REST, & Reactive

We are experiencing a profusion of interconnected devices. Architectures are undergoing radical changes to enable better scaling and resiliency. And at the heart of all of these are several new protocols that are changing the way services communicate. A lot of interest lies with WebSocket, HTTP/2, CoAP, MQTT, XMPP, etc. What can these protocols do? What can we learn from them? And where are things going? This session will explore these questions and more.

Philly ETE 2015 – Michael Toppa – Agile Contracts for Software Consultants

You’re ready to go with all the best Agile practices: you’ll develop incrementally and iteratively, you’ll have sprints and retrospectives, and you can’t wait to tell your clients about your velocity and show them your burndown charts. But all of your prospective clients are telling you they want firm quotes, and contracts with detailed specifications and delivery dates. How do you convince them a traditional contract is actually riskier than they think, and persuade them to instead sign an Agile (time and materials) contract?