TDC2017 | São Paulo - Trilha Arquitetura Java How we figured out we had a SRE team at - Implementando Microserviços Reativos com Vert.x

•Download as PPTX, PDF•

0 likes•80 views

This document discusses reactive microservices and how Vert.x can help build them. It defines reactive systems as being elastic, resilient and responsive through asynchronous messaging. Microservices are popular due to their autonomy, isolation and ability to adapt. Vert.x is highlighted as a tool that enables scalable and non-blocking development of microservices using verticles, an event bus and shared data stores while providing high availability.

Education

Reactive software reacts and
adapts its behavior based on the
stimuli it receives

Reactive System
An architecture style
used to build
responsive and robust
distributed systems
based on asynchronous
message-passing
Reactive Programming
A development model
focusing on the
observation of data
streams, reacting on
changes, and propagating
them.

Reactive Streams
Reactive streams is an initiative to provide a
standard for asynchronous stream processing with
back-pressure

Back Pressure
when n > m, please wait!
n n
mm
Producer Consumer

Reactive Systems
Elasticity
The ability to scale horizontally (scale out/in)
Resilience
The ability to handle failure and recover
Responsive
The most important thing for all companies
Asynchronous message-passing

Reactive Microservices
Autonomy & Isolation
adapt to the availability or unavailability of the services
surrounding them
Resilience
The ability to handle failure and recover
Asynchronisity
The most important thing for all companies
Elasticity
The ability to scale horizontally (scale out/in)

Worker Verticles
Worker Loop
Non-Concurrent
Blocking

Event Bus
Publisher and Subscribe
Point 2 Point
Clustered

Shared Data
Local and Distributed using
Hazelcast

High Availability
Cluster Manager using Hazelcast
with automatic failover

mrbrazjava
I help developers and architects to be more productive on
distributed system development for them to be recognized as
references in the market. geracaosucesso.com

Lagom is an open source framework for building reactive microservice systems that age well over time. It provides tools and architectural patterns to help systems maintain integrity as requirements change rapidly. Lagom aims to minimize complexity through isolation of services, asynchronous messaging, and other patterns. It also aims to protect developer productivity through its Scala and Java APIs and other features.

Divide and Conquer: Easier Continuous Delivery using Micro-Services

Carlos Sanchez

Docker has revolutionized the way people think about applications and deployments. It provides a simple way to run and distribute Linux containers for a variety of use cases, from lightweight virtual machines to complex distributed micro-services architectures. Containers allow to run services in isolation with a minimum performance penalty, increased speed, easier configuration and less complexity, making it ideal for continuous integration and continuous delivery based workloads. But testing a distributed micro-services architecture is no easy task, requiring a shift in mindset and tooling to accommodate the new architecture. We will provide insight on our experience creating a Jenkins platform based on distributed Docker containers running on Apache Mesos and Marathon, applicable for all types of applications, but specially Java and JVM based ones.

Introduction to microservices

Anil Allewar

TechEd NZ 2014: Building Web Applications at Scale with Azure Web Sites

Intergen

TechEd NZ 2014 - DEV320 - James Carpinter Building a web app with Azure Web Sites couldn't be easier. But building one that handles thousands of requests per second requires more than just turning on auto scale. Building scalable, reliable, maintainable and high performing web apps requires an understanding of the platform as well as the right application architecture. Come learn about patterns and practices to adopt for your next web app, whether it be at local scale or global scale.

5 PaaS myths every CIO needs to get over

RedPixie

This document discusses and dispels 5 common myths that CIOs have about platform-as-a-service (PaaS). The myths addressed are that PaaS won't help businesses, that businesses will lose control, that businesses cannot transition back from PaaS, that all PaaS offerings are the same, and that moving to PaaS will be too difficult. The document argues that PaaS provides benefits like better performance, lower costs, and easier maintenance for businesses of all sizes and allows businesses to retain control of applications while outsourcing infrastructure concerns. It also notes that PaaS offerings differ and that transitions to PaaS can be simpler than expected with the right support.

VMware vRealize Operations Management Pack for Amazon DynamoDB

Blue Medora

Debugging and interacting with production applications

Michel HUBERT

This document discusses debugging and monitoring applications in Microsoft Azure. It provides an overview of Azure Monitor, which offers unified monitoring of metrics, logs and other telemetry across infrastructure, applications and networks. Azure Monitor uses machine learning capabilities to provide data-driven insights. It also integrates with popular DevOps, issue management and IT security tools. Application Insights is highlighted as a key part of Azure Monitor for application monitoring and analytics. It provides visibility into applications, insights to find and fix problems, and helps with optimization. Features like instant analytics, integrations with DevOps tools, app mapping and correlated tracing are discussed. Snapshot debugging and deployment slots in Azure are also summarized.

MLB Advanced Media: Delivering a Digital Experience to 25 Million Fans with N...

Amazon Web Services

When it comes to streaming live video across the web for millions of users, the stakes are high. Major League Baseball Advanced Media (MLBAM) is the dedicated streaming platform for MLB as well as other high-profile clients such as HBO Now. Since user experience is a critical aspect of their offering, MLBAM embraced a DevOps approach to application development and deployment, leading them to Amazon Web Services and New Relic. Join us for our upcoming webinar where speakers from New Relic, AWS, and MLBAM will explain how MLBAM uses the scalability of AWS and the visibility provided by New Relic to produce the “gold standard” for digital streaming video infrastructure.

The document discusses how virtual cloud computing can help businesses grow and maximize their potential. It defines cloud servers as logical servers built and hosted through cloud platforms over the internet, allowing access to multiple systems on shared hardware. Cloud servers offer advantages like scaling resources on demand, reliability through data redundancy, security through cloud tools, flexibility for employees, and global access. The document provides examples of how cloud benefits like these can help businesses scale, have reliable access to data, protect security, and more. It concludes by promoting a cloud hosting provider called SageNext.

Transform Fearlessly to Serverless with Dynatrace 2 - DEM07 - Toronto AWS Summit

Amazon Web Services

When breaking your monolith into components, services or even functions you must understand WHERE and HOW you break your existing code base and architecture into smaller units to allow it to SCALE, PERFORM and make it EASY enough to operate! This session shows how Dynatrace redefined their architecture; which migration capabilities Dynatrace engineers built into their product; and how the lessons learned can benefit all of us to transform Fearless from Monolith to Serverless!

Computaris cloud and DevOps services

Computaris

The document discusses services related to migrating applications and workloads to the cloud. It offers consulting to define a cloud roadmap and architecture, development of cloud native software using Agile methodology, and migration of legacy applications to the cloud using microservices. It also provides integration of cloud applications with on-premise systems and experience with platforms like AWS, Azure, and OpenStack. Automation services adopt DevOps tools like CI/CD, containers and configuration management. Additional DevOps engineers can assist with DevOps expertise and accelerating a client's DevOps transformation process.

How to Broker Access to vSphere and Cloud

RightScale

Windows Server 2012: Top Technical Reasons to Upgrade

CHIPS Technology Group

The New Normal - Eric Gales, AWS Canada

TriNimbus

Managing RightScale on RightScale

RightScale

RightScale uses RightScale to manage its own infrastructure including production, staging, development, and meta systems. The production environment has hundreds of servers running in various clouds to provide high availability. Upgrades are done by launching new servers with the latest code while keeping existing servers available as a rollback option. Monitoring is extensive and includes monitoring the monitoring systems. Key RightScale features like server templates and the library are very useful but some areas could be improved.

DevOps at Scale: How Datadog is using AWS and PagerDuty to Keep Pace with Gr...

Amazon Web Services

Meeting the demands of everchanging IT management and security requirements means evolving both how you respond to and resolve incidents. It’s critical for organizations to adopt a scalable DevOps solution that integrates with their current monitoring systems to enable collaboration across development and operations teams, reducing the mean time to resolution. PagerDuty works with AWS services like Amazon CloudWatch, to provide rapid incident response with rich, contextual details that allow you to analyze trends and monitor the performance of your applications and AWS environment.

re:Invent Recap Breakfast

Jimmy Dahlqvist

The document summarizes discussions from re:Invent 2021 about sustainability, serverless computing, community initiatives, and low-code/no-code tools. On sustainability, AWS is adding it as a new pillar and tools like the carbon footprint calculator. Serverless options were expanded for services like S3, MSK, Redshift, and EMR. The community is using new forums like re:Post and improvements to CDK. Low-code tools like Amplify Studio and SageMaker Canvas make app and model building more accessible. The takeaways note sustainability as a hot topic and continued investment in serverless.

Introduction to testing in Cloud / AWS

Jimmy Dahlqvist

This document provides an overview of cloud concepts including cloud native applications, infrastructure as code, automation, microservices, serverless computing, deployment methods, chaos engineering, and observability. Specifically, it discusses how cloud native applications are loosely coupled and scale independently, the benefits of modeling infrastructure as code and storing it in version control, and techniques for automating infrastructure provisioning, testing, and deployments. It also covers asynchronous communication, event-driven architectures, blue/green and canary deployments, and using chaos engineering experiments to test system reliability in production environments.

Security management using devops | LCloud

LCloud

Security is one of the most important aspects when designing and creating environments in the cloud. It is worth considering infrastructure design in relation to best practices. DevOps can be such an example. All the sources are linked in the presentation. Enjoy and don't forget to check out our blog and other social media! LCloud Blog https://bit.ly/2Vgooz4 Facebook https://bit.ly/2tCqBJS Twitter https://twitter.com/LCLOUD16 LinkedIn https://bit.ly/2syaQCr YouTube https://bit.ly/2tGV62b Questions? Feel free to ask: kontakt@lcloud.pl https://lcloud.pl/

Strategic Approaches to AWS Enterprise Application Migration

Amazon Web Services

This document discusses strategic approaches to migrating enterprise applications to AWS. It presents three approaches: Lift and Shift, which involves pushing existing hardware to AWS with minimal transformation; Build it and Pull, a demand-driven approach where user teams migrate apps; and a 2-Step approach that combines pushing to a holding zone then pulling to a future state. It also discusses Qantas' experience migrating applications to AWS, how they created a migration strategy and capability, partnered with Sourced Group, and achieved results like 90% lower infrastructure costs and 100% uptime of migrated components.

Event driven architecture

Shadrach Jabonir

The document discusses event-driven architecture (EDA). EDA is a software architecture pattern that promotes processing, detecting, consuming, and reacting to events. An event is defined as a significant change in state. EDA allows for real-time processing as events happen, push notifications, and immediate actions by consumers without waiting. EDA is scalable in processing, design, and adapting to change. It focuses on domain logic and collaborating with domain experts. EDA uses message brokers, producers that generate events, and consumers that process events.

Launch .NET Applications in the Cloud

RightScale

RightScale User Conference NYC 2011 - Raphael Simon - Senior Systems Architect, RightScale Shivan Bindal - Product Manager, RightScale Deploying Windows-based applications in the cloud has historically been challenging because the available machine images were often inconsistent across regions/clouds and they lacked simple remote control. Add in the inflexibility that comes with pre-baked application stacks along with a lack of consistent automation, and you have the recipe for a sudden onset migraine. With RightScale ServerTemplates™, you can dynamically configure, launch, and manage your Windows software stacks in the cloud. We'll showcase a proven setup for a scalable, production .NET web application and present a live demo in which we'll use ServerTemplates with built-in Microsoft best practices to launch a SQL Server-based web application.

Updating Security Operations for the Cloud

Amazon Web Services

Learn how to increase the effectiveness of your security operations as you move to the cloud. We will discuss how your current incident response, forensic investigations, monitoring, and audit response tactics have to change in the cloud. Pulling from experiences helping clients move to the cloud, industry research, and the school of hard knocks, this talk will help provide practical advice you can apply today.

10 Good Reasons - NetApp FlexPod

NetAppUK

FlexPod is a converged infrastructure solution from NetApp and Cisco that can be deployed and ready for use within 60 minutes (sentence 1). It provides a single management layer for compute, networking and storage to simplify administration and free up IT staff from manual tasks (sentence 2). FlexPod allows independent scalability of compute and storage resources to meet the needs of different workloads (sentence 3).

Actor model in F# and Akka.NET

Riccardo Terrell

The document discusses the actor model and how it can solve problems for building concurrent, distributed, asynchronous, high performance, scalable, and fault tolerant systems. It outlines how the actor model aligns with the principles of the Reactive Manifesto by being responsive, message-driven, resilient, and elastic. Actors communicate asynchronously through message passing, isolate state and processing, and can be distributed across multiple machines through clustering and remoting.

Reactive Architecture

Knoldus Inc.

Reactive programming is an asynchronous programming paradigm, concerned with streams of information and the propagation of changes. This differs from imperative programming, where that paradigm uses statements to change a program’s state. Reactive Architecture is nothing more than the combination of reactive programming and software architectures. Also known as reactive systems, the goal is to make the system responsive, resilient, elastic, and message-driven.

Building a High-Performance Reactive Microservices Architecture

Cognizant

Reactive Microservices

Crishantha Nanayakkara

Reactive Microservices

Knoldus Inc.

Event Driven Software Architecture Pattern

jeetendra mandal

An event-driven architecture consists of event producers that generate event streams and event consumers that listen for events. It allows for loose coupling between components and asynchronous event handling. Key aspects include publish/subscribe messaging patterns, event processing by middleware, and real-time or near real-time information flow. Benefits include scalability, loose coupling, fault tolerance, and the ability to add new consumers easily. Challenges include guaranteed delivery, processing events in order or exactly once across multiple consumer instances. Common tools used include Apache Kafka, Apache ActiveMQ, Redis, and Apache Pulsar.

What's hot

High performance Of Cloud Computing

Stuart Braud

Transform Fearlessly to Serverless with Dynatrace 2 - DEM07 - Toronto AWS Summit

Amazon Web Services

Computaris cloud and DevOps services

Computaris

How to Broker Access to vSphere and Cloud

RightScale

Windows Server 2012: Top Technical Reasons to Upgrade

CHIPS Technology Group

The New Normal - Eric Gales, AWS Canada

TriNimbus

Managing RightScale on RightScale

RightScale

DevOps at Scale: How Datadog is using AWS and PagerDuty to Keep Pace with Gr...

Amazon Web Services

re:Invent Recap Breakfast

Jimmy Dahlqvist

Introduction to testing in Cloud / AWS

Jimmy Dahlqvist

Security management using devops | LCloud

LCloud

Strategic Approaches to AWS Enterprise Application Migration

Amazon Web Services

Event driven architecture

Shadrach Jabonir

Launch .NET Applications in the Cloud

RightScale

Updating Security Operations for the Cloud

Amazon Web Services

10 Good Reasons - NetApp FlexPod

NetAppUK

What's hot (16)

High performance Of Cloud Computing

Transform Fearlessly to Serverless with Dynatrace 2 - DEM07 - Toronto AWS Summit

Computaris cloud and DevOps services

How to Broker Access to vSphere and Cloud

Windows Server 2012: Top Technical Reasons to Upgrade

The New Normal - Eric Gales, AWS Canada

Managing RightScale on RightScale

DevOps at Scale: How Datadog is using AWS and PagerDuty to Keep Pace with Gr...

re:Invent Recap Breakfast

Introduction to testing in Cloud / AWS

Security management using devops | LCloud

Strategic Approaches to AWS Enterprise Application Migration

Event driven architecture

Launch .NET Applications in the Cloud

Updating Security Operations for the Cloud

10 Good Reasons - NetApp FlexPod

Similar to TDC2017 | São Paulo - Trilha Arquitetura Java How we figured out we had a SRE team at - Implementando Microserviços Reativos com Vert.x

Actor model in F# and Akka.NET

Riccardo Terrell

Reactive Architecture

Knoldus Inc.

Building a High-Performance Reactive Microservices Architecture

Cognizant

Reactive Microservices

Crishantha Nanayakkara

Reactive Microservices

Knoldus Inc.

Event Driven Software Architecture Pattern

jeetendra mandal

Microservices Interview Questions and Answers pdf by ScholarHat

Scholarhat

Next generation of frontend architectures

luca mezzalira

Reactive applications and microservices with Vert.x tool-kit

Victor Hugo

This document discusses reactive applications and microservices using the Vert.x toolkit. It defines reactive as responding quickly to stimuli. Reactive systems are responsive, rapid, resilient, and scalable. Microservices break applications into smaller, independent services. Vert.x is a toolkit that can build reactive and microservices applications. It is lightweight, fast, modular, and supports multiple programming languages. Vert.x allows building scalable, high-performance microservices and applications.

Reactive Integrations - Caveats and bumps in the road explained

Markus Eisele

Becoming reactive without overreacting (@pavlobaron)

Pavlo Baron

This document discusses the reactive approach to building enterprise systems. It argues that becoming reactive means making reactiveness explicit rather than implicit. All systems are inherently reactive under the hood due to things like threading, event loops, and interrupts. The benefits of reactive systems include responsiveness to change and resource efficiency. Some challenges to going reactive include overcoming the temptation to go fully or partially reactive without understanding reactivity, and writing one's own reactive framework instead of using existing ones.

Reactive - Is it really a Magic Pill?

Tech Triveni

Reactive stack paints a very rosy picture of the way to develop the scalable applications focusing on the 4 fundamental things that are responsive, elastic, resilient and asynchronous communication. The principles are pretty simple but there are a lot of pitfalls that nobody talks about. The challenges are numerous to build the system in the right way and in this talk we will focus on what are these pitfalls and how can we avoid them. We will be exploring the myth that once you adapt to it the journey will be smooth and show how these distributed systems add to additional complexity but can be managed by making smart decisions. I will share our experience of building Reactive Applications and how we have overcome the difficulties that we encounter.

Reactive: Programming -> Systems -> Architecture

Aleksey Izmailov

Service Ecosystem

Richard Veryard

The document discusses an ecological approach to analyzing software and service development based on separating the domain into four interconnected ecosystems: service use, service supply, device use, and device supply. Each ecosystem has different ecological principles that guide development, such as network effects, availability, flexibility, and biodiversity. Components must satisfy the principles of multiple ecosystems to survive and thrive within this framework.

A Guide on What Are Microservices: Pros, Cons, Use Cases, and More

Simform

Resisting to The Shocks

Stefano Fago

1) Resilience refers to a system's ability to recover quickly from difficulties or withstand disruptions. A resilient system has qualities like modularity, diversity, and decoupling to prevent problems in one part from spreading. 2) Distributed systems need resilience because perfect reliability is impossible and many systems are not built to withstand real-world conditions after launch. Failures can occur from things like network issues, resource exhaustion, or dependency failures. 3) To improve resilience, systems can employ patterns like isolation, queueing, timeouts, retries, fallbacks, and circuit breakers to absorb failures and degrade gracefully instead of failing completely. Monitoring and chaos engineering can help test a system's resilience.

What is reactive

Lightbend

The document discusses how being reactive is good. It argues that reactive principles like being asynchronous, non-blocking, elastic and resilient help engineers, businesses and enterprises capture opportunities. Being message-driven and responsive to events within the business and market allows systems to scale efficiently. The Lightbend Reactive Platform and tools like Akka and Play can be used to build fully reactive microservices systems that are responsive, elastic and resilient. Reactive architectures allow modernizing existing systems and responding to changes in technology, users and opportunities.

Antifragile Software Design

Hayim Makabee

The concept of Antifragility was introduced by Nassim Taleb to describe systems that benefit from impacts and volatility. In this talk we will discuss how this concept may be applied in the field of Software Design with the goal of developing Change-Resilient Systems. In particular we will address two patterns which frequently appear in Antifragile systems: 1) The Barbell Strategy and the importance of the separation between high-level abstract elements and concrete implementation details. 2) The Componentization Strategy and its applications in SOA, Microservices and Software Product Lines.

Managing and Scaling Microservices with Docker in the Wild

Alois Mayr

Architectural Patterns of Resilient Distributed Systems

Ines Sombra

This document contains the slides from a presentation given by Ines Sombra at Strangeloop 2015 about architectural patterns for building resilient distributed systems. The presentation discusses defining resilience, models of resilience from literature like probabilistic availability and decomposition/orthogonality. It also discusses insights from industry systems like Netflix, Google Chubby, Twitter Truce, and resilient architectural patterns like redundancies, gossip protocols, and prioritizing operability and the ability to handle unknown unknowns.

Similar to TDC2017 | São Paulo - Trilha Arquitetura Java How we figured out we had a SRE team at - Implementando Microserviços Reativos com Vert.x (20)

Actor model in F# and Akka.NET

Reactive Architecture

Building a High-Performance Reactive Microservices Architecture

Reactive Microservices

Event Driven Software Architecture Pattern

Microservices Interview Questions and Answers pdf by ScholarHat

Next generation of frontend architectures

Reactive applications and microservices with Vert.x tool-kit

Reactive Integrations - Caveats and bumps in the road explained

Becoming reactive without overreacting (@pavlobaron)

Reactive - Is it really a Magic Pill?

Reactive: Programming -> Systems -> Architecture

Service Ecosystem

A Guide on What Are Microservices: Pros, Cons, Use Cases, and More

Resisting to The Shocks

What is reactive

Antifragile Software Design

Managing and Scaling Microservices with Docker in the Wild

Architectural Patterns of Resilient Distributed Systems

More from tdc-globalcode

TDC2019 Intel Software Day - Visao Computacional e IA a servico da humanidade

TDC2017 | São Paulo - Trilha Arquitetura Java How we figured out we had a SRE team at - Implementando Microserviços Reativos com Vert.x

Recommended

Recommended

More Related Content

What's hot

What's hot (16)

Similar to TDC2017 | São Paulo - Trilha Arquitetura Java How we figured out we had a SRE team at - Implementando Microserviços Reativos com Vert.x

Similar to TDC2017 | São Paulo - Trilha Arquitetura Java How we figured out we had a SRE team at - Implementando Microserviços Reativos com Vert.x (20)

More from tdc-globalcode

More from tdc-globalcode (20)

Recently uploaded

Recently uploaded (20)

TDC2017 | São Paulo - Trilha Arquitetura Java How we figured out we had a SRE team at - Implementando Microserviços Reativos com Vert.x