<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud Native Architecture on Dhaval Shah</title><link>https://www.dhaval-shah.com/categories/cloud-native-architecture/</link><description>Recent content in Cloud Native Architecture on Dhaval Shah</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Sun, 12 Sep 2021 14:53:50 +0000</lastBuildDate><atom:link href="https://www.dhaval-shah.com/categories/cloud-native-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Performance Comparison - RSocket Vs Webflux</title><link>https://www.dhaval-shah.com/performance-comparison-rsocket-webflux/</link><pubDate>Sun, 12 Sep 2021 14:53:50 +0000</pubDate><guid>https://www.dhaval-shah.com/performance-comparison-rsocket-webflux/</guid><description>Background In one of my previous post we saw tangible advantages (w.r.t throughput, latency and resource utilization) of refactoring existing Microservice application from imperative to reactive constructs.
So an obvious question that comes to an inquisitive mind -
Can we apply Reactive principles to the underlying communication layer
Answer to above question is - Yes and RSocket is the way to go
What is RSocket RSocket is a binary protocol that can perform bi-directional communication via TCP.</description></item><item><title>Performant and optimal Spring WebClient</title><link>https://www.dhaval-shah.com/performant-and-optimal-spring-webclient/</link><pubDate>Mon, 15 Mar 2021 14:53:50 +0000</pubDate><guid>https://www.dhaval-shah.com/performant-and-optimal-spring-webclient/</guid><description>Background In my previous post I tried demonstrating how to implement an optimal and performant REST client using RestTemplate
In this article I will be demonstrating similar stuff but by using WebClient. But before we get started, lets try rationalizing
Why yet another REST client i.e. WebClient
IMO there are 2 compelling reasons -
Maintenance mode of RestTemplate NOTE: As of 5.0 this class is in maintenance mode, with only minor requests for changes and bugs to be accepted going forward.</description></item><item><title>REST client with desired NFRs using Spring RestTemplate</title><link>https://www.dhaval-shah.com/rest-client-with-desired-nfrs-using-springs-resttemplate/</link><pubDate>Tue, 19 May 2020 14:53:50 +0000</pubDate><guid>https://www.dhaval-shah.com/rest-client-with-desired-nfrs-using-springs-resttemplate/</guid><description>Background In this contemporary world of enterprise application development, Microservice Architecture has become defacto paradigm. With this new paradigm, an application is going to have myriad set of independent and autonomous (micro)services which will be calling each other. One of the fundamental characteristics of Microservice Architecture is
Services must be easily consumable
Hence most of the services implemented will be exposing REST APIs. In order to consume these REST APIs, each Microservice application will have to implement a REST client.</description></item><item><title>Chaos Engineering – Demonstration with working example (Part-2)</title><link>https://www.dhaval-shah.com/chaos-engineering-demonstration-with-working-example/</link><pubDate>Fri, 02 Aug 2019 17:21:13 +0000</pubDate><guid>https://www.dhaval-shah.com/chaos-engineering-demonstration-with-working-example/</guid><description>Background From first part of blog we gathered understanding about basics of Chaos Engineering. Now we will further deep dive to understand how to perform Chaos Engineering with a working example - which to me is going to be quite interesting. First lets start with understanding basics of working example which will be used to demonstrate following-
How to perform chaos engineering within an application How to monitor the behavior of the system What to monitor whilst executing experiments on our system Bird's eye view of demo example</description></item><item><title>Chaos Engineering – A quick primer</title><link>https://www.dhaval-shah.com/chaos-engineering-a-quick-primer/</link><pubDate>Sun, 30 Jun 2019 18:13:30 +0000</pubDate><guid>https://www.dhaval-shah.com/chaos-engineering-a-quick-primer/</guid><description>Human body is vulnerable to lot of diseases. So in order to protect human beings from diseases vaccines have been invented. Vaccines mainly work due to process called 'Hormesis', by which system or organism adapts to harm in order to become stronger. Just as our body is susceptible to diseases and germs, so do our systems in software world. Hence vaccines and vaccination can be considered as an apt analogy for understanding Chaos Engineering.</description></item><item><title>Monitoring Spring Boot application using Actuator, Micrometer, Prometheus and Grafana</title><link>https://www.dhaval-shah.com/monitoring-spring-boot-application/</link><pubDate>Fri, 02 Nov 2018 10:37:46 +0000</pubDate><guid>https://www.dhaval-shah.com/monitoring-spring-boot-application/</guid><description>Spring Boot helps developers to implement enterprise grade applications which can be pushed to production in no time. Once application gets into production and if we strongly believe in vedic philosophy of Karma :), we are bound to experience Murphy's Law.
Whatever can go wrong, will go wrong
Considering nature of Distributed Architecture, Observability and Monitoring of application and infrastructure is of paramount importance. Thanks to the Spring Boot team, who has shipped Spring Boot Actuator from the very first release.</description></item><item><title>Understanding Cloud Native Architecture with an example</title><link>https://www.dhaval-shah.com/understanding-cloud-native-architecture-with-an-example/</link><pubDate>Thu, 16 Mar 2017 05:20:05 +0000</pubDate><guid>https://www.dhaval-shah.com/understanding-cloud-native-architecture-with-an-example/</guid><description>Whenever the buzz word 'Cloud Native Architecture' gets to our ears, first thing that comes to our mind is - It sounds too jazzy and latest and would have something to do with technology since it has a word called 'Architecture' within it :). Because of this it creates a perception in the minds of lot of people that 'Cloud Native Architecture' is just about TECHNOLOGY. Unfortunately, this is one of the most common misconception that prevails currently in the industry.</description></item></channel></rss>