Revitalizing Aging Architectures with Microservices

•

19 likes•7,858 views

When you need to react quickly to competitive threats, but your existing architecture is anything but nimble, what do you do? In this presentation, you will hear the story of how Walmart Canada revitalized its aging architecture with a microservices model built for speed and performance - that efficiently leveraged its JVM infrastructure - to achieve major e-commerce success in just 12 months: Conversions up 20% Mobile orders up 98% No downtime during Black Friday or Boxing Day This webinar is based off Kevin Webber’s highly successful Gartner session, Lessons Learned: Revitalizing Walmart's Aging Architecture For Web Scale, and will include added content.

Software

Revitalizing Aging Architectures with
Microservices
Kevin Webber (@kvnwbbr)
Enterprise Advocate

Typesafe
Reactive
Platform
» Play - RESTful API
framework
» Akka - Distributed
computing framework
» Spark - General purpose in-
memory compute engine
» ConductR, Monitoring, and
commercial features

Theworld by2020
» 4 billion connected people
» 25+ million apps
» 25+ billion embedded systems
» 40 zettabytes (40 trillion gigabytes)
» 5,200 GB of data for every person on Earth

The goal
» ~100% availability ("nine nines")

The goal
» ~100% availability ("nine nines")
» Consistent responsiveness under varying load
conditions

The goal
» ~100% availability ("nine nines")
» Consistent responsiveness under varying load
conditions
» Predictable spikes of trafﬁc, e.g, Black Friday
» Less predictable spikes of trafﬁc, e.g,
marketing campaign driving trafﬁc

Walmart's Business Uplift
» Conversions up 20%
» Mobile orders up 98%
» No downtime Black Friday or Boxing Day

Walmart's OperationalSavings
» Moved off expensive hardware
» On cheap virtual x86 servers
» 20% - 50% cost savings
» ~ 40% compute cycles

asynchronous, non-blocking, real-time, highly-
available, loosely coupled, scalable, fault-tolerant,
concurrent, reactive, event-driven, push instead of
pull, distributed, low latency, high throughput...

Reactive
A maturity model for modern
distributed systems.
» Responsive
» Resilient
» Elastic
» Message-driven

Why,What, How
Reactive (principles)
» responsive, resilient,
elastic, message-driven

Why,What, How
Reactive (principles)
» responsive, resilient,
elastic, message-driven
Microservices (strategy)
» bounded contexts (DDD),
event sourcing, CQRS,
eventual consistency

Clustered
microservices
» responsive to events, load,
failure, users
» embrace new concepts and
patterns
» cluster computing
» distribution of data
» new patterns like
circuit breakers

Microservices
Ecosystem
plus:
» service registry
» service discovery
» architecture visualization
» security

PlayAnatomy
Stateless
» Session is stored in the
browser cookie
Actions
» User-deﬁned functions that
run in a different context
than the request loop

Playatits core
» Familiar MVC paradigm
» Embraces ﬂows of data
» WebSockets, SSE
» Reactive Streams (experimental in Play 2.4)
» File uploads
» Integration with Akka
» Distribute work via messaging

Actor model
» Distribution
» Location transparency
» Isolation

Streams?
» A series of elements over time
» Events, chunks of ﬁles
» No beginning, no end

AkkaStreams
» Per-event processing
» Back-pressure
» Not distributed
» Reactive Streams compliant
» Integrate with Spark
Streaming

Typesafe ConductR
ManageTypesafe Reactive Platformapplicationsacrossacluster

Typesafe Monitoring
Knowexactlywhatyour Reactive system is doing

Commercialfeatures
» Akka Split Brain Resolver
» Akka 2.3 Cluster Support for Docker
» Play User Quotas
» Play SOAP

ProjectSuccess Subscription
» Certiﬁed build
» Compatibility veriﬁcations
» Security alerts
» Binary updates
» Long-term support
» Legal protection

Thankyou!
Visit https://www.typesafe.com/products/typesafe-
reactive-platform to get started
Contactinfo
» Twitter: @kvnwbbr
» Email: kevin.webber@typesafe.com

What's hot

The Reactive Principles: Eight Tenets For Building Cloud Native Applications

Lightbend

Having a team adopt new technologies and approaches to software development is a daunting task. New paradigms and unfamiliar ontologies headline the biggest risks to having a team be productive quickly. Lightbend (formerly Typesafe) has a suite of training classes to help you adopt whatever components of the Lightbend Reactive Platform you need to be responsive to you customers by creating resilient and elastic applications. In this webinar, we will discuss the philosophies and structures of Lightbend's training materials for Scala, Akka, Play Framework, and Spark.

Lightbend Training for Scala, Akka, Play Framework and Apache Spark

Lightbend

Distributed architecture in a cloud native microservices ecosystem

Zhenzhong Xu

Digital Transformation with Kubernetes, Containers, and Microservices

Lightbend

How to build streaming data pipelines with Akka Streams, Flink, and Spark usi...

Lightbend

It’s become clear to many business that the ability to extract real-time actionable insights from data is not only a source of competitive advantage, but also a way to defend their existing business models from disruption. So while legacy models such as nightly batch jobs aren’t disappearing, an era of fast, streaming data (aka “Fast Data”) is upon us, and represents the state of the art for gaining real-time perishable insights that can then be used to serve existing customers better, acquiring new markets and keep the competition at bay. That said, distributed, Fast Data architectures are much harder to build, and carry their own set of challenges. Enterprises looking to move quickly are presented with a growing ecosystem of technologies, which often delays fast decisions and provides its own set of risks: * With so many choices, what tools should you use? * How do you avoid making rookie mistakes? * What are the best patterns and practices for streaming applications? In this webinar with Sean Glover, Senior Consultant at Lightbend and industry veteran, we examine the rise of streaming systems built around Spark, Mesos, Akka, Cassandra and Kafka, their role in handling endless streams of data to gain real-time insights. Sean then reviews how the Lightbend Fast Data Platform (FDP) brings them together in a comprehensive, easy to use, integrated platform, which includes installation, integration, and monitoring tools tuned for various deployment scenarios, plus sample applications.

Building Streaming And Fast Data Applications With Spark, Mesos, Akka, Cassan...

Lightbend

Lessons From HPE: From Batch To Streaming For 20 Billion Sensors With Lightbe...

Lightbend

Scala Security: Eliminate 200+ Code-Level Threats With Fortify SCA For Scala

Lightbend

It is widely understood that our software needs to become reactive; we need to consider responsiveness, maintainability, elasticity and scalability from the outset. Not all systems need to implement all these to the same degree, as specific project requirements will determine where effort is most wisely spent. But, in the vast majority of cases, the need to go reactive will demand that we design our applications differently. In this presentation Dr. Roland Kuhn will explore several architecture elements that are commonly found in reactive systems, like the circuit breaker, various replication techniques, and flow control protocols. These patterns are language agnostic and also independent of the abundant choice of reactive programming frameworks and libraries. They are well-specified starting points for exploring the design space of a concrete problem: thinking is strictly required! This webinar is based off of Dr. Kuhn’s session, Reactive Design Sessions, presented at WJAX and Code Mesh.

Reactive Design Patterns

Legacy Typesafe (now Lightbend)

What is Reactive programming?

Kevin Webber

Cloudstate - Towards Stateful Serverless

Lightbend

When moving to a cloud native architecture Moogsoft knew they needed more scale than Rabbit could provide. Moogsoft moved into Kafka which is known for quick writing and driving heavy event driven workloads on top of niceties such as replayability. Choosing the tool was easy, finding a vendor that ticked all their boxes was not. They needed to ensure scalability, upgradability, builds via existing IAC pipelines, and observability via existing tools. When Moogsoft found Aiven, they were impressed with their offering and ability to scale on demand. During this presentation we will explore how Moogsoft used Aiven for Kafka to manage and scale their data in the cloud.

The Road Most Traveled: A Kafka Story | Heikki Nousiainen, Aiven

HostedbyConfluent

Going Reactive in the Land of No

Lightbend

Journey to the Modern App with Containers, Microservices and Big Data

Lightbend

Full Stack Reactive In Practice

Lightbend

How Netflix does Microservices

Manuel Correa

In this session, we will discuss: * reactive architecture tenets * distributed “fast data” streams * application and analytics focused Data Lake Enterprise level concerns and the importance of holistic governance, operational management, and a Metadata Lake will be conceptually investigated. The next level of detail will be to explore what a prospective architecture looks like at scale with Terabytes of ingestion per day, how scale puts pressure on an architecture, and how to be successful without losing data in a mission critical system via resilient, self-healing, scalable technologies. DevOps and application architecture concerns will be first-class themes throughout. Reactive principles and technology will be the second act of this talk. Kafka. Akka. Spark. Various streaming technologies (Kafka Streams, Akka Streams, Spark Streaming) will be reviewed to identify what they are best suited for. The fast data pipeline discussion will center around Kafka, Akka, and Apache Flink (Lightbend Fast Data platform). We’ll also walk through an exciting addition to the Akka family, Alpakka, which is a Camel equivalent for Enterprise Integration Patterns. The final act will be to dive into the Data Lake, from both an analytics and application development perspective. Technologies used to explain concepts will include Amazon and Hadoop. A Data Lake may service multiple analytics consumers with various “views” (and access levels) of data. It may also be a participant of various applications, perhaps by acting as a centralized source for reference data or common middleware (in turn feeding the analytics aspect). The concept of the Metadata Lake to apply structure, meaning and purpose will be an over-arching success factor for a Data Lake. The difference between the Data Lake and Metadata Lake is conceptually similar to a Halocline… Various technologies (Iglu/Snowplow and more) will be discussed from a feature standpoint to flesh out the technology capabilities needed for Data Lake governance.

Building Reactive Fast Data & the Data Lake with Akka, Kafka, Spark

Todd Fritz

How to Migrate to Cloud with Complete Confidence and Trust

Apcera

Couchbase Cloud No Equal (Rick Jacobs, Couchbase) Kafka Summit 2020

HostedbyConfluent

Something changed in job ads over the last few years: everyone wants the DevOps Unicorn. What is that and why did this happen? You probably have a good amount of what is in that description, but is there an easy way to fill in the rest of the 100%? It turns out that it is possible to fake your way to being a DevOps Unicorn. All that you need is a way to know which metrics are the most important. And to know that you need a framework that applies everywhere. No really, it's easier than you think. There is some work needed on your part, but just a few minutes is enough to get started. In this 20 minute session, we will cover what changed in the market, what the framework looks like, and how to apply it to all of the containerized applications you need to monitor.

20 mins to Faking the DevOps Unicorn by Matt williams, Datadog

Docker, Inc.

What's hot (20)