<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Quarkus on akos.ma</title><link>https://akos.ma/tags/quarkus/</link><description>Recent content in Quarkus on akos.ma</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 19 May 2023 00:00:00 +0200</lastBuildDate><atom:link href="https://akos.ma/tags/quarkus/index.xml" rel="self" type="application/rss+xml"/><item><title>Back to Monoliths</title><link>https://akos.ma/blog/back-to-monoliths/</link><pubDate>Fri, 19 May 2023 00:00:00 +0200</pubDate><guid>https://akos.ma/blog/back-to-monoliths/</guid><description>So Amazon Prime Video (of all people!) published a blog post about how they&amp;rsquo;re returning to monoliths, relayed by DHH, generating lots of noise, to the point that even Dr. Werner Vogels himself, CTO at Amazon, had to pour some thoughts about the subject.</description></item><item><title>Microservices or Not? Your Team Has Already Decided</title><link>https://akos.ma/blog/microservices-or-not-your-team-has-already-decided/</link><pubDate>Fri, 05 Aug 2022 00:00:00 +0200</pubDate><guid>https://akos.ma/blog/microservices-or-not-your-team-has-already-decided/</guid><description>Let’s take a somewhat tangential approach to the subject of the Microservices architecture. Most discussions about it are centered around technological aspects; which language to choose, how to create the most RESTful services, which service mesh is the most performant, etc.</description></item><item><title>Fortune Apps</title><link>https://akos.ma/blog/fortune-apps/</link><pubDate>Fri, 20 May 2022 00:00:00 +0200</pubDate><guid>https://akos.ma/blog/fortune-apps/</guid><description>&lt;p&gt;As part of my work in &lt;a href="https://www.vshn.ch/"&gt;VSHN&lt;/a&gt;, I lately prepared a set of demo applications ready to be containerized and deployed in our new product &lt;a href="https://appuio.cloud/"&gt;APPUiO Cloud&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Lots of VSCode Extensions</title><link>https://akos.ma/blog/lots-of-vscode-extensions/</link><pubDate>Fri, 29 Oct 2021 00:00:00 +0200</pubDate><guid>https://akos.ma/blog/lots-of-vscode-extensions/</guid><description>&lt;p&gt;The recent &lt;a href="https://code.visualstudio.com/blogs/2021/10/20/vscode-dev"&gt;release&lt;/a&gt; by Microsoft of &lt;a href="https://vscode.dev/"&gt;vscode.dev&lt;/a&gt;, the online version of &lt;a href="https://code.visualstudio.com/"&gt;Visual Studio Code&lt;/a&gt;, made me think of all the different things I do with VSCode, including this blog. And of course, being productive in VSCode means, to a large extent, finding gems across a seemingly infinite number of extensions.&lt;/p&gt;</description></item><item><title>Visual J++</title><link>https://akos.ma/blog/visual-j/</link><pubDate>Fri, 12 Feb 2021 00:00:00 +0100</pubDate><guid>https://akos.ma/blog/visual-j/</guid><description>&lt;p&gt;Once upon a time, there was a programming environment made by Microsoft called &lt;a href="https://en.wikipedia.org/wiki/Visual_J%2B%2B"&gt;Visual J++&lt;/a&gt;. It was their attempt to do with Java what they had done with JScript before, and to be honest, it was quite cool. You could compile and run Java code on Windows with a very good IDE - this was 5 years before &lt;a href="https://www.jetbrains.com/lp/intellijidea-20-anniversary/"&gt;IntelliJ released IDEA&lt;/a&gt;! It generated much faster binaries than what the official Java compiler from Sun produced. Developers could access functionality inside of packages starting with the &lt;code&gt;microsoft.&lt;/code&gt; name, but that of course that kind of broke the whole point of Java which is to make cross-platform stuff that you only write once and then you run everywhere.&lt;/p&gt;</description></item></channel></rss>