<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Events on Micha Kops&#39; Tech Notes</title>
    <link>https://www.hascode.com/tags/events/</link>
    <description>Recent content in Events on Micha Kops&#39; Tech Notes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright © 2010 - 2025 Micha Kops. #e9d956c0c0154a221ad83c925346a8fa0e72f866</copyright>
    <lastBuildDate>Fri, 05 Sep 2025 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://www.hascode.com/tags/events/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Message-Driven Architecture Across Multiple Teams</title>
      <link>https://www.hascode.com/message-driven-architecture-across-multiple-teams/</link>
      <pubDate>Fri, 05 Sep 2025 00:00:00 +0200</pubDate>
      <guid>https://www.hascode.com/message-driven-architecture-across-multiple-teams/</guid>
      <description>&lt;div id=&#34;preamble&#34;&gt;
&lt;div class=&#34;sectionbody&#34;&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;Whenever I start planning a new message-driven architecture that spans several software teams, I quickly realize how many moving parts there are.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;To keep my head clear, I’ve put together a personal checklist of things I always try to cover.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;It’s not meant to be a formal rulebook, but more of a practical reminder of what usually makes the difference between smooth collaboration and endless headaches.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;imageblock&#34;&gt;
&lt;div class=&#34;content&#34;&gt;
&lt;img src=&#34;message-driven-architecture-conver.png&#34; alt=&#34;message driven architecture conver&#34;/&gt;
&lt;/div&gt;
&lt;div class=&#34;title&#34;&gt;Figure 1. Message Driven Architecture Article Cover Image&lt;/div&gt;</description>
    </item>
    <item>
      <title>Snippet: Java Mission Control (JMC) and Flight Recorder (JFR)</title>
      <link>https://www.hascode.com/snippet-java-mission-control-jmc-and-flight-recorder-jfr/</link>
      <pubDate>Wed, 11 Oct 2017 00:00:00 +0200</pubDate>
      <guid>https://www.hascode.com/snippet-java-mission-control-jmc-and-flight-recorder-jfr/</guid>
      <description>&lt;div id=&#34;preamble&#34;&gt;
&lt;div class=&#34;sectionbody&#34;&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;The Java Mission Control and the Java Flight Recorder allow us to capture run-time information from our Java applications without much overhead and aggregate profiling information.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;I have written down the commands that I’m using the most when profiling a Java application with this tool chain in the following article.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;imageblock&#34;&gt;
&lt;div class=&#34;content&#34;&gt;
&lt;img src=&#34;java-mission-control-reports-1024x629.png&#34; alt=&#34;java mission control reports 1024x629&#34;/&gt;
&lt;/div&gt;
&lt;div class=&#34;title&#34;&gt;Figure 1. Java Mission Control - Report&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class=&#34;sect1&#34;&gt;
&lt;h2 id=&#34;_running_java_mission_control_jmc&#34;&gt;Running Java Mission Control (JMC)&lt;/h2&gt;
&lt;div class=&#34;sectionbody&#34;&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;We may start the JMC user interface shown above using the &lt;em&gt;jmc&lt;/em&gt; command that is shipped with Oracle’s JRockit or Java (since Java 7 update 40).&lt;/p&gt;
&lt;/div&gt;</description>
    </item>
  </channel>
</rss>
