Patterns for Asynchronous Microservices with NATS

•Download as PPTX, PDF•

5 likes•1,514 views

Presentation from a talk by Raul Perez (@repejota) of R3Labs on asynchronous microservices patterns using NATS (@nats_io), the lightweight, high performance open source messaging system written in Go. You can learn more about NATS at http://www.nats.io

Technology

Patterns for Asynchronous
Microservices
Raül Pérez - @repejota NATS London - 10/05/2016

Who am I?
Raül Pérez
Lead Software Engineer
at R3 Labs Ltd.
Twitter: @repejota
Github: https://github.com/repejota
Email: repejota@gmail.com
2
Raül Pérez - @repejota NATS London - 10/05/2016

Who am I?
Raül Pérez
Lead Software Engineer
at R3 Labs Ltd.
Twitter: @repejota
Github: https://github.com/repejota
Email: repejota@gmail.com
3
● Almost 4 years working on devops & distributed projects.
Raül Pérez - @repejota NATS London - 10/05/2016

Who am I?
Raül Pérez
Lead Software Engineer
at R3 Labs Ltd.
Twitter: @repejota
Github: https://github.com/repejota
Email: repejota@gmail.com
4
● Almost 4 years working on devops & distributed projects.
● Still more a dev than op dude.
Raül Pérez - @repejota NATS London - 10/05/2016

Who am I?
Raül Pérez
Lead Software Engineer
at R3 Labs Ltd.
Twitter: @repejota
Github: https://github.com/repejota
Email: repejota@gmail.com
5
● Almost 4 years working on devops & distributed projects.
● Still more a dev than op dude.
● Proud to be a Gopher after a looong PHP/Ruby/Python/Node.js past
experience. :P
Raül Pérez - @repejota NATS London - 10/05/2016

Who am I?
Raül Pérez
Lead Software Engineer
at R3 Labs Ltd.
Twitter: @repejota
Github: https://github.com/repejota
Email: repejota@gmail.com
6
● Almost 4 years working on devops & distributed projects.
● Still more a dev than op dude.
● Proud to be a Gopher after a looong PHP/Ruby/Python/Node.js past
experience. :P
● Based in Barcelona.Raül Pérez - @repejota NATS London - 10/05/2016

Who am I?
Raül Pérez
Lead Software Engineer
at R3 Labs Ltd.
Twitter: @repejota
Github: https://github.com/repejota
Email: repejota@gmail.com
7
● Almost 4 years working on devops & distributed projects.
● Still more a dev than op dude.
● Proud to be a Gopher after a looong PHP/Ruby/Python/Node.js past
experience. :P
● Based in Barcelona.Raül Pérez - @repejota NATS London - 10/05/2016

Summary
8
Raül Pérez - @repejota NATS London - 10/05/2016
● Why microservices?
● Synchronous vs. Asynchronous communication.
● Pattern: Broker approach & NATS
● Pattern: Autonomy of services vs. Coordination between services.

Why microservices?
9
Raül Pérez - @repejota NATS London - 10/05/2016
● Loosely coupled components.
● Specific responsibility, each one delivers a capability.
● Designed to be defensive against failures.

Why microservices?
10
Raül Pérez - @repejota NATS London - 10/05/2016
● Loosely coupled components.
● Specific responsibility, each one delivers a capability.
● Designed to be defensive against failures.
● Designed around business needs.
● Decentralised governance.
● Decentralised data management.
● Connected through a common interface.

Pattern: Sync vs. Async communication.
11
Raül Pérez - @repejota NATS London - 10/05/2016
● The most common interface to communicate is HTTP.
● But HTTP is “mostly” synchronous.
● Once the number of services grow, HTTP is sometimes not enough.

Pattern: Sync vs. Async communication.
12
Raül Pérez - @repejota NATS London - 10/05/2016
● The most common interface to communicate
is HTTP.
● But HTTP is “mostly” synchronous.
● Once the number of services grow, HTTP is
not enough.
● It also has a complex error
management.

Pattern: Sync vs. Async communication.
13
Raül Pérez - @repejota NATS London - 10/05/2016
● Synchronous communication is simple but….
○ Drawback: Suffers from latency on each connection.
● Asynchronous communication is faster but…
○ Drawback: Increases the complexity.
○ Drawback: Snowball effect, difficult to manage and orchestrate.
So, Is there a better communication interface?

Pattern: Sync vs. Async communication.
14
Raül Pérez - @repejota NATS London - 10/05/2016
● Pattern: Use a broker to orchestrate your communication needs.
○ AMPQ, RabbitMQ, NSQ, etc ….
○ NATS :)
● A broker is flexible, allows you to use:
○ Work queues.
○ Publish/Subscribe.
○ Request/Response.
○ Message routing.
○ etc...

Pattern: Broker approach & NATS
15
Raül Pérez - @repejota NATS London - 10/05/2016
● Loosely coupled clients and servers.
● Multiple patterns: Publish/Subscribe,
Request/Response.
● Easy to scale.

Pattern: Broker approach & NATS
16
Raül Pérez - @repejota NATS London - 10/05/2016
● Loosely coupled clients and servers.
● Multiple patterns: Publish/Subscribe,
Request/Response.
● Easy to scale.
● NATS is fast!

Pattern: Broker approach & NATS
17
Raül Pérez - @repejota NATS London - 10/05/2016
● Loosely coupled clients and servers.
● Multiple patterns: Publish/Subscribe,
Request/Response.
● Easy to scale.
● NATS is fast!
● Just a message system, no
assumptions, no extra features.
Easy to deploy, easy to use.

Pattern: Broker approach & NATS
18
Raül Pérez - @repejota NATS London - 10/05/2016
● Loosely coupled clients and servers.
● Multiple patterns: Publish/Subscribe,
Request/Response.
● Easy to scale.
● NATS is fast!
● Just a message system, no
assumptions, no extra features.
Easy to deploy, easy to use.
● It is also secure: SSL, password ...

Pattern: Broker approach & NATS
19
Raül Pérez - @repejota NATS London - 10/05/2016
● Loosely coupled clients and servers.
● Multiple patterns: Publish/Subscribe,
Request/Response.
● Easy to scale.
● NATS is fast!
● Just a message system, no
assumptions, no extra features.
Easy to deploy, easy to use.
● It is also secure: SSL, password ...
● Simple protocol, it is just text.

Pattern: Autonomy vs. Coordination.
20
Raül Pérez - @repejota NATS London - 10/05/2016
● Make your services autonomous.
● Avoid coordination between different services.
● The minimal coordination the more optimal autonomy.
● Increased autonomy gives it freedom to evolve.

Pattern: Autonomy vs. Coordination.
21
Raül Pérez - @repejota NATS London - 10/05/2016
● Make your services autonomous.
● Avoid coordination between different services.
● The minimal coordination the more optimal autonomy.
● Increased autonomy gives it freedom to evolve.
● Your services delivers “capabilities”

Pattern: Autonomy vs. Coordination.
22
Raül Pérez - @repejota NATS London - 10/05/2016
● Make your services autonomous.
● Avoid coordination between different services.
● The minimal coordination the more optimal autonomy.
● Increased autonomy gives it freedom to evolve.
● Your services delivers “capabilities”
● What is a capability?
A complete business capability is a process that can be finished
consecutively without interruptions or excursions to other services.

Resources
● http://microservices.io
● https://en.wikipedia.org/wiki/Cloud_computing
● http://nats.io
23
● http://repejota.com
● http://r3labs.io
● http://ernest.io
● http://apcera.comRaül Pérez - @repejota NATS London - 10/05/2016

Questions?
Raül Pérez - @repejota NATS London - 10/05/2016

Thank you!
25Raül Pérez - @repejota NATS London - 10/05/2016

NATS 2.0 is the largest feature release since the original code base for the server was released. NATS 2.0 was created to allow a new way of thinking about NATS as a shared utility, solving problems at scale through distributed security, multi-tenancy, larger networks, and secure sharing of data. In this presentation, Derek discusses the motives behind the newest features of NATS and how to leverage them to reduce total cost of ownership, decrease time to value, support extremely large scale deployments, and decentralize security to create secure and easy to manage modern distributed systems.

KubeCon NA 2019 Keynote | NATS - Past, Present, and the Future

NATS

On-demand recording: https://www.nginx.com/resources/webinars/mra-ama-part-6-service-mesh-models/ Speakers: Charles Pretzer Technical Architect NGINX, Inc. Floyd Smith Director of Content Marketing NGINX, Inc. About the webinar: In this webinar, two models of the NGINX Microservices Reference Architecture, the Router Mesh Model and the Fabric Model, are shown as successively more capable implementations of a service mesh architecture. We compare the MRA models to Istio, linkerd, and other service mesh architectures, and show how the NGINX Kubernetes Ingress Controller allows direct use of these other architectures. Attendees of the live webinar will have the opportunity to ask questions. Service mesh models are an emerging standard for microservices development and deployment. Popular architectures such as Istio and linkerd use a service mesh approach, including attributes such as load balancing capability, support for authorization and authentication, and use of the circuit breaker model for resiliency. Watch this webinar to learn: - Key problems solved by using a service mesh model for microservices _ How different service mesh architectures compare to each other - How to use NGINX service mesh models - the Router Mesh Model and Fabric Model of the MRA - How the Kubernetes Ingress Controller enables the use of NGINX in Istio, linkerd, and other service mesh models

NATS Connect Live | SwimOS & NATS

NATS

MRA AMA: Ingenious: The Journey to Service Mesh using a Microservices Demo App

NGINX, Inc.

On-demand Link: https://www.nginx.com/resources/webinars/microservices-ingenious-journey-service-mesh-demo-app/ In this webinar, we discuss how Ingenious is (mostly) the same, but also the differences in its code, features, and runtime behavior, as it’s implemented in various architectural models. You then get a chance to ask us, well, anything about microservices, the MRA, and service mesh architectures. Join this webinar to learn" - The reasons for choosing one architecture over others for your app icon - How apps can maximize architecture-independence, giving you maximum flexibility in development and deployment icon - How the features, performance, stability, and reliability of the Ingenious demo app benefit from various microservices architectures icon How to secure the Ingenious app, and your own apps, across different architectures

Introducing the Microservices Reference Architecture Version 1.2

NGINX, Inc.

About the webinar Application development using microservices is changing very quickly, even as many organizations are gearing up to produce their first full-fledged microservices apps, or expand microservices development. Among these changes are the emergence of Kubernetes as the most widely -used approach to container management and the arrival of service mesh architectures. The Istio service mesh architecture has reached version 1.0. There is also an increasing recognition of the need for security in service-to-service communications. In the upcoming Version 1.2 of the Microservices Reference Architecture, NGINX will offer an update to its robust and flexible array of models for microservices development, giving developers much more choice and the opportunity to “right-size” the microservices model they choose to the task at hand, while preserving the opportunity for future growth.

GopherCon 2017 - Writing Networking Clients in Go: The Design & Implementati...

wallyqs

Cloud-Native Progressive Delivery

Matt Turner

Cloud Solution Day 2016: Service Mesh for Kubernetes

AWS Vietnam Community

Dual write strategies for microservices

Bilgin Ibryam

Running a Robust DNS Infrastructure with CloudFlare Virtual DNS

Cloudflare

NGINX, Istio, and the Move to Microservices and Service Mesh

NGINX, Inc.

On-demand recording: https://www.nginx.com/resources/webinars/istio-move-to-microservices-service-mesh/ About the webinar NGINX is widely known, used, and trusted for a variety of purposes. NGINX works as a reliable, high-performance web server, reverse proxy server, and load balancer. NGINX is also a widely used microservices hub, an Ingress controller for Kubernetes, and a sidecar proxy in the Istio service mesh. In this webinar, we’ll describe the move to microservices, the crucial role that NGINX has already played, and a range of architectural options that organizations have for their microservices apps, including three progressively complex models in the NGINX Microservices Reference Architecture. We’ll then introduce the emergence of Kubernetes as a container orchestration framework, the use of service mesh architectures, and the design of Istio. We’ll finish by showing how NGINX Open Source and NGINX Plus can be used as the sidecar proxy in an Istio service mesh, bringing greater reliability and capability to your service mesh application.

Loadbalancers: The fabric for your micro services

Chiradeep Vittal

An approach for migrating enterprise apps into open stack

Arthur Berezin

Simplify Microservices with the NGINX Application Platform

NGINX, Inc.

Learn how we discuss our vision for reducing complexity and building microservices applications with the NGINX Application Platform. On-demand recording: https://www.nginx.com/resources/webinars/updating-nginx-application-platform/ - Our vision for building microservices applications with the NGINX Application Platform icon - How the NGINX Application Platform is helping our customers reduce cost and complexity icon - How the NGINX Application Platform will help you consolidate multiple tools and solutions icon - The latest updates about products in the NGINX Application Platform About the webinar At NGINX we help simplify the journey to microservices. Many of our customers would love to migrate to microservices, but have been held back by existing, complex application infrastructures with years of technical debt. When we talk to these companies, they’re surprised by how much they can simplify their infrastructure by consolidating common functions onto NGINX Plus. With the NGINX Application Platform, we can collapse ten disparate functions into a single product suite. This includes web server, load balancer, reverse proxy, content cache, application server, web application firewall (WAF), API gateway, Kubernetes ingress controller, sidecar proxy, and service mesh controller. Using the NGINX Application Platform, we are helping our customers reduce complexity and begin migrating to a modern, microservices-based architecture.

linkerd: The Cloud Native Service Mesh

Dario Simonetti

InfluxCloudi craft container orchestrator

Gianluca Arbezzano

Encode

Vanessa Lošić

Dynamic routing in microservice oriented architecture

Daniel Leon

Microservices

NewsCred Dhaka

NewsCred Dhaka hosted an interactive session on MircroServices. The main focus of the event was to provide a platform for people to share their experiences, understand the architecture and hear about the challenges and benefits of continuous deployment. Presenters: Asif Rahman (CTO), Brian Schmitz (Director of Engineering), Rana Khandakar (Lead Software Engineer), Ashrafuzzaman Jitu (Engineering Manager), and Zahiduzzaman Setu (Senior Software Engineer), as they share their experiences with MicroServices and in the process find out if it is right for you.

NATS: A Central Nervous System for IoT Messaging - Larry McQueary

Apcera

Security, identity and scalability define the IoT landscape. Developers in any IoT ecosystem need a flexible, lightweight and secure method to communicate device status/telemetry and content that operates at the speed of a central nervous system and doesn’t rely on inflexible and outdated protocol specifications designed for point-to-point communication. Enter NATS. NATS is an open source messaging framework based on Go that is designed for simple, secure, lightweight and scalable messaging in any language and for any platform/processor architecture. Larry McQueary present's an overview and short demonstration on the NATS architecture and API that will demonstrate how NATS can enable “things” and backend infrastructure to communicate securely and scalably at high speed without locking in vendor-specific technology or protocols. You can learn more about NATS at http://www.nats.io

Nats in action a real time microservices architecture handled by nats

Raul Perez

Implementing Microservices with NATS

Apcera

What's hot

Using an API Gateway for Microservices (APAC Webinar)

NGINX, Inc.

MRA AMA Part 6: Service Mesh Models

NGINX, Inc.

NATS Connect Live | SwimOS & NATS

NATS

MRA AMA: Ingenious: The Journey to Service Mesh using a Microservices Demo App

NGINX, Inc.

Introducing the Microservices Reference Architecture Version 1.2

NGINX, Inc.

GopherCon 2017 - Writing Networking Clients in Go: The Design & Implementati...

wallyqs

Cloud-Native Progressive Delivery

Matt Turner

Cloud Solution Day 2016: Service Mesh for Kubernetes

AWS Vietnam Community

Dual write strategies for microservices

Bilgin Ibryam

Running a Robust DNS Infrastructure with CloudFlare Virtual DNS

Cloudflare

NGINX, Istio, and the Move to Microservices and Service Mesh

NGINX, Inc.

Loadbalancers: The fabric for your micro services

Chiradeep Vittal

An approach for migrating enterprise apps into open stack

Arthur Berezin

Simplify Microservices with the NGINX Application Platform

NGINX, Inc.

linkerd: The Cloud Native Service Mesh

Dario Simonetti

InfluxCloudi craft container orchestrator

Gianluca Arbezzano

Encode

Vanessa Lošić

Dynamic routing in microservice oriented architecture

Daniel Leon

Microservices

NewsCred Dhaka

What's hot (19)

Using an API Gateway for Microservices (APAC Webinar)

MRA AMA Part 6: Service Mesh Models

NATS Connect Live | SwimOS & NATS

MRA AMA: Ingenious: The Journey to Service Mesh using a Microservices Demo App

Introducing the Microservices Reference Architecture Version 1.2

GopherCon 2017 - Writing Networking Clients in Go: The Design & Implementati...

Cloud-Native Progressive Delivery

Cloud Solution Day 2016: Service Mesh for Kubernetes

Dual write strategies for microservices

Running a Robust DNS Infrastructure with CloudFlare Virtual DNS

NGINX, Istio, and the Move to Microservices and Service Mesh

Loadbalancers: The fabric for your micro services

An approach for migrating enterprise apps into open stack

Simplify Microservices with the NGINX Application Platform

linkerd: The Cloud Native Service Mesh

InfluxCloudi craft container orchestrator

Encode

Dynamic routing in microservice oriented architecture

Microservices

Viewers also liked

NATS: A Central Nervous System for IoT Messaging - Larry McQueary

Apcera

Nats in action a real time microservices architecture handled by nats

Raul Perez

Implementing Microservices with NATS

Apcera

Simple and Scalable Microservices: Using NATS with Docker Compose and Swarm

Apcera

Waldemar Quevedo, Senior Software Engineer at Apcera NATS is a high-performance messaging system optimized for simplicity, reliability and low latency which can be a lightweight solution for the internal communication of your distributed system. In this talk, we will cover its core feature set as well as how to develop and assemble NATS-based microservices using the latest Docker tooling such as Compose and Swarm mode. You can learn more about NATS at http://www.nats.io

NATS for Modern Messaging and Microservices

Apcera

The Current Messaging Landscape: RabbitMQ, ZeroMQ, nsq, Kafka

All Things Open

Debugging Network Issues

Apcera

Jaime Piña, @variadico, Software Engineer at Apcera Microservice issues are networking issues. Fixing code in your app is easy, but the hard part of using microservices is the networking. How do you actually know if you're sending what you think you are? Why does this request fail in my app, but not when I use curl? Is this service very slow or is it up at all? This talk will help demystify some common problems you might experience while building out your collection of microservices. Once you can find the issue, it becomes way easier to fix.

Actor Patterns and NATS - Boulder Meetup

Apcera

The Zen of High Performance Messaging with NATS

Apcera

The Zen of High Performance Messaging with NATS Waldemar Quevedo Salinas, Senior Software Engineer NATS is an open source, high performant messaging system with a design oriented towards both being as simple and reliable as possible without at the same time trading off scalability. Originally written in Ruby, and then rewritten in Go, a NATS server can nowadays push over 11M messages per second. In this talk, we will cover how following simplicity as the main design constraint as well as focusing on a limited built-in feature set, resulted in a system which is easy to operate and reason about, making up for an attractive choice for when building many types of distributed systems where low latency and high availability are very important. You can learn more about NATS at http://www.nats.io

Micro on NATS - Microservices with Messaging

Apcera

NATS - A new nervous system for distributed cloud platforms

Derek Collison

NATS is an open-source, high-performance, lightweight cloud messaging system. NATS was created by Derek Collison, Founder/CEO of Apcera who has spent 20+ years designing, building, and using publish-subscribe messaging systems. Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems.

Policy-based Cloud Storage: Persisting Data in a Multi-Site, Multi-Cloud World

Apcera

Apcera's Earl Ruby discusses the role of policy in cloud storage, microservices and container management at SF Microservices meetup. As organizations are building storage and infrastructure at scale, policy supports provisioning, security, performance and business logic. What problems are we trying to solve? Define “Scale”... Cloud software has to to "play nice with others" Policy for Provisioning, Security, Performance, and Business Logic You can learn more about The Trusted Cloud Platform at: https://www.apcera.com/

Kubernetes, The Day After

Apcera

High Performance Systems in Go - GopherCon 2014

Derek Collison

Migrate Your Business to the Cloud

cloudbakers

Cloudlytics Reporting: Analyze Amazon CloudFront, S3 & ELB Logs - Part 2

Blazeclan Technologies Private Limited

Levent Nart Dinamikler 2016

Dinamikler

Metin Örnek Dinamikler 2016

Dinamikler

Cloudbakers' Presentation at Jobg8's Job Board Summit 2013

cloudbakers

Overview of AWS Services for Media Content

Blazeclan Technologies Private Limited

Viewers also liked (20)

NATS: A Central Nervous System for IoT Messaging - Larry McQueary

Nats in action a real time microservices architecture handled by nats

Implementing Microservices with NATS

Simple and Scalable Microservices: Using NATS with Docker Compose and Swarm

NATS for Modern Messaging and Microservices

The Current Messaging Landscape: RabbitMQ, ZeroMQ, nsq, Kafka

Debugging Network Issues

Actor Patterns and NATS - Boulder Meetup

The Zen of High Performance Messaging with NATS

Micro on NATS - Microservices with Messaging

NATS - A new nervous system for distributed cloud platforms

Policy-based Cloud Storage: Persisting Data in a Multi-Site, Multi-Cloud World

Kubernetes, The Day After

High Performance Systems in Go - GopherCon 2014

Migrate Your Business to the Cloud

Cloudlytics Reporting: Analyze Amazon CloudFront, S3 & ELB Logs - Part 2

Levent Nart Dinamikler 2016

Metin Örnek Dinamikler 2016

Cloudbakers' Presentation at Jobg8's Job Board Summit 2013

Overview of AWS Services for Media Content

Similar to Patterns for Asynchronous Microservices with NATS

Patterns for Asynchronous Microservices with NATSRaül Pérez

NATS & IoTRaül Pérez

Micro Manchester Meetup: "The Seven (More) Deadly Sins of Microservices"

Daniel Bryant

There is trouble brewing in the land of microservices – today’s shiny technology is tomorrow’s legacy, and there is concern that we will all be dealing with spaghetti services in 2018… It is often a sign of an architectural approach’s maturity that in addition to the emergence of well established principles and practices, that anti-patterns also begin to be identified and classified. In this talk we introduce the 2016 edition of the seven deadly sins that if left unchecked could easily ruin your next microservices project…

Getting to grips with a Service Level Agreement and how SLA-Ready can help

SLA-Ready Network

apidays LIVE Hong Kong - Let's get started development of API client library ...

apidays

OSCON EU 2016 "Seven (More) Deadly Sins of Microservices"

Daniel Bryant

All is not completely rosy in microservice-land. It’s often a sign of an architectural approach’s maturity that anti-patterns begin to be identified and classified alongside well-established principles and practices. Daniel Bryant introduces seven deadly sins from real projects, which left unchecked could easily ruin your next microservices project. Daniel offers an updated tour for 2016 of some of the nastiest anti-patterns in microservices from several real-world projects he’s encountered as a consultant, providing a series of anti-pattern “smells” you can sniff out and exploring the tools and techniques you need to avoid or mitigate the potential damage. Topics include: Pride: Selfishly building the wrong thing, such as the "Inter-Domain-Enterprise-Application-Service-Bus” or a fully bespoke infrastructure platform Envy: Introducing inappropriate intimacy within services by creating a shared “canonical” domain model Wrath: Failing to deal with the inevitable bad things that occur within a distributed system Sloth: Composing services in a lazy fashion, which ultimately leads to the creation of a "distributed monolith” Lust: Embracing the latest and greatest technology without evaluating the operational impact incurred by these choices

RIPE Atlas

RIPE NCC

NET53494 Extensions in the Age of S/4HANA

Christian Lechner

SAP S/4HANA in its broadest sense (including SAP Cloud Platform) not only leads to a new programming model, but also to new options and variants when it comes to extensibility and add-on development. Join this session to hear thoughts about the different options and their consequences for customers and partners. We explore the topics of in-app extensibility and side-by-side extensibility as well as the options for bringing your solution to the cloud.

Tecnologia rest em python

Allex Lima

A Taste of Open Fabrics Interfaces

seanhefty

F-interop Meetup

Digital Catapult

AusNOG 2011 - Residential IPv6 CPE - What Not to Do and Other Observations

Mark Smith

Patna_Meetup_MQ

Om Prakash

Agile at DeLorme

agilemaine

Operations Delivery Business Value

Sonatype

Dave Mangot, Solarwinds Cloud Companies In this session, we will looks at the ways that Operations can deliver business value. Long ago Operations was a cost center, now it's a strategic differentiator. We used to think our job was to work with technology, now we realize it's to deliver value to the business. We'll examine some principles that are signs of a mature DevOps practice and use examples from the Librato move from EC2 Classic to VPC and the next generation platform we built in the process to demonstrate how adherence to those principles allow us to deliver value to the business faster and more reliably than ever before.

Micro services may not be the best idea

Samuel ROZE

COBIT as Framework for Leading IT-enabled Change and Transformation

BoonNam Goh

ATLRUG Announcements/Upgrade News - August 2016

jasnow

Are you SLA-Ready?

SLA-Ready Network

Performance is not an Option - gRPC and Cassandra

Dave Bechberger

Similar to Patterns for Asynchronous Microservices with NATS (20)

Patterns for Asynchronous Microservices with NATS

NATS & IoT

Micro Manchester Meetup: "The Seven (More) Deadly Sins of Microservices"

Getting to grips with a Service Level Agreement and how SLA-Ready can help

apidays LIVE Hong Kong - Let's get started development of API client library ...

OSCON EU 2016 "Seven (More) Deadly Sins of Microservices"

RIPE Atlas

NET53494 Extensions in the Age of S/4HANA

Tecnologia rest em python

A Taste of Open Fabrics Interfaces

F-interop Meetup

AusNOG 2011 - Residential IPv6 CPE - What Not to Do and Other Observations

Patna_Meetup_MQ

Agile at DeLorme

Operations Delivery Business Value

Micro services may not be the best idea

COBIT as Framework for Leading IT-enabled Change and Transformation

ATLRUG Announcements/Upgrade News - August 2016

Are you SLA-Ready?

Performance is not an Option - gRPC and Cassandra

More from Apcera

Gopher fest 2017: Adding Context To NATS

Apcera

The Context package has been a popular topic in the Golang community for sometime and as of the Go 1.7 release, it has become a standard Go library. It carries a variety of details across API boundaries and between processes. NATS is an open-source, high-performance, lightweight cloud native messaging system. Many NATS users working in Go have been using Context alongside NATS, but there has not been an officially-supported Context-NATS integration – that is, until now. This talk will discuss what Context is, what observations and lessons Waldemar and his team have learned integrating Context and NATS, and how you use the two together. He'll also provide a quick demo to show the integration. About the Speaker: Waldemar Quevedo is a Senior Software Engineer at Apcera, where he develops the Apcera Trusted Platform and is part of the NATS team. Previously, he formed part of the PaaS team at Rakuten in Tokyo which was one of the early adopters of CloudFoundry for production usage where he experienced operating NATS for the first time, and became a fan of its simplicity. You can learn more about NATS at http://www.nats.io

How Clarifai uses NATS and Kubernetes for Machine Learning

Apcera

Clarifai (www.clarifai.com) is a machine learning company which aims to make artificial intelligence accessible to the entire world. Their platform allows users to tap into powerful machine learning algorithms while abstracting away the technical minutiae of how the algorithms work and the infrastructure scaling problems of building AI applications from scratch. Clarifai has moved to a highly available Kubernetes (www.kubernetes.io) based architecture, which also required a simple, scalable messaging layer. NATS (www.nats.io) was selected by the Clarifai team for a variety of reasons. The video of the talk that accompanies these slides is available at: https://www.youtube.com/watch?v=fJ20plWSBzw&feature=youtu.be

Modernizing IT in the Platform Era

Apcera

IT Modernization Doesn’t Mean You Leave Your Legacy Apps Behind

Apcera

As enterprises adopt cloud infrastructure and modern architectures, they can’t turn their back on existing applications. The challenge is that legacy applications are expensive-to-maintain and inflexible due to infrastructure requirements and dependencies. Explore new approaches to application modernization with Mark Thiele, Chief Strategy Officer at Apcera, and Ralph Loura, CTO and Rodan + Fields, to learn how to protect current IT investments and establish a secure path to the cloud.

NATS Connector Framework - Boulder Meetup

Apcera

Securing the Cloud Native Stack

Apcera

How to Migrate to Cloud with Complete Confidence and Trust

Apcera

KURMA - A Containerized Container Platform - KubeCon 2016

Apcera

Kurma is a container runtime that is based on the container instrumentation built into the Apcera Platform. Kurma, and its accompanied “KurmaOS” is our vision of a lightweight, fully containerized operating system. This presentation will cover Apcera’s journey in its container instrumentation. Beginning with the pre-Docker landscape, how it grew over the course of 3+ years, and the “next-gen” adaption of it, where the base container instrumentation has been adapted to stand on its own, and growing it to be used beyond just Apcera’s own usage. Kurma incorporates a lot of lessons learned with both development and operations of a container platform, including building modular vs monolith, extensibility being built in vs built on, and managing a cluster of hosts and containers. We’ll also cover our experiences with introducing it to Kubernetes as another first class runtime provider. Taking how Kurma works and have it work with Kubernetes, and how we’d like to see Kubernetes grow in some of the areas we see Kurma growing.

Integration Patterns and Anti-Patterns for Microservices Architectures

Apcera

NATS: Control Flow for Distributed Systems

Apcera

Integration Patterns for Microservices Architectures

Apcera

One of the fundamental principals of microservices is the idea of lightweight, composable loosely coupled applications that can either talk through some type of service endpoint, through some protocol like HTTP or through pipes. A lightweight messaging system such as NATS is a better way for microservices to talk to each other and integrate disparate systems outside the microservice or architecture. You can learn more about NATS at http://www.nats.io

Nats meetup sf 20150826

Apcera

NATS was created by Derek Collison, founder and CEO of Apcera, who has spent 20+ years designing, building, and using publish-subscribe messaging systems. Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. Learn how end users are building modern, reliable and scalable cloud and distributed systems with NATS. Talk given by David Williams, Principal, Williams & Garcia You can learn more about NATS at http://www.nats.io

Microservices: Notes From The Field

Apcera

Docker + App Container = ocp

Apcera

Apcera: Agility and Security in Docker Delivery

Apcera

Delivering Policy & Trust to the Hybrid Cloud

Apcera

More from Apcera (16)

Gopher fest 2017: Adding Context To NATS

How Clarifai uses NATS and Kubernetes for Machine Learning

Modernizing IT in the Platform Era

IT Modernization Doesn’t Mean You Leave Your Legacy Apps Behind

NATS Connector Framework - Boulder Meetup

Securing the Cloud Native Stack

How to Migrate to Cloud with Complete Confidence and Trust

KURMA - A Containerized Container Platform - KubeCon 2016

Integration Patterns and Anti-Patterns for Microservices Architectures

NATS: Control Flow for Distributed Systems

Integration Patterns for Microservices Architectures

Nats meetup sf 20150826

Microservices: Notes From The Field

Docker + App Container = ocp

Apcera: Agility and Security in Docker Delivery

Delivering Policy & Trust to the Hybrid Cloud

Recently uploaded

Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...

UiPathCommunity

💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™: See how to accelerate model training and optimize model performance with active learning Learn about the latest enhancements to out-of-the-box document processing – with little to no training required Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath. Speakers: 👨‍🏫 Andras Palfi, Senior Product Manager, UiPath 👩‍🏫 Lenka Dulovicova, Product Program Manager, UiPath

Knowledge engineering: from people to machines and back

Elena Simperl

GenAISummit 2024 May 28 Sri Ambati Keynote: AGI Belongs to The Community in O...

Sri Ambati

FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf

FIDO Alliance

Neuro-symbolic is not enough, we need neuro-*semantic*

Frank van Harmelen

Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”. All of this illustrated with link prediction over knowledge graphs, but the argument is general.

Essentials of Automations: Optimizing FME Workflows with Parameters

Safe Software

Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place. Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects. Here’s what you’ll gain: - Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows. - Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy. - Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency. - Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity. We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic. Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.

The Art of the Pitch: WordPress Relationships and Sales

Laura Byrne

Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes? All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.

FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf

FIDO Alliance

Bits & Pixels using AI for Good.........

Alison B. Lowndes

When stars align: studies in data quality, knowledge graphs, and machine lear...

Elena Simperl

Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...

Jeffrey Haguewood

Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows. We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases. This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams. Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.

GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...

James Anderson

Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management. The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM). Speakers: Bob Boule Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle. Gopinath Rebala Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.

The Future of Platform Engineering

Jemma Hussein Allen

GraphRAG is All You need? LLM & Knowledge Graph

Guy Korland

Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs. 1. Unifying Large Language Models and Knowledge Graphs: A Roadmap. https://arxiv.org/abs/2306.08302 2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs: https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/

LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...

DanBrown980551

Do you want to learn how to model and simulate an electrical network from scratch in under an hour? Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)! During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook. PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides: - A fully editable and extendable library for grid component modelling; - Visualization tools to display your network; - Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses; The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well. What you will learn during the webinar: - For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills; - For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.

PCI PIN Basics Webinar from the Controlcase Team

ControlCase

Assuring Contact Center Experiences for Your Customers With ThousandEyes

ThousandEyes

Accelerate your Kubernetes clusters with Varnish Caching

Thijs Feryn

Connector Corner: Automate dynamic content and events by pushing a button

DianaGray10

Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to: Create a campaign using Mailchimp with merge tags/fields Send an interactive Slack channel message (using buttons) Have the message received by managers and peers along with a test email for review But there’s more: In a second workflow supporting the same use case, you’ll see: Your campaign sent to target colleagues for approval If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team But—if the “Reject” button is pushed, colleagues will be alerted via Slack message Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors. And... Speakers: Akshay Agnihotri, Product Manager Charlie Greenberg, Host

From Siloed Products to Connected Ecosystem: Building a Sustainable and Scala...

Product School

Recently uploaded (20)

Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...

Knowledge engineering: from people to machines and back

GenAISummit 2024 May 28 Sri Ambati Keynote: AGI Belongs to The Community in O...

FIDO Alliance Osaka Seminar: Passkeys and the Road Ahead.pdf

Neuro-symbolic is not enough, we need neuro-*semantic*

Essentials of Automations: Optimizing FME Workflows with Parameters

The Art of the Pitch: WordPress Relationships and Sales

FIDO Alliance Osaka Seminar: Passkeys at Amazon.pdf

Bits & Pixels using AI for Good.........

When stars align: studies in data quality, knowledge graphs, and machine lear...

Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...

GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...

The Future of Platform Engineering

GraphRAG is All You need? LLM & Knowledge Graph

LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...

PCI PIN Basics Webinar from the Controlcase Team

Assuring Contact Center Experiences for Your Customers With ThousandEyes

Accelerate your Kubernetes clusters with Varnish Caching

Connector Corner: Automate dynamic content and events by pushing a button

From Siloed Products to Connected Ecosystem: Building a Sustainable and Scala...

Patterns for Asynchronous Microservices with NATS

1. Patterns for Asynchronous Microservices Raül Pérez - @repejota NATS London - 10/05/2016

2. Who am I? Raül Pérez Lead Software Engineer at R3 Labs Ltd. Twitter: @repejota Github: https://github.com/repejota Email: repejota@gmail.com 2 Raül Pérez - @repejota NATS London - 10/05/2016

3. Who am I? Raül Pérez Lead Software Engineer at R3 Labs Ltd. Twitter: @repejota Github: https://github.com/repejota Email: repejota@gmail.com 3 ● Almost 4 years working on devops & distributed projects. Raül Pérez - @repejota NATS London - 10/05/2016

4. Who am I? Raül Pérez Lead Software Engineer at R3 Labs Ltd. Twitter: @repejota Github: https://github.com/repejota Email: repejota@gmail.com 4 ● Almost 4 years working on devops & distributed projects. ● Still more a dev than op dude. Raül Pérez - @repejota NATS London - 10/05/2016

5. Who am I? Raül Pérez Lead Software Engineer at R3 Labs Ltd. Twitter: @repejota Github: https://github.com/repejota Email: repejota@gmail.com 5 ● Almost 4 years working on devops & distributed projects. ● Still more a dev than op dude. ● Proud to be a Gopher after a looong PHP/Ruby/Python/Node.js past experience. :P Raül Pérez - @repejota NATS London - 10/05/2016

6. Who am I? Raül Pérez Lead Software Engineer at R3 Labs Ltd. Twitter: @repejota Github: https://github.com/repejota Email: repejota@gmail.com 6 ● Almost 4 years working on devops & distributed projects. ● Still more a dev than op dude. ● Proud to be a Gopher after a looong PHP/Ruby/Python/Node.js past experience. :P ● Based in Barcelona.Raül Pérez - @repejota NATS London - 10/05/2016

7. Who am I? Raül Pérez Lead Software Engineer at R3 Labs Ltd. Twitter: @repejota Github: https://github.com/repejota Email: repejota@gmail.com 7 ● Almost 4 years working on devops & distributed projects. ● Still more a dev than op dude. ● Proud to be a Gopher after a looong PHP/Ruby/Python/Node.js past experience. :P ● Based in Barcelona.Raül Pérez - @repejota NATS London - 10/05/2016

8. Summary 8 Raül Pérez - @repejota NATS London - 10/05/2016 ● Why microservices? ● Synchronous vs. Asynchronous communication. ● Pattern: Broker approach & NATS ● Pattern: Autonomy of services vs. Coordination between services.

9. Why microservices? 9 Raül Pérez - @repejota NATS London - 10/05/2016 ● Loosely coupled components. ● Specific responsibility, each one delivers a capability. ● Designed to be defensive against failures.

10. Why microservices? 10 Raül Pérez - @repejota NATS London - 10/05/2016 ● Loosely coupled components. ● Specific responsibility, each one delivers a capability. ● Designed to be defensive against failures. ● Designed around business needs. ● Decentralised governance. ● Decentralised data management. ● Connected through a common interface.

11. Pattern: Sync vs. Async communication. 11 Raül Pérez - @repejota NATS London - 10/05/2016 ● The most common interface to communicate is HTTP. ● But HTTP is “mostly” synchronous. ● Once the number of services grow, HTTP is sometimes not enough.

12. Pattern: Sync vs. Async communication. 12 Raül Pérez - @repejota NATS London - 10/05/2016 ● The most common interface to communicate is HTTP. ● But HTTP is “mostly” synchronous. ● Once the number of services grow, HTTP is not enough. ● It also has a complex error management.

13. Pattern: Sync vs. Async communication. 13 Raül Pérez - @repejota NATS London - 10/05/2016 ● Synchronous communication is simple but…. ○ Drawback: Suffers from latency on each connection. ● Asynchronous communication is faster but… ○ Drawback: Increases the complexity. ○ Drawback: Snowball effect, difficult to manage and orchestrate. So, Is there a better communication interface?

14. Pattern: Sync vs. Async communication. 14 Raül Pérez - @repejota NATS London - 10/05/2016 ● Pattern: Use a broker to orchestrate your communication needs. ○ AMPQ, RabbitMQ, NSQ, etc …. ○ NATS :) ● A broker is flexible, allows you to use: ○ Work queues. ○ Publish/Subscribe. ○ Request/Response. ○ Message routing. ○ etc...

15. Pattern: Broker approach & NATS 15 Raül Pérez - @repejota NATS London - 10/05/2016 ● Loosely coupled clients and servers. ● Multiple patterns: Publish/Subscribe, Request/Response. ● Easy to scale.

16. Pattern: Broker approach & NATS 16 Raül Pérez - @repejota NATS London - 10/05/2016 ● Loosely coupled clients and servers. ● Multiple patterns: Publish/Subscribe, Request/Response. ● Easy to scale. ● NATS is fast!

17. Pattern: Broker approach & NATS 17 Raül Pérez - @repejota NATS London - 10/05/2016 ● Loosely coupled clients and servers. ● Multiple patterns: Publish/Subscribe, Request/Response. ● Easy to scale. ● NATS is fast! ● Just a message system, no assumptions, no extra features. Easy to deploy, easy to use.

18. Pattern: Broker approach & NATS 18 Raül Pérez - @repejota NATS London - 10/05/2016 ● Loosely coupled clients and servers. ● Multiple patterns: Publish/Subscribe, Request/Response. ● Easy to scale. ● NATS is fast! ● Just a message system, no assumptions, no extra features. Easy to deploy, easy to use. ● It is also secure: SSL, password ...

19. Pattern: Broker approach & NATS 19 Raül Pérez - @repejota NATS London - 10/05/2016 ● Loosely coupled clients and servers. ● Multiple patterns: Publish/Subscribe, Request/Response. ● Easy to scale. ● NATS is fast! ● Just a message system, no assumptions, no extra features. Easy to deploy, easy to use. ● It is also secure: SSL, password ... ● Simple protocol, it is just text.

20. Pattern: Autonomy vs. Coordination. 20 Raül Pérez - @repejota NATS London - 10/05/2016 ● Make your services autonomous. ● Avoid coordination between different services. ● The minimal coordination the more optimal autonomy. ● Increased autonomy gives it freedom to evolve.

21. Pattern: Autonomy vs. Coordination. 21 Raül Pérez - @repejota NATS London - 10/05/2016 ● Make your services autonomous. ● Avoid coordination between different services. ● The minimal coordination the more optimal autonomy. ● Increased autonomy gives it freedom to evolve. ● Your services delivers “capabilities”

22. Pattern: Autonomy vs. Coordination. 22 Raül Pérez - @repejota NATS London - 10/05/2016 ● Make your services autonomous. ● Avoid coordination between different services. ● The minimal coordination the more optimal autonomy. ● Increased autonomy gives it freedom to evolve. ● Your services delivers “capabilities” ● What is a capability? A complete business capability is a process that can be finished consecutively without interruptions or excursions to other services.

23. Resources ● http://microservices.io ● https://en.wikipedia.org/wiki/Cloud_computing ● http://nats.io 23 ● http://repejota.com ● http://r3labs.io ● http://ernest.io ● http://apcera.comRaül Pérez - @repejota NATS London - 10/05/2016

24. Questions? Raül Pérez - @repejota NATS London - 10/05/2016

25. Thank you! 25Raül Pérez - @repejota NATS London - 10/05/2016

Patterns for Asynchronous Microservices with NATS

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Viewers also liked

Viewers also liked (20)

Similar to Patterns for Asynchronous Microservices with NATS

Similar to Patterns for Asynchronous Microservices with NATS (20)

More from Apcera

More from Apcera (16)

Recently uploaded

Recently uploaded (20)

Patterns for Asynchronous Microservices with NATS