<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nasim Salmany on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/nasim-salmany/</link><description>Articles written by Nasim Salmany on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Sep 2024 09:56:13 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/nasim-salmany/index.xml" rel="self" type="application/rss+xml"/><item><title>How to profile a performance issue using Spring Boot profiling tools</title><link>https://foojayio.github.io/website/today/how-to-profile-a-performance-issue-using-spring-boot-profiling-tools/</link><pubDate>Mon, 02 Sep 2024 09:56:13 +0000</pubDate><guid>https://foojayio.github.io/website/today/how-to-profile-a-performance-issue-using-spring-boot-profiling-tools/</guid><description>&lt;p&gt;&lt;strong&gt;In today&amp;rsquo;s fast-paced development environment, ensuring the performance and reliability of your services is critical. Imagine you are part of a team responsible for several services essential to both internal teams and external customers. These services are the backbone of various business operations, and any downtime or performance degradation can have significant repercussions.&lt;/strong&gt;{#c79c}&lt;/p&gt;
&lt;p&gt;Now, picture this scenario: your team has not yet implemented a robust monitoring and observability system. One day, you start receiving emails and messages from frustrated clients reporting that your service is down. Panic sets in as your team tries to figure out what went wrong. Without proper monitoring tools, finding the root cause of issues in production is challenging. Persistent downtime increases pressure, affecting business operations and customer satisfaction.{#acf3}&lt;/p&gt;</description></item></channel></rss>