<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Arcentry Blog on Arcentry — Interactive cloud diagrams</title><link>https://arcentry.com/blog/</link><description>Recent content in Arcentry Blog on Arcentry — Interactive cloud diagrams</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://arcentry.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>A Simple Guide to Europe's Complicated Cloud Provider Landscape</title><link>https://arcentry.com/blog/a-simple-guide-to-europes-complicated-cloud-provider-landscape/</link><pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/a-simple-guide-to-europes-complicated-cloud-provider-landscape/</guid><description>&lt;p&gt;&lt;embed-frame id="9dc517f4-2ecb-45c0-8c2c-8c90c5aa5006"&gt;&lt;/embed-frame&gt;&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re looking to run a large-scale compute project in the US, you&amp;rsquo;re spoiled for choice. There&amp;rsquo;s a wide range of capable cloud offerings, from &lt;a href="https://www.ibm.com/" target="_blank" rel="noopener noreferrer"&gt;IBM&lt;/a&gt; and &lt;a href="https://www.oracle.com/" target="_blank" rel="noopener noreferrer"&gt;Oracle&lt;/a&gt; to &lt;a href="https://www.cloudflare.com/" target="_blank" rel="noopener noreferrer"&gt;Cloudflare&lt;/a&gt; and &lt;a href="https://www.digitalocean.com/" target="_blank" rel="noopener noreferrer"&gt;DigitalOcean&lt;/a&gt;. But chances are, you&amp;rsquo;ll end up with one of the big three: &lt;a href="https://www.microsoft.com/" target="_blank" rel="noopener noreferrer"&gt;Microsoft&lt;/a&gt;&amp;rsquo;s &lt;a href="https://azure.microsoft.com/" target="_blank" rel="noopener noreferrer"&gt;Azure&lt;/a&gt;, &lt;a href="https://cloud.google.com/" target="_blank" rel="noopener noreferrer"&gt;Google Cloud&lt;/a&gt;, or &lt;a href="https://aws.amazon.com/" target="_blank" rel="noopener noreferrer"&gt;Amazon Web Services&lt;/a&gt; (&lt;a href="https://aws.amazon.com/" target="_blank" rel="noopener noreferrer"&gt;AWS&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;These platforms support massive scale, offer an incredible range of products and services, and provide straightforward setup and super-granular, usage-based billing.&lt;/p&gt;</description></item><item><title>Isometric Mermaid Diagrams with Arcentry</title><link>https://arcentry.com/blog/isometric-mermaid-diagrams-with-arcentry/</link><pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/isometric-mermaid-diagrams-with-arcentry/</guid><description>&lt;p&gt;&lt;embed-frame id="0094f2a1-1106-4386-9a33-91b5cd49642b"&gt;&lt;/embed-frame&gt;&lt;/p&gt;
&lt;p&gt;Have you ever looked at a thing and thought, “This is nice&amp;hellip; but could it be code?” Probably. There’s infrastructure as code. There’s &lt;a href="https://www.openpolicyagent.org"&gt;policy as code&lt;/a&gt;. There’s even &lt;a href="https://sonic-pi.net/"&gt;music as code&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;So, of course, there’s also diagrams as code. We sort of knew that back in 2018, when we created the &lt;a href="https://arcentry.com/api-docs/create-diagram/"&gt;Infrastructure Description Format&lt;/a&gt;: a way to describe the visual representation of compute infrastructure as code.&lt;/p&gt;
&lt;p&gt;There were only two problems.&lt;/p&gt;
&lt;p&gt;For one, the name. IDF seemed harmless enough in 2018. Today, those three letters can set off flags in some AI systems, leading to reviews for illicit activity. Not quite what we had in mind when we asked for a database and a load balancer.&lt;/p&gt;</description></item><item><title>Arcentry is back - and better than ever.</title><link>https://arcentry.com/blog/arcentry-is-back-and-better-than-ever/</link><pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/arcentry-is-back-and-better-than-ever/</guid><description>&lt;p&gt;&lt;img src="./overview-diagram.png" alt="AWS and Custom Infrastructure" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;Six years ago, I wrote a somewhat heartfelt blog post called &lt;em&gt;Discontinuing Arcentry&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;In it, I talked about walking my dog (a very fluffy Samoyed) until she didn’t want to walk anymore, while trying to decide whether I should sell Arcentry.&lt;/p&gt;
&lt;p&gt;In the end, I did.&lt;/p&gt;
&lt;p&gt;Five years later, I somehow managed to get it back. How exactly that happened is a story for another time.&lt;/p&gt;</description></item><item><title>Service Mesh VS API Gateway VS Message Queue - when to use what?</title><link>https://arcentry.com/blog/api-gateway-vs-service-mesh-vs-message-queue/</link><pubDate>Fri, 01 Mar 2019 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/api-gateway-vs-service-mesh-vs-message-queue/</guid><description>&lt;p&gt;&lt;img src="./title.png" alt="Flog of birds" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s skip the pitch for microservices - you already know what they are and why they make sense. In fact, few topics have received as much coverage in recent years as the unsurprising fact that breaking down a big thing into many small ones can make it easier to handle.&lt;/p&gt;
&lt;p&gt;The trouble is: once we&amp;rsquo;ve shattered our monolith, how do we put it back together into a larger system that still makes sense? Despite what Istio, Kong or Kafka enthusiasts will tell you, there&amp;rsquo;s more than one answer to this question and different solutions are differently suited for different needs.&lt;/p&gt;</description></item><item><title>Talking about tech is so hard, its a wonder we can do it at all</title><link>https://arcentry.com/blog/talking-about-tech-is-so-hard-its-a-wonder-we-can-do-it-at-all/</link><pubDate>Wed, 27 Feb 2019 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/talking-about-tech-is-so-hard-its-a-wonder-we-can-do-it-at-all/</guid><description>&lt;p&gt;&lt;img src="title.png" alt="Empty Grassland" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;A while ago I was watching AWS re:Invent, presenting its ever-flowing stream of new and innovative cloud services. And I couldn&amp;rsquo;t help but admire what I saw: Not just the services themselves, but especially the ease with which the presenters navigated the sky-high piles of ever thicker abstraction layers that constitute modern information technologies.&lt;/p&gt;
&lt;p&gt;Of course, this talent isn&amp;rsquo;t exclusive to the people we see on stage - we all use it on a daily basis, often without noticing. Just imagining Amazon announcing its new time-series-database-as-a-service offering with all abstractions removed:&lt;/p&gt;</description></item><item><title>How to create 3D Cloud Architecture Diagrams with Arcentry</title><link>https://arcentry.com/blog/how-to-create-3d-architecture-diagrams-with-arcentry/</link><pubDate>Tue, 26 Feb 2019 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/how-to-create-3d-architecture-diagrams-with-arcentry/</guid><description>&lt;p&gt;Branching lines, walls around a VPN, custom components, layers and sharing are just some of the features I cover in this tutorial video - have a look:&lt;/p&gt;
&lt;iframe title="Embedded media" loading="lazy" width="700" height="394" src="https://www.youtube.com/embed/j4JCFa0yHrc" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen&gt;&lt;/iframe&gt;</description></item><item><title>Democratizing Industry 4.0</title><link>https://arcentry.com/blog/democratizing-networked-production/</link><pubDate>Mon, 07 Jan 2019 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/democratizing-networked-production/</guid><description>&lt;p&gt;&lt;img src="title.png" alt="Crane lifting Vertical Shaft Sinking Machine" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;Every couple of decades the way we produce things gets turned upside-down.&lt;/p&gt;
&lt;p&gt;It happened in the early 19th century when mechanical looms and steam-engines caused productivity to skyrocket. It happened in the 20th century with the advent of electricity and mass production on assembly-lines. It happened in the 1990s when computer-controlled robots took over from human workers - and it is happening right now, in what&amp;rsquo;s shaping up to be the most fundamental shift yet.&lt;/p&gt;</description></item><item><title>At 22 years old, Postgres might just be the most advanced database yet</title><link>https://arcentry.com/blog/postgres-might-just-be-the-most-advanced-database-ever/</link><pubDate>Wed, 05 Dec 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/postgres-might-just-be-the-most-advanced-database-ever/</guid><description>&lt;p&gt;&lt;img src="./postgres.svg" alt="PostgreSQL Logo" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;As a techy, many of the debates I engage in can be boiled down to just one question: Should we pick the new thing or the proven one?
As passionate as this question is discussed, there are a handful of technologies where the answer is easy: Why not both?&lt;/p&gt;
&lt;p&gt;Postgres is such a technology. Originally released in 1996 (and effectively developed since 1982), it is now 22 years old - yet in many respects, it is the most modern database management system there is. Not only does it come with a simply mindboggling set of features, but it also transcends being a pure database and evolved into a fully programmable, integrated data environment, complete with its own programming language PL/pgSQL.&lt;/p&gt;</description></item><item><title>What comes after serverless?</title><link>https://arcentry.com/blog/what-comes-after-serverless/</link><pubDate>Mon, 03 Dec 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/what-comes-after-serverless/</guid><description>&lt;p&gt;&lt;img src="header.jpg" alt="Multiple Doors representing choices" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;As humans, we have this weird tendency: We believe that however things are right now, that&amp;rsquo;s the way they&amp;rsquo;ll always be. It&amp;rsquo;s not that we don&amp;rsquo;t acknowledge the existence of change or past progress - but somehow, we rationalize that the status quo necessarily constitutes a peak or final stage in its development and we&amp;rsquo;re struggling to imagine how it could ever be superseded.&lt;/p&gt;
&lt;p&gt;This seems particularly true for discussions about serverless lately:
It&amp;rsquo;s just an isolated function - right? How much less could you possibly run?&lt;/p&gt;</description></item><item><title>Four predictions for the next decade of Cloud Computing</title><link>https://arcentry.com/blog/four-predictions-for-the-next-decade-of-cloud-computing/</link><pubDate>Thu, 08 Nov 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/four-predictions-for-the-next-decade-of-cloud-computing/</guid><description>&lt;p&gt;&lt;img src="title.png" alt="Cloud" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;The cloud&amp;rsquo;s key promise of &amp;ldquo;less infrastructure, more business value&amp;rdquo; - holds as true as ever.
But the way the cloud delivers on this promise - and the way that users adopt it - is undergoing significant change.&lt;/p&gt;
&lt;p&gt;It is, of course, always hard to make predictions about something as young and dynamic as cloud infrastructure, but I believe there are four distinct trends that are likely to accelerate over the next decade and that are already fundamentally reshaping what &amp;ldquo;the cloud&amp;rdquo; really is:&lt;/p&gt;</description></item><item><title>An introduction to medieval cities and cloud security</title><link>https://arcentry.com/blog/an-introduction-to-medieval-cities-and-cloud-security/</link><pubDate>Mon, 17 Sep 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/an-introduction-to-medieval-cities-and-cloud-security/</guid><description>&lt;div class="image-with-attribution"&gt;
 &lt;img src="carcassone.jpg" alt="Panorama of the Cité de Carcassonne" /&gt;
 &lt;p class="image-title"&gt;Panorama of the Cité de Carcassonne by Chensiyuan &lt;a href="https://creativecommons.org/licenses/by-sa/4.0"&gt;CC BY-SA 4.0&lt;/a&gt;, from Wikimedia Commons&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Sometimes, trust is THE most important resource - something vividly apparent when standing atop the towering walls of Carcassonne, a fortified city in south-western France. For centuries, its citizens were subject to countless sieges and invasion attempts, leaving them with little reason to trust anyone out on the open planes surrounding the city - and yet they had to exert some degree of trust in order to trade, to travel, to work on their farms and fields and to keep connections to other villages - in short, to function as a society.&lt;/p&gt;</description></item><item><title>Arcentry API: Programmable Cloud Diagrams</title><link>https://arcentry.com/blog/announcing-the-arcentry-api/</link><pubDate>Tue, 28 Aug 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/announcing-the-arcentry-api/</guid><description>&lt;p&gt;It&amp;rsquo;s been quite a few late evenings and coffee-sustained nights, but today we are excited to announce that Arcentry diagrams have just become programmable.&lt;/p&gt;
&lt;p&gt;&lt;img src="scaling-groups.gif" alt="Scaling Groups" loading="lazy"&gt;
&lt;/p&gt;
&lt;h2 id="butwhy"&gt;But&amp;hellip;why?&lt;/h2&gt;
&lt;p&gt;Keeping track of the bigger picture is one of the hardest things when running any cloud infrastructure. Existing tools stop at the component level and even cloud-provider dashboards are broken down into individual services and their respective instances. There&amp;rsquo;s no layer above that lets you see or control what your cloud actually does or looks like.
And that&amp;rsquo;s a shame - because having a holistic view and seeing problems and bottlenecks in their wider context can be invaluable when it comes to debugging, maintaining and optimizing complex deployments.&lt;/p&gt;</description></item><item><title>What the f*** is the edge?</title><link>https://arcentry.com/blog/what-the-f-is-the-edge/</link><pubDate>Thu, 09 Aug 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/what-the-f-is-the-edge/</guid><description>&lt;p&gt;I still remember a call with a potential investor I had a while ago at deepstreamhub, a company selling realtime data servers to enterprises. Things were going well, we churned through the technical concepts, use cases, customer adoption and business metrics and she seemed to like what she heard.
But then her tone of voice lowered - a long pause ensued, and I could tell that she was about to ask something really, REALLY important. I braced myself - here it came:&lt;/p&gt;</description></item><item><title>How to choose a database in 2018</title><link>https://arcentry.com/blog/choosing-a-database-in-2018/</link><pubDate>Tue, 07 Aug 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/choosing-a-database-in-2018/</guid><description>&lt;p&gt;&lt;img src="overview.png" alt="databases" loading="lazy"&gt;
&lt;/p&gt;
&lt;p&gt;I met a friend for lunch the other day and we were chatting about the jungle of databases and data storage solution out there- and what a jungle it is: At the time of writing &lt;a href="https://db-engines.com/en/ranking"&gt;DB Engines Ranking&lt;/a&gt; lists more than 340 actively developed and up to date databases to choose from - all of which essentially present slightly different solutions to the same problem: storing and retrieving text-based information. To help you navigate this jungle, this article tries to offer a simple framework for deciding which database is right for your project.&lt;/p&gt;</description></item><item><title>Embed interactive cloud diagrams directly into your website</title><link>https://arcentry.com/blog/announcing-embeddable-diagrams/</link><pubDate>Mon, 06 Aug 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/announcing-embeddable-diagrams/</guid><description>&lt;p&gt;Sometimes your architecture gets too complex to fit into a single picture to put on your website or presentation. Sometimes you want to give your blog&amp;rsquo;s readers something a little more special and cool. Whatever it is - Arcentry&amp;rsquo;s new embed feature might just do the trick.&lt;/p&gt;
&lt;p&gt;It lets you embed your diagram in an interactive 3D viewer directly into your app. Here&amp;rsquo;s what that looks like:&lt;/p&gt;
&lt;p&gt;&lt;embed-frame id="b03e4004-ffdd-49b4-9ca7-80add3ccf6a0"&gt;&lt;/embed-frame&gt;&lt;/p&gt;
&lt;p&gt;To give it a go, log into your Arcentry account and go to export-&amp;gt;embed in website or &amp;lt;a href=&amp;quot;#&amp;quot; @click=&amp;ldquo;showForm(&amp;lsquo;signup&amp;rsquo;)&amp;quot;&amp;gt;sign up to Arcentry for free&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Our (not so smooth) journey productising a serverless app on AWS</title><link>https://arcentry.com/blog/our-not-so-smooth-journey-getting-a-serverless-webapp-to-production/</link><pubDate>Mon, 06 Aug 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/our-not-so-smooth-journey-getting-a-serverless-webapp-to-production/</guid><description>&lt;p&gt;Serverless is the future. I&amp;rsquo;m sure of it. The cloud&amp;rsquo;s great promise is to help companies focus on business value rather than infrastructure - and serverless is our best take delivering on this promise so far.&lt;/p&gt;
&lt;p&gt;But the current reality of serverless is something I am far less sure of. Navigating the jungle of Lambda Functions, API Gateways, S3 Buckets, VPNs, VPCs, Cloudfront Templates, Log groups, Internet Gateways, Policy Attachments, IAM roles and all the other bits and bops required does not quite feel like what we had in mind when we envisioned the simple, self-orchestrating, serverless world of tomorrow.&lt;/p&gt;</description></item><item><title>Scaling webapps for newbs &amp; non-techies</title><link>https://arcentry.com/blog/scaling-webapps-for-newbs-and-non-techies/</link><pubDate>Fri, 27 Jul 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/scaling-webapps-for-newbs-and-non-techies/</guid><description>&lt;img alt="" loading="lazy" src="lego-title-image.jpg" /&gt;
This guide summarizes the basic principles of scaling - from a single server to a web app capable of serving millions of users. It is aimed at newcomers and non-developers working in technical fields - so if you've just deployed your multi-cloud-terraform-vpn-setup, this one is not for you.
&lt;p&gt;For everyone else though: Let&amp;rsquo;s get started!&lt;/p&gt;
&lt;h2 id="scalingwut"&gt;Scaling&amp;hellip;wut?!?&lt;/h2&gt;
&lt;p&gt;You&amp;rsquo;ve just finished building your website, online store, social network or whatever else it is you are up to, put it online and things are going splendidly: A few hundred visitors pass by your site every day, requests are answered quickly, orders are processed immediately and everything is humming along nicely.&lt;/p&gt;</description></item><item><title>Why building a cloud management AI starts with a diagram drawing app</title><link>https://arcentry.com/blog/why-building-a-cloud-management-ai-starts-with-a-diagram-drawing-app/</link><pubDate>Tue, 24 Jul 2018 00:00:00 +0000</pubDate><guid>https://arcentry.com/blog/why-building-a-cloud-management-ai-starts-with-a-diagram-drawing-app/</guid><description>&lt;p&gt;I still remember the first web app I’ve ever deployed. I did what most people were doing back then: I paid a hosting provider for a “v-host” - a tiny folder on a server I shared with hundreds of other users. It ran PHP scripts and allowed access to a small section of a shared MySQL database. It wasn’t fast, had no means of scaling and security was &amp;hellip;well… debatable. But it worked.&lt;/p&gt;</description></item></channel></rss>