Data Relativity: What they never told you about SOA & how Stream Processing help

Hey, remember when Service Oriented Architecture was the next best
thing, and not the worst thing that ever happened to you?

Like all revolutions in computing, this idea of separating software
components into independently deployable components communicating over network protocols has proven to be a double edged sword. On the leading edge of this paradigm shift, it seemed like SOA/Microservices would be the thing to solve our biggest enterprise architecture problems. But now, a lot of eager adopters are discovering that, as many big, fundamental problems as it solves, it also creates a different set of big, fundamental problems.

The thing that was hard to see up front is that when you start deploying independent services, you turn your company into a distributed system. Which comes with all the same fun, headache-inducing challenges that face the developers of Kafka, Cassandra, Elasticsearch, etc.

The good news is that, just as this challenge is really coming to the fore, recent developments in Streaming are becoming available, which can help you make an end-run around your next existential crisis. Come out and join us as we discuss the big practical and philosophical problems you're facing now and will face in the near future, and what you can do to design around them.

John Roesler is a software engineer at Confluent and a contributor to
Apache Kafka, primarily to Kafka Streams. Before that, he spent eight
years at Bazaarvoice, on a team designing and building a large-scale
streaming database and a high-throughput declarative Stream Processing
engine.