Over a million developers have joined DZone.

Microservices and Fast Data: Industry and Architecture Trends

DZone's Guide to

Microservices and Fast Data: Industry and Architecture Trends

In this video, Dean Wampler of Lightbend and Matt Aslett of 451 Research discuss the business justification for shifting to microservices software architecture.

· Microservices Zone ·
Free Resource

Download the  How to Build (and Scale) with Microservices eBook and learn how microservices are rapidly emerging as the architecture of choice. Brought to you in partnership with AppDynamics

As the end goal of streaming and Fast Data systems include a promise of accelerated access to information that can lead to new opportunities for innovation and competitive advantage, it's easy to forget that they aren't just "faster" versions of Big Data systems.

Under the hood, these Fast Data systems have forced system architecture changes to meet new demands for reliability and dynamic scalability, more like the sorts of microservices architectures and design patterns we see successfully utilized by many of our customers today.

In this fireside chat style presentation, Dean Wampler of Lightbend and Matt Aslett of 451 Research will:

  • Discuss the business justification for transitioning from batch-oriented big data to stream-oriented fast data.
  • Explain the changes that streaming architectures require to meet their higher demands for reliability, resiliency, dynamic scalability, etc.
  • Discuss how some of these requirements can be met by leveraging what organizations already know about microservice architectures.

You can check out the SlideShare presentation here.

As always, Lightbend is here to make your streaming and Fast Data journey successful.

Learn how to track microservices deployed in elastic infrastructure such as containers or cloud where nodes scale up and down very rapidly.

microservices ,streaming data ,software architecture

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}