{"version":"1.0","provider_name":"Software Architecture Gathering 2026","provider_url":"https:\/\/conferences.isaqb.org\/software-architecture-gathering","author_name":"Mika Gustavson","author_url":"https:\/\/conferences.isaqb.org\/software-architecture-gathering\/author\/wolkenhart\/","title":"Chopping the Monolith - Software Architecture Gathering 2026","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"eUsMXGNSmI\"><a href=\"https:\/\/conferences.isaqb.org\/software-architecture-gathering\/session\/chopping-the-monolith\/\">Chopping the Monolith<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/conferences.isaqb.org\/software-architecture-gathering\/session\/chopping-the-monolith\/embed\/#?secret=eUsMXGNSmI\" width=\"600\" height=\"338\" title=\"&#8220;Chopping the Monolith&#8221; &#8212; Software Architecture Gathering 2026\" data-secret=\"eUsMXGNSmI\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script type=\"text\/javascript\">\n\/* <![CDATA[ *\/\n\/*! This file is auto-generated *\/\n!function(d,l){\"use strict\";l.querySelector&&d.addEventListener&&\"undefined\"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!\/[^a-zA-Z0-9]\/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret=\"'+t.secret+'\"]'),o=l.querySelectorAll('blockquote[data-secret=\"'+t.secret+'\"]'),c=new RegExp(\"^https?:$\",\"i\"),i=0;i<o.length;i++)o[i].style.display=\"none\";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(\"style\"),\"height\"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):\"link\"===t.message&&(r=new URL(s.getAttribute(\"src\")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(\"message\",d.wp.receiveEmbedMessage,!1),l.addEventListener(\"DOMContentLoaded\",function(){for(var e,t,s=l.querySelectorAll(\"iframe.wp-embedded-content\"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(\"data-secret\"))||(t=Math.random().toString(36).substring(2,12),e.src+=\"#?secret=\"+t,e.setAttribute(\"data-secret\",t)),e.contentWindow.postMessage({message:\"ready\",secret:t},\"*\")},!1)))}(window,document);\n\/* ]]> *\/\n<\/script>\n","description":"Micro services are ubiquitous. However, most companies that implement micro services do not reap their full benefits - at best. At worst, it\u2019s an epic failure.  There are reasons for micro services: independent deployment of business capabilities. However, the unspoken assumption is that you need to deploy all capabilities all the time. My experience has shown me that it\u2019s plain wrong. Some capabilities need frequent deployment, while some are much more stable. In \u201cthe past\u201d, we used Rule Engines to allow updating business rules without deployment. While it solved the problem, this approach had issues. Between introducing a Rule Engine and migrating your complete system to micro services, I believe that there\u2019s a middle path, and that this path is Function-as-a-Service.  In this talk, I\u2019ll detail every point I\u2019ve made above, and show how one can use Serverless to pragmatically design a system that allows deploying as often as you need."}