Mathias Nitzsche

Want to integrate systems without turning your architecture into a spaghetti mess? “𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝘀𝗶𝗴𝗻 𝘄𝗶𝘁𝗵 𝗗𝗗𝗗” is a hands-on workshop where 🐝Karol Skrzymowski and Philipp Kostyra show how to use Domain-Driven Design to design integrations that actually match business domains - not just “connect system A to B”. You’ll work through real scenarios and leave with practical skills:  • trade-off analysis of integration options,  • focusing on key quality attributes (time-to-market, extensibility, composability),  • justifying architectural decisions with business reasoning,  • choosing the right ecosystem style: 𝗽𝗼𝗶𝗻𝘁-𝘁𝗼-𝗽𝗼𝗶𝗻𝘁, 𝗲𝘃𝗲𝗻𝘁-𝗱𝗿𝗶𝘃𝗲𝗻, 𝗯𝗿𝗼𝗸𝗲𝗿 𝘁𝗼𝗽𝗼𝗹𝗼𝗴𝘆, 𝗔𝗣𝗜-𝗹𝗲𝗱. Expect interactive exercises, discussion, and patterns you can take straight into real projects. #PolishDreamin26 #Architecture #Integration #DDD #DomainDrivenDesign #EAI #APILed #EventDriven #EDA #Microservices #SystemsDesign #SolutionArchitecture #Tradeoffs #TechWorkshop #TrailblazerCommunity #SalesforceCommunity #Wroclaw #TechConference

5

Running multiple coding agents at the same time 🤝 Beyond Code GmbH recently released their new product Polyscope, an agent-first dev environment. We've had the chance to talk to Sebastian Schlein, CEO of Beyond Code GmbH, about it and Yannick had a few interesting questions. Check out the interview to hear what Sebastian is really excited about and how he is able to do bug fixes on his phone while attending Laracon EU. ℹ️ There is also a free version of Polyscope and Beyond Code GmbH has been busy adding features since the release and we're sure there is even more to come!

17

2 Kommentare

Ten requests. Could be ten cache hits. Could be ten heavy server-side renders that pin every core you have. Same number. Wildly different cost. ⚠️ This is the trap enterprise teams fall into constantly! Teams build capacity forecasts on top of traffic volume, because traffic is the easiest thing to measure. Then they're surprised when the forecast is wrong, because volume was never the thing that mattered; work was. 💡 The Platformatic ICC Planner doesn't touch request counts. It learns from what the real-time scaler already knows: Event Loop Utilization, heap pressure, the actual capacity target your app needed to stay healthy. That's the signal that reflects what your Node.js process is actually doing under the hood! If your capacity planning still starts with "requests per second," you're building a forecast on the wrong variable. It'll look reasonable right up until it isn't. What's the metric your team currently trusts to represent "load," and have you ever checked whether it's lying to you?

2

1 Kommentar

🚀 The API Conference Berlin program brings together practical sessions and workshops for teams working on APIs, AI agents, governance, frontend–backend integration, security, and modern software architecture. Here are a few highlights you should have on your radar: 🔗 Closing the Gap: Seamless Frontend–Backend APIs with tRPC with Mario Goller  A look at how tRPC helps teams build end-to-end type-safe APIs between frontend and backend. 🤖 Workshop: Architecting AI-Ready APIs with Agent Skills with Erik Wilde and Frank Kilcommins  A hands-on workshop on designing governed APIs for AI-driven integrations and autonomous agent workflows. 🧾 Beyond Commercial Monoliths: How to Build a Vendor-Agnostic Invoice Extraction Pipeline with S(V)LMs and Visual Judging with Dr. Kersten Döring  A practical session on building flexible, vendor-agnostic AI pipelines for document processing. 🤝 Mind Your Manners: API Etiquette with Michael Dowden  Why good API consumption matters for performance, cost, reliability, and scalable integration. 📍 Berlin 📆 November 16–20, 2026 👉 Explore the full program: https://lnkd.in/dDuwi3VN 👉 Get your ticket: https://lnkd.in/dEi-FXfj #APIConference #APIs #APIDesign #APIManagement #AIAgents #APIArchitecture #APIGovernance #SoftwareArchitecture #BackendDevelopment #BerlinEvents

5

2 Kommentare

Your software architecture might be costing you more than you think. Not just in cloud bills. In slower releases. In fragile integrations. In engineering time. In features that take weeks instead of days. And the difficult part? You may not notice it until your product starts scaling. At Remote Data Exchange, when we look at a software platform, we don't start with: “Which technology should we use?” We start with: “What is the business trying to achieve, and what does the architecture need to make possible?” Imagine you're building a platform that needs to support thousands—or eventually millions of users. We'd break the architecture down by asking: → Which components actually need to scale independently? → Where could real-time processing become a bottleneck? → Which data belongs in transactional systems, and which doesn't? → Where are unnecessary infrastructure costs accumulating? → What happens when one service fails? → Can the engineering team add new capabilities without constantly touching the core system? These decisions matter. Because adding more technology doesn't automatically make a system more scalable. Sometimes a complex microservices architecture is exactly what you need. Sometimes it's an expensive layer of complexity you don't need yet. The right architecture depends on your product, your users, your growth plans, and your business model. That's the difference between building software and engineering for growth. At RDX, we help businesses design, modernize, and scale software systems with that bigger picture in mind. If your product is growing and you're wondering whether your current architecture is ready for the next stage Let's take a look at it. 📩 Message us and let's start the conversation. #SoftwareArchitecture #SoftwareDevelopment #TechStrategy #DigitalTransformation #ScalableSoftware #Engineering #RDX

1

🔐 Single Sign-On (SSO) looks simple to users — but it’s one of the most important trust flows in modern systems. From the user’s perspective, SSO feels like: 👉 log in once 👉 access multiple apps 👉 move faster with less friction But behind that convenience is a carefully orchestrated exchange between: the user the service provider the identity provider This visual explains that flow well: The user requests access The app checks for an active session If none exists, it redirects to the identity provider The user authenticates Credentials are verified A token is issued Access is granted — and reused across connected services Why SSO matters ✅ Better user experience One login can unlock multiple services. ✅ Centralized identity management Authentication is handled in one place, not scattered across apps. ✅ Stronger security controls It becomes much easier to enforce: MFA conditional access centralized session management identity-based monitoring But here’s the tradeoff SSO improves usability and control, but it also makes the identity layer more critical than ever. If the identity provider is weak, everything connected to it inherits that weakness. That’s why SSO should never be treated as just a convenience feature. It’s a security architecture decision. My takeaway SSO is really about balancing two things: less friction for users and stronger trust enforcement for systems When implemented well, it does both. 💬 What do you think is the bigger SSO challenge in practice: integration complexity, token/session security, or identity-provider trust? #SSO #IdentitySecurity #IAM #Authentication #CyberSecurity #ZeroTrust #AccessManagement #SystemDesign #CloudSecurity

70

🦸 Five new speakers join the React Day Berlin lineup, and they're bringing some of the hottest topics in React right now. ⚡ Violina Popova, Software Developer at ClipMyHorse.TV: "Controlling Async Chaos in React with Effect-TS" ⚡ Austin Zhang, AI Engineer at Google DeepMind: "Human + AI Shared State Management: Extending Frontend Patterns into Agentic Systems" ⚡ Misha Kazakov, Frontend Engineer at Netflix, workshop: "Transform Your React App Into an MCP App. Rebuilding UI for AI Agents" ⚡ Ramona Schwering, Engineer at mittwald: "Don't Panic! React Security After 2025" ⚡ Scott Batson, Staff Engineer at Medium: "The Code Isn't Precious: What Every Staff Engineer Figured Out That You Haven't Yet" 🎟Learn more: https://reactday.berlin

31

There's no "best" database. No "best" architecture. No "best" approach. There are only trade-offs. Fast vs. consistent. Simple vs. scalable. Cheap vs. reliable. Engineering is choosing which trade-offs you can live with.

4

SaaS breaks down when it doesn’t match your architecture. Most operational inefficiencies aren’t due to lack of tools, they come from poor system fit. Common symptoms: • Feature bloat with low utilization • Missing workflow-specific capabilities • Fragile integrations across multiple platforms • Manual workarounds to bridge system gaps This is a system design problem, not just a tooling issue. At CodeAutomation.ai, we build custom software engineered around your operations: • Workflow-specific architecture (not template-based) • API-first integrations with your existing stack • Scalable systems aligned with business growth • Automation layers to eliminate repetitive processes • Full ownership of codebase and infrastructure We’ve delivered 350+ solutions across web apps, SaaS platforms, and internal systems for 16+ industries. If your stack requires constant patching to function, it’s likely time to rebuild with intent. 🔗 https://lnkd.in/g_GkZTBT

4