<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Pandhu Wibowo on Medium]]></title>
        <description><![CDATA[Stories by Pandhu Wibowo on Medium]]></description>
        <link>https://medium.com/@pandhuwibowo?source=rss-f36a1987a51e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nY7CrKJ0b5--mDkQbU46qA.jpeg</url>
            <title>Stories by Pandhu Wibowo on Medium</title>
            <link>https://medium.com/@pandhuwibowo?source=rss-f36a1987a51e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:18:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pandhuwibowo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Great Open-Source Exodus: Why Teams Are Moving Away from Redis, Terraform, and Vault (And What…]]></title>
            <link>https://pandhuwibowo.medium.com/the-great-open-source-exodus-why-teams-are-moving-away-from-redis-terraform-and-vault-and-what-8f1011196739?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f1011196739</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Tue, 10 Nov 2026 15:24:44 GMT</pubDate>
            <atom:updated>2026-11-10T15:24:44.977Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Great Open-Source Exodus: Why Teams Are Moving Away from Redis, Terraform, and Vault (And What Replaces Them)</h3><p><em>Stop building on shifting licenses — your 2026 guide to OpenTofu, OpenBao, Valkey and friends.</em></p><h3>The hook: the license rug-pull</h3><p>For a decade, Terraform, Vault and Redis were the boring, dependable bedrock of modern infrastructure. You picked them because everyone picked them — and because they were open source.</p><p>Then the ground moved. In 2023 HashiCorp relicensed Terraform and Vault from MPL-2.0 to the Business Source License (BUSL-1.1). In 2024 Redis left BSD for a dual RSALv2/SSPL model. Neither is an OSI-approved open-source license; both are “source-available”, which means you can read the code but your rights to build on it depend on what you build.</p><p>For engineering teams, that created three real risks:</p><ul><li><strong>Legal ambiguity and lock-in.</strong> Source-available licenses restrict competitive or hosted use. If you run an internal platform, a multi-tenant SaaS, or embed these tools in a product, someone in legal now has to read the fine print.</li><li><strong>Ecosystem fragmentation.</strong> Cloud providers and the Linux Foundation forked each project to protect themselves. A large share of community contributors, integrations and distro packaging followed the forks.</li><li><strong>Frozen, unpatched stacks.</strong> Teams that “just pinned” the last open version (Terraform 1.5.7, Redis 7.2.4) are now running software that no longer gets security fixes.</li></ul><blockquote><em>💡 </em><strong><em>Fun fact:</em></strong><em> These forks were born fast. OpenTofu launched life as </em><strong><em>OpenTF</em></strong><em>, a manifesto signed by companies within days of HashiCorp’s announcement, and was renamed before joining the Linux Foundation. Valkey went from Redis’s license change to a Linux Foundation project in roughly a week.</em></blockquote><h3>Infrastructure as code: Terraform → OpenTofu</h3><p><strong>Why move:</strong> BUSL-1.1, a roadmap decided behind closed doors, and features increasingly steered toward HCP Terraform / Terraform Enterprise.</p><h3>The drop-in: OpenTofu</h3><ul><li><strong>Governance:</strong> Linux Foundation project, MPL-2.0 — the license Terraform used to have.</li><li><strong>Compatibility:</strong> a fork of Terraform 1.5.x, so existing HCL, providers and state files work. For most teams it’s close to a binary swap.</li><li><strong>Its own features now:</strong> native client-side state encryption (a long-requested feature Terraform never shipped in open source), early-evaluated variables in backends and module sources, provider for_each, and more.</li></ul><p><strong>Migration checklist:</strong></p><ol><li>Audit required_version constraints — OpenTofu versions differ from Terraform&#39;s.</li><li>Note the registry: providers resolve via registry.opentofu.org. Check the lock file after the first tofu init.</li><li>Back up state first, then run tofu plan and confirm a no-op.</li><li>Lock down CI/CD so a stray terraform apply can&#39;t write to state after you&#39;ve moved.</li></ol><h3>Alternatives if you want to leave HCL entirely</h3><ul><li><strong>Pulumi</strong> (Apache-2.0) — infrastructure in TypeScript, Python, Go, C# or Java.</li><li><strong>Crossplane</strong> (CNCF, Apache-2.0) — manage cloud resources as Kubernetes custom resources with continuous reconciliation.</li></ul><blockquote><em>💡 </em><strong><em>Fun fact:</em></strong><em> HashiCorp itself is no longer independent — </em><strong><em>IBM completed its acquisition of HashiCorp in early 2025.</em></strong><em> Terraform and Vault are now IBM products, which is one more reason teams are re-evaluating long-term roadmaps.</em></blockquote><h3>Secrets management: Vault → OpenBao &amp; Infisical</h3><p><strong>Why move:</strong> Vault went BUSL-1.1 alongside Terraform, and self-hosting a highly available Vault cluster (unseal, storage, upgrades, policies) is a real operational job.</p><h3>The drop-in: OpenBao</h3><ul><li><strong>Governance:</strong> Linux Foundation (OpenSSF) fork of Vault, MPL-2.0.</li><li><strong>Why choose it:</strong> API-compatible with Vault, so existing clients, auth methods and dynamic-secret workflows keep working. The lowest-friction exit if Vault is already deeply embedded.</li></ul><h3>The developer-first option: Infisical</h3><ul><li><strong>Governance:</strong> MIT-licensed open core.</li><li><strong>Why choose it:</strong> lighter to run, clean UI and CLI, environment-aware secrets, secret rotation and dynamic secrets, self-hosted or cloud.</li></ul><h3>The Kubernetes-native pattern: ESO + cloud secret managers</h3><p>Keep secrets in AWS Secrets Manager, Google Secret Manager or Azure Key Vault and sync them into clusters with <strong>External Secrets Operator</strong> (Apache-2.0). No stateful secrets cluster to babysit.</p><h3>In-memory data stores: Redis → Valkey &amp; Dragonfly</h3><p><strong>Why move:</strong> the 2024 license change broke trust with the community, and teams pushing huge throughput were already fighting Redis’s mostly single-threaded command execution.</p><h3>The drop-in: Valkey</h3><ul><li><strong>Governance:</strong> Linux Foundation fork of Redis 7.2.4 (the last BSD release), BSD-3-Clause.</li><li><strong>Why choose it:</strong> the default open Redis replacement in 2026. It speaks the same protocol and works with existing Redis clients, is backed by AWS, Google Cloud, Oracle and others, and has shipped major releases of its own (8.x, then 9.x) with multithreaded I/O improvements and memory-efficiency work.</li></ul><h3>The performance option: Dragonfly</h3><p>A multi-threaded, shared-nothing engine that speaks the Redis and Memcached protocols. Ideal when you want very high throughput per node and fewer shards to manage. Note: Dragonfly uses BSL 1.1 itself, so check whether it fits your licensing policy.</p><h3>Honorable mentions</h3><ul><li><strong>Garnet</strong> (Microsoft Research, MIT) — RESP-compatible cache store with tiered storage.</li><li><strong>Apache Kvrocks</strong> (Apache-2.0) — RocksDB-backed, for datasets too large or too persistent to keep entirely in RAM.</li></ul><blockquote><em>💡 </em><strong><em>Fun fact — the plot twist:</em></strong><em> Redis came back. Salvatore Sanfilippo (“antirez”), Redis’s original creator, rejoined the company in November 2024 and pushed for an open license. </em><strong><em>On May 1, 2025, Redis 8 shipped with AGPLv3 added as a licensing option</em></strong><em>, alongside RSALv2 and SSPL. Redis is technically open source again — but AGPL is a non-starter at many companies, and Valkey had already replaced Redis in major Linux distros. Trust, it turns out, is harder to relicense than code.</em></blockquote><h3>Quick comparison table</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*IhgGCo6bL0mvzs2wgmt8cg.png" /></figure><h3>And so on: the same pattern elsewhere</h3><ul><li><strong>Elasticsearch → OpenSearch.</strong> The original blueprint. Elastic moved to SSPL/Elastic License in 2021; AWS forked OpenSearch (Apache-2.0), which now lives under the Linux Foundation.</li><li><strong>Promtail → Grafana Alloy.</strong> Not a license story but a deprecation one: Grafana is steering users from Promtail to Alloy, an OpenTelemetry-compatible collector.</li><li><strong>Ingress-NGINX → Gateway API / Envoy / Caddy.</strong> Kubernetes’ community Ingress-NGINX controller was announced for retirement, pushing teams toward Gateway API implementations such as Envoy Gateway.</li></ul><blockquote><em>💡 </em><strong><em>Fun fact:</em></strong><em> Elastic did a Redis-style U-turn first — it </em><strong><em>added AGPLv3 as an option for Elasticsearch in August 2024</em></strong><em>, about three years after its own license change. OpenSearch kept growing anyway.</em></blockquote><h3>Closing takeaways</h3><ul><li><strong>Don’t migrate blindly.</strong> If you rely on paid enterprise features (HCP Terraform, Vault Enterprise, Redis Enterprise) under a contract, staying can still be the right business call.</li><li><strong>Audit your dependencies.</strong> Find every tool pinned to a frozen, end-of-life open version. Those are your real security liabilities.</li><li><strong>Start new projects on open governance.</strong> For greenfield stacks, default to foundation-governed, OSI-licensed options like OpenTofu, OpenBao and Valkey, so a future license change can’t force an emergency migration.</li></ul><p>The lesson isn’t that companies are villains. Maintaining infrastructure software is expensive. The lesson is that <strong>governance is a feature</strong>, and it belongs on your evaluation checklist next to performance and docs.</p><p><em>What has your team migrated off, and what surprised you? Tell me in the comments.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f1011196739" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Honest Review: Almost 3 Months Using Anveesa Nias — Here’s What Actually Happened]]></title>
            <link>https://blog.devgenius.io/honest-review-almost-3-months-using-anveesa-nias-heres-what-actually-happened-271c59032cd5?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/271c59032cd5</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Tue, 23 Jun 2026 16:34:12 GMT</pubDate>
            <atom:updated>2026-06-25T12:29:58.072Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jxldMQJuDe_fOd-QGx6VOw.png" /></figure><p>Let me be upfront — this isn’t a sponsored post or a polished marketing piece. This is just me sharing what actually changed after switching to Anveesa Nias for the past (almost) 3 months.</p><p>Before I get into it, let me paint the picture of what my setup looked like before.</p><h3>The “Before” State</h3><p>If you work in IT infrastructure or DevOps, you probably know the drill. You’ve got a tab for this, a tool for that, a separate login for everything. My daily toolkit looked something like this:</p><ul><li>CloudBeaver for general database management</li><li>PgAdmin whenever I needed to go deeper into PostgreSQL</li><li>Kafka UI to monitor and manage message brokers</li><li>MongoDB Client for document-based database operations</li><li>Redis client for cache and session management</li><li>Archery DMS for SQL audit and review workflows</li><li>New Relic for monitoring and observability</li></ul><p>Seven tools. Seven different interfaces. Seven sets of credentials to manage. And on top of that, I had to provision and maintain multiple cluster nodes just to host all of these tools — each one eating its share of compute and memory.</p><p>Honestly? I didn’t even realize how exhausting it was until I stopped doing it.</p><h3>Why I Tried Anveesa Nias</h3><p>I’ll be honest — I went in skeptical. “All-in-one platform” tools have a reputation. They sound great in the pitch, but when you actually use them day-to-day, there’s always something missing, something half-baked, or something that works fine for simple use cases but falls apart when things get real.</p><p>But I decided to give it a shot anyway.</p><p>The first few days were just getting familiar with the interface and migrating my connections over. No dramatic moment, no instant “wow.” Just… gradually realizing I hadn’t opened PgAdmin in a week. Then two weeks. Then I terminated the node I was running Kafka UI on. Then another node went down because nothing was running on it anymore.</p><p>That’s when it clicked.</p><h3>What Actually Changed</h3><h4>One account to rule them all — with MFA.</h4><p>This sounds small but it’s not. Before, I was managing separate accounts across seven platforms. Different passwords, different session timeouts, different security postures. Some platforms had solid MFA support, others were basically just username and password and a prayer.</p><p>Now it’s one account. One login. And it comes with MFA built in. For someone who works in IT security, that alone already sold me. Centralized access management, proper authentication, no more juggling credentials across half a dozen platforms.</p><h4>Infrastructure cost went down — meaningfully.</h4><p>This was the most tangible, measurable impact. Before Anveesa Nias, I had several dedicated nodes in my cluster specifically to host and run all those tools. Each one had its own resource allocation — CPU, memory, storage. Now? I joined Anveesa Nias to an existing node, and the compute footprint is genuinely small. Those other nodes? Terminated.</p><p>Monthly cloud cost dropped. The budget I freed up didn’t just disappear into savings — I was able to reallocate it to things that actually move the needle. Better observability coverage, more capacity for actual workloads, less money going toward tool overhead.</p><h4>Productivity increased in ways I didn’t expect.</h4><p>I knew consolidating tools would save some time. What I didn’t anticipate was how much mental overhead I was carrying from context switching.</p><p>When you’re jumping between 7 different tools throughout the day — different UIs, different interaction patterns, different ways of doing the same thing — your brain is constantly re-orienting. It’s low-grade friction, but it’s constant. You stop noticing it after a while. Until it’s gone.</p><p>Now I stay in one place. One interface, one context, everything I need is reachable without opening a new tab or logging into something else. The time savings are real, but honestly the cognitive relief is what I notice most.</p><h4>Redis via terminal? Not anymore.</h4><p>One specific thing I want to call out — Redis. Before, managing Redis meant cracking open a terminal, connecting manually, running commands one by one. It worked, but it wasn’t exactly pleasant, especially when you just need a quick key inspection or want to flush something fast.</p><p>With Anveesa Nias, Redis has a proper interface. Point and click, browse keys, run commands — all inside the same platform I’m already in. It’s one of those quality-of-life improvements that you don’t know you needed until you have it.</p><h4>Alerts that actually reach you.</h4><p>Some of the tools I used before had limited or no alerting integration. You’d have to either poll manually or set up some janky workaround to get notifications into Slack or whatever channel your team lives in.</p><p>Anveesa Nias supports alert routing to channels. So when something needs attention, it goes where my team already is — no more “I didn’t see it because I wasn’t in that tool.” That’s the kind of operational maturity that makes a real difference in incident response time.</p><h4>The performance surprised me.</h4><p>This one I genuinely didn’t expect to be a highlight. When you consolidate everything into one platform, you kind of assume there’s going to be a trade-off somewhere — maybe it loads slower, maybe it feels heavier under the hood.</p><p>Nope.</p><p>Anveesa Nias is fast. Not “acceptable for a web-based tool” fast — actually fast. Lightweight, responsive, doesn’t make me wait. When you’re opening this thing dozens of times a day, that snappiness compounds. It’s one of those things that’s hard to quantify but you’d notice immediately if it went away.</p><h4>AI-driven features are now in the mix.</h4><p>This is something that’s been rolling out recently and it’s genuinely exciting. Anveesa Nias has started incorporating AI-driven features into the platform. It’s still evolving, but the direction is clear — making the tooling smarter, reducing the manual effort for things that don’t need to be manual. I won’t over-hype it because it’s still growing, but it’s a signal that the platform is moving in the right direction and the development is active, not stagnant.</p><h4>3 Months In</h4><p>No major complaints. Still using it daily. Still the go-to for anything database, monitoring, broker management — you name it.</p><p>Anveesa Nias has hit 4.2k downloads on Docker Hub and the number keeps climbing. From my side as the maintainer, I’m still actively developing and pushing updates — not because I feel obligated to, but because I use this tool myself every single day and I want it to keep getting better. The feedback loop is short: I notice something that could be improved, I fix it, I use the fix. That’s a good place to be.</p><h4>Who Should Try This</h4><p>If you’re managing infrastructure with 5, 6, 7 separate tools and it feels like that’s just “how it is” — it doesn’t have to be. If your cluster has nodes running purely to host tooling overhead — those nodes don’t need to exist. If you’re spending cognitive energy on tool-switching that could go toward actual problem-solving — there’s a better way.</p><p>Six months in, Anveesa Nias is one of those rare tools where the real-world experience actually matched — and in some areas exceeded — what was promised.</p><p>That doesn’t happen often. Worth talking about when it does.</p><p>If you’re curious or want to contribute to the project, check it out at <a href="https://anveesa.com/">https://anveesa.com/</a> or the GitHub repo at <a href="https://github.com/PandhuWibowo/anveesa-nias">https://github.com/PandhuWibowo/anveesa-nias</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=271c59032cd5" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/honest-review-almost-3-months-using-anveesa-nias-heres-what-actually-happened-271c59032cd5">Honest Review: Almost 3 Months Using Anveesa Nias — Here’s What Actually Happened</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Kafka Browser in Anveesa Nias — Manage Your Kafka Cluster Without Leaving Your…]]></title>
            <link>https://blog.devgenius.io/introducing-kafka-browser-in-anveesa-nias-manage-your-kafka-cluster-without-leaving-your-4d955f610599?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d955f610599</guid>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Sun, 10 May 2026 08:02:30 GMT</pubDate>
            <atom:updated>2026-05-13T09:10:30.826Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introducing Kafka Browser in Anveesa Nias — Manage Your Kafka Cluster Without Leaving Your Dashboard</h3><h4>A built-in Kafka client manager, now part of the open-source Anveesa Nias platform.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uSSbYUWEXmIdsuuiJawrhQ.png" /></figure><p>If you’ve ever managed a Kafka cluster, you know the drill. You SSH into a broker, run kafka-topics.sh, squint at the output, hop into another terminal to check consumer lag, and somewhere along the way you lose track of what you were actually debugging in the first place.</p><p>That friction is exactly what I wanted to eliminate when I built <strong>Kafka Browser</strong> into <a href="https://anveesa.com/">Anveesa Nias</a>.</p><h3>What is Anveesa Nias?</h3><p>Anveesa Nias is an open-source cloud storage and infrastructure manager I’ve been building as a personal project. The goal is simple: give developers and infrastructure engineers a single, clean interface to manage cross-cloud resources — without juggling five different tools and three browser tabs.</p><p>The project lives at <a href="https://github.com/PandhuWibowo/anveesa-nias">github.com/PandhuWibowo/anveesa-nias</a> and is available as a Docker image on Docker Hub.</p><h3>Why a Kafka Browser?</h3><p>Kafka is everywhere. If you’re running microservices, event-driven pipelines, or real-time data streams, you’re almost certainly running Kafka somewhere in the stack. But the tooling around Kafka has always felt fragmented — you need one tool to browse topics, another to watch consumer lag, and a CLI to produce test messages.</p><p>I wanted something integrated. Something you could pull up mid-incident and immediately see what’s happening — without remembering which flags to pass to kafka-console-consumer.</p><p>So I built it.</p><h3>What Kafka Browser Can Do</h3><p>Here’s a quick walkthrough of what’s shipped in this release.</p><h3>Topic &amp; Partition Overview</h3><p>The first thing you see when you connect your Kafka cluster is a clean summary: how many topics, total partitions, active consumer groups, and leader coverage status.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ND1CRrOul58_NdUCfywWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JBytc0vdSAI6zc0etyVOYQ.png" /></figure><p>From the Topics tab you can drill into any topic — view its partition count, replication factor, leader partitions, and which consumer groups are consuming it.</p><h3>Consumer Group Inspection</h3><p>The Consumer Groups tab is where things get useful fast. Select any group and you immediately see:</p><ul><li><strong>State</strong> — Empty, Stable, or Dead</li><li><strong>Members</strong> — how many active consumers are connected</li><li><strong>Tracked partitions</strong> — which partitions the group is assigned to</li><li><strong>Total lag</strong> — the number of messages yet to be consumed</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6zN5WpdL_AUV4qpYEQuRng.png" /></figure><p>The group detail panel also shows a per-partition offset breakdown — committed offset, latest offset, and lag per partition. This is the view you want open during a deployment or incident.</p><h3>Produce Messages</h3><p>Need to push a test message to verify your consumer is working? The Produce tab lets you do it directly from the dashboard. Set your key, headers, and value (JSON or plain text), pick your topic, and fire.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DNHq98ckel5_uawJmEIiZA.png" /></figure><p>No CLI. No kafka-console-producer. Just a clean form.</p><h3>Message Browser</h3><p>The Message Browser lets you read records from any topic across all partitions. You can set the decode mode (JSON, plain text), filter by partition, and set a replay target if you want to re-process messages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UGP822-fhjEDx8hVLDj1Kw.png" /></figure><p>One thing worth noting: __consumer_offsets is a Kafka-internal topic, so message browsing is disabled for it by default. For your own application topics, it works exactly as you&#39;d expect.</p><h3>End-to-End Trace Lookup</h3><p>This is one of my favourite features. If your services tag messages with a trace_id, you can search for it directly from the dashboard. Kafka Browser will check the selected topic and any configured DLQ / failure topics and build a timeline:</p><ul><li><strong>Produced</strong> — was the message produced in this session?</li><li><strong>Stored</strong> — is it stored in the topic?</li><li><strong>Consumed</strong> — has a consumer group committed the offset?</li><li><strong>Lag status</strong> — are offsets caught up?</li><li><strong>DLQ / Failure</strong> — did it land in a dead-letter queue?</li></ul><p>This kind of visibility is normally only possible by cross-referencing logs from multiple services. Having it in one place makes a real difference.</p><h3>Topic Admin</h3><p>You can also create and manage topics without touching the CLI. Set partition count, replication factor, and topic configs (retention, cleanup policy) directly from the Topic Tools tab. Partition increases are supported; deletion is available but irreversible — the UI makes that clear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mwz7GRRINU7u7tVSa8Pkmg.png" /></figure><h3>Getting Started</h3><p>Anveesa Nias runs as a Docker container. Getting started is straightforward:</p><pre>docker pull pandhu612/anveesa-nias:latest<br>docker run -d -p 8080:8080 pandhu612/anveesa-nias:latest</pre><p>Then open http://localhost:8080, add your Kafka connection (broker address and port), and you&#39;re in.</p><p>Full setup instructions and configuration options are in the GitHub repository:</p><p><strong>GitHub:</strong> <a href="https://github.com/PandhuWibowo/anveesa-nias">github.com/PandhuWibowo/anveesa-nias</a> <strong>Docker Hub:</strong> <a href="https://hub.docker.com/r/pandhu612/anveesa-nias/tags">hub.docker.com/r/pandhu612/anveesa-nias</a></p><h3>What’s Next</h3><p>This is an early release. The Kafka Browser covers the core use cases — topic inspection, consumer lag monitoring, message production and consumption, and trace lookup — but there’s more planned:</p><ul><li>Schema Registry support</li><li>ACL and user management</li><li>Alert rules on consumer lag thresholds</li><li>Multi-cluster switching</li></ul><p>If you have feature requests or run into issues, open an issue on GitHub. Contributions are very welcome.</p><h3>Closing Thoughts</h3><p>I built Anveesa Nias because I kept switching between tools during incidents and development, and I was tired of the context switching. Kafka Browser is the first major feature that directly solves that for me day-to-day.</p><p>If you’re running Kafka and want a cleaner way to interact with it, give it a try. It’s free, open-source, and runs entirely on your own infrastructure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d955f610599" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/introducing-kafka-browser-in-anveesa-nias-manage-your-kafka-cluster-without-leaving-your-4d955f610599">Introducing Kafka Browser in Anveesa Nias — Manage Your Kafka Cluster Without Leaving Your…</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anveesa Nias: Solusi Open Source untuk Integritas Data Produksi yang Auditable dan Transparan]]></title>
            <link>https://pandhuwibowo.medium.com/anveesa-nias-solusi-open-source-untuk-integritas-data-produksi-yang-auditable-dan-transparan-182b53dcd41a?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/182b53dcd41a</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Sun, 26 Apr 2026 16:10:56 GMT</pubDate>
            <atom:updated>2026-04-26T16:10:56.702Z</atom:updated>
            <content:encoded><![CDATA[<p>Sebagai praktisi yang berkutat dengan data di lingkungan produksi, kita semua tahu betapa krusialnya menjaga integritas, auditabilitas, dan transparansi. Namun, realitanya, proses pengelolaan data seringkali diwarnai oleh tantangan yang membuat kita bertanya-tanya: apakah ada cara yang lebih baik?</p><h3>Tantangan Klasik dalam Pengelolaan Data Produksi</h3><p>Bayangkan skenario ini: Anda perlu melakukan data adjustment di server produksi. Apa yang sering terjadi? Kita membuat script ad-hoc, atau lebih parah, copy-paste query langsung ke command line interface (CLI) server. Proses ini tidak hanya rentan kesalahan, tetapi juga memakan waktu, terutama ketika harus melewati birokrasi change management yang berlapis. Seringkali, ada “gap” besar antara prosedur yang tertulis dengan implementasi di lapangan, menciptakan risiko dan inefisiensi.</p><p>Kebutuhan akan tool yang mumpuni sangat terasa, terutama yang mendukung:</p><ul><li>Traceable &amp; Auditable: Setiap perubahan harus tercatat dengan jelas, siapa, kapan, dan apa yang diubah.</li><li>Private Connection: Keamanan adalah prioritas utama, koneksi ke database produksi harus privat dan terenkripsi.</li><li>Less CLI: Mengurangi interaksi langsung dengan CLI untuk meminimalkan risiko kesalahan manusia dan mempercepat operasional.</li><li>Logger Tersentralisasi: Semua aktivitas harus terekam di satu tempat untuk memudahkan troubleshooting dan audit.</li></ul><p>Sebelumnya, saya telah mencoba berbagai tool populer seperti Cloud Beaver, PgAdmin, dan Archery DMS. Meskipun masing-masing memiliki keunggulan, saya menemukan bahwa mereka memiliki keterbatasan signifikan yang justru menghambat alur kerja tim. Mulai dari kurangnya fitur audit yang mendalam, kesulitan dalam mengelola approval workflow, hingga ketergantungan pada CLI yang tinggi.</p><h3>Memperkenalkan Anveesa Nias: Lahir dari Kebutuhan Nyata</h3><p>Dari pengalaman dan “frustrasi” inilah, Anveesa Nias lahir. Ini adalah database studio open-source yang dirancang khusus untuk tim yang membutuhkan solusi komprehensif dalam menjelajahi data, menjalankan SQL, mengelola saved queries, membangun analytics dashboards, dan mengaudit aktivitas database melalui web UI yang intuitif. Dibangun dengan Go HTTP API di backend dan Vue 3 + Vite di frontend, Anveesa Nias menawarkan pendekatan modern untuk masalah klasik.</p><h3>Bagaimana Anveesa Nias Mengatasi Tantangan Anda?</h3><p>Anveesa Nias secara langsung menjawab poin-poin krusial yang sering menjadi kendala:</p><h3>1. Konektivitas Multi-Database &amp; SQL Editor Canggih</h3><p>Anveesa Nias mendukung koneksi ke berbagai database populer seperti PostgreSQL, MySQL, SQLite, dan SQL Server. Dilengkapi dengan SQL editor yang kaya fitur, saved queries, query history, dan schema browsing, memudahkan tim untuk berinteraksi dengan data tanpa perlu berpindah tool.</p><h3>2. Monitoring &amp; Audit Komprehensif</h3><p>Fitur monitoring dan audit adalah jantung dari Anveesa Nias. Ini memungkinkan tim untuk memahami penggunaan aplikasi, aktivitas database, risiko performa, dan perubahan historis. Beberapa fitur utamanya meliputi :</p><ul><li>Dashboard Operasional: Memberikan gambaran umum status aplikasi dan koneksi database secara real-time.</li><li>Query Performance: Mengidentifikasi query yang lambat atau gagal, membantu mengoptimalkan performa.</li><li>Database Audit: Memantau sesi database aktif dan sinyal akses, membantu mendeteksi aktivitas mencurigakan.</li><li>Audit Log: Melacak tindakan level aplikasi, memberikan akuntabilitas untuk workflow sensitif.</li><li>Row History: Menampilkan riwayat perubahan (INSERT, UPDATE, DELETE) pada level baris, memungkinkan pelacakan siapa yang mengubah data tertentu.</li><li>Watchers: Memantau query atau aktivitas tabel penting secara berkala.</li></ul><h3>3. Change Management dengan Approval Workflows</h3><p>Salah satu fitur paling revolusioner adalah manajemen perubahan yang terintegrasi dengan approval workflows . Ini mengatasi “gap” antara prosedur dan eksekusi dengan menyediakan:</p><ul><li>Approval Requests: Antrean global untuk permintaan write SQL yang memerlukan persetujuan sebelum dieksekusi. Ini memisahkan pembuatan permintaan dari persetujuan dan eksekusi, memastikan setiap perubahan berisiko memiliki jejak review yang jelas.</li><li>Change Sets: Mengemas perubahan database terstruktur dengan alur review dan eksekusi, memudahkan validasi perubahan besar sebelum diterapkan.</li><li>Data Scripts: Membangun perubahan data terprogram menggunakan JavaScript, Python, atau PHP API pembantu. Ini memungkinkan workflow yang lebih kompleks dan traceable untuk transformasi data.</li><li>Schema Diff: Membandingkan struktur skema antar target, membantu mengidentifikasi perbedaan sebelum perencanaan perubahan.</li></ul><p>Dengan fitur-fitur ini, Anveesa Nias memastikan bahwa setiap perubahan data di produksi tidak hanya aman dan auditable, tetapi juga transparan dan terkontrol melalui alur persetujuan yang jelas.</p><p>Anveesa Nias adalah proyek open-source yang dibangun untuk komunitas. Anda bisa dengan mudah menjalankannya menggunakan Docker, baik di lingkungan lokal untuk eksplorasi maupun di server untuk penggunaan produksi. Ini adalah undangan bagi para pengembang, data engineers, dan tim operasional untuk mencoba, memberikan feedback, dan berkontribusi.</p><p>Setiap feedback, laporan bug, atau bahkan ide fitur baru sangat berarti untuk pengembangan Anveesa Nias ke depan. Mari bersama-sama membangun tool yang lebih baik untuk pengelolaan data produksi.</p><p>Kunjungi repositori GitHub Anveesa Nias dan mulai berkontribusi hari ini:<a href="https://github.com/PandhuWibowo/anveesa-nias">https://github.com/PandhuWibowo/anveesa-nias</a></p><h3>Referensi</h3><p><a href="https://github.com/PandhuWibowo/anveesa-nias/blob/main/docs/03-monitoring-and-audit.md">[1] Monitoring And Audit — Anveesa Nias Documentation</a></p><p><a href="https://github.com/PandhuWibowo/anveesa-nias/blob/main/docs/04-change-management.md">[2] Change Management — Anveesa Nias Documentation</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=182b53dcd41a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero Gap — Production Changes. Transparent. Accountable. Controlled.]]></title>
            <link>https://medium.com/bitsrc/zero-gap-production-changes-transparent-accountable-controlled-023e03c45178?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/023e03c45178</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Fri, 20 Mar 2026 17:04:56 GMT</pubDate>
            <atom:updated>2026-03-20T17:11:45.599Z</atom:updated>
            <content:encoded><![CDATA[<h4>It is a powerful tool that you must use to keep your data integrity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAhpn8RGsIRgHLWaNzCoVA.png" /></figure><p>Every engineer, every DBA, everyone who has ever been responsible for a production environment — has been there.</p><p>A wrong record. A missed update. A migration that went sideways at the worst possible moment. The pressure is real. The consequences are real. And the clock is always ticking.</p><p>I’ve spent eight years in IT. And in those eight years, one thing has never changed: most companies still have no structured answer for how to safely handle this. The process exists somewhere between a Slack message, a manual form, and someone’s gut instinct. That’s not a process. That’s a prayer.</p><p>I’ve looked. Across the entire open-source landscape, across the tools teams swear by, across the solutions vendors sell — searching for one thing that could answer a simple question: <em>is this data change safe, traceable, and compliant?</em></p><p>What I found were fragments. Workarounds. Tools that solved half the problem and quietly ignored the rest. Nothing addressed the full picture.</p><p>So I built it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSPPBAN6rKo8&amp;type=text%2Fhtml&amp;schema=youtube&amp;display_name=YouTube&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSPPBAN6rKo8%3Ffeature%3Doembed" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7cfb4bea1d92853429f133cd29c027da/href">https://medium.com/media/7cfb4bea1d92853429f133cd29c027da/href</a></iframe><p>When production data needs to be updated, the debate is never about <em>whether</em> it should be done. Everyone already knows it has to happen. The real question — the one that rarely has a clean answer — is <em>how</em>. Under what controls. With whose approval. And with what guarantee that what was approved is exactly what gets executed.</p><p>Without a clear process, every engineer solves it differently. And that inconsistency is exactly where risk lives. I’ve seen it. More than once.</p><p>Before any change, teams fill out forms. Manually. In spreadsheets, in emails, buried in Confluence pages that nobody can find six months later. The approval is real — but the friction is enormous. And worse, the form is almost always disconnected from the actual execution.</p><p>There is a gap between what was approved and what was run. That gap is an audit finding waiting to happen.</p><p><em>Who ran this query? When? Against which database? With whose approval? What exactly did it change?</em></p><p>These questions shouldn’t be hard to answer. But without a dedicated tool, the audit trail lives in someone’s memory — or it doesn’t exist at all. And when the regulator walks in, “someone’s memory” is not an acceptable response.</p><p>I’ve sat in those rooms. I know how that conversation goes.</p><p>Companies operating in variants regulations— and there are many — treat every data operation in production as a potential audit finding. Compliance isn’t optional. It’s the baseline. The expectation isn’t just a solution that works. It’s a solution that <em>proves</em> it worked. To the right people. In the right format. Every single time.</p><p>So this is what I built.</p><p>Not a finished product. This is version one — the foundation. But it solves the core problem at its root: bringing structure, approval, and full traceability to every data change in production, from the moment a request is raised to the moment it’s executed.</p><p>The request is created inside the tool itself. The context, the intent, the SQL — everything lives in one place. No separate form. No copy-paste across systems. No gap between what was written and what gets run.</p><p>Before anything executes, it goes through an approval flow — in real time, inside the same tool. The approver sees exactly what will run. Not a summary. Not a description. The actual query. There is no ambiguity. There is no gap.</p><p>And when it runs, every action is logged. Who submitted it. Who approved it. What was executed. When. Against which database. That log isn’t just useful for security — it <em>is</em> the compliance record. When the auditor asks what happened to a record, you don’t scramble. You open the tool, and the answer is already there. Clean. Timestamped. Attributed.</p><p>There is more to build. More features, deeper integrations, more granular controls. But the foundation is right.</p><p>Every production data change — from request to approval to execution — in one traceable, auditable, compliant workflow.</p><p>Eight years of watching this problem get ignored. This is where it ends.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=023e03c45178" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bitsrc/zero-gap-production-changes-transparent-accountable-controlled-023e03c45178">Zero Gap — Production Changes. Transparent. Accountable. Controlled.</a> was originally published in <a href="https://medium.com/bitsrc">Bits and Pieces</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[This Tool Will EnhanceYour Security]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://pandhuwibowo.medium.com/this-tool-will-enhanceyour-security-f396ad307b98?source=rss-f36a1987a51e------2"><img src="https://cdn-images-1.medium.com/max/2600/1*fICg5MzpSwapwCGHujiosg.png" width="2854"></a></p><p class="medium-feed-snippet">Avoid given permission from when your user does not really need important service</p><p class="medium-feed-link"><a href="https://pandhuwibowo.medium.com/this-tool-will-enhanceyour-security-f396ad307b98?source=rss-f36a1987a51e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandhuwibowo.medium.com/this-tool-will-enhanceyour-security-f396ad307b98?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f396ad307b98</guid>
            <category><![CDATA[anveesa-vestra]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[sre]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Sun, 08 Mar 2026 05:07:05 GMT</pubDate>
            <atom:updated>2026-06-30T14:54:23.780Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Developer now no need access Cloud anymore]]></title>
            <link>https://blog.devgenius.io/developer-now-no-need-access-cloud-anymore-6ab6fdb1f869?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ab6fdb1f869</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Sun, 22 Feb 2026 14:44:25 GMT</pubDate>
            <atom:updated>2026-02-26T08:43:29.376Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey everyone! It’s been a minute, hasn’t it? I’ve been a little MIA lately catching up on life. Anyway, wishing a happy Ramadan to everyone fasting — may you all be blessed!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nG4NlgNUiMEG6PGOPLoyiQ@2x.jpeg" /><figcaption>Photo by Fuu J on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Have you ever faced, if any none infrastructure member/SRE/Platform Engineer member wants access bucket yes only bucket, you have to given access a cloud platform?</p><p>Even the requester only need one bucket, you must allow cloud permission.</p><p>But in the world of cloud infrastructure, “simple” often turns into a security headache. To give them that access, you usually have to:</p><ul><li>Navigate through complex IAM roles.</li><li>• Grant console access that they don’t really want (and you don’t really want them to have).</li><li>• Risk the “oops” moment where someone accidentally clicks the wrong button in a production environment.</li></ul><p>It feels like using a sledgehammer to crack a nut. Why should a developer need to understand the entire Cloud Console just to interact with one specific resource?</p><p>The Security vs. Velocity Struggle</p><p>As Platform Engineers and SREs, we want to say “yes” to our teams. We want them to move fast. But our primary job is to keep the gates locked. This creates a friction point:</p><ol><li>Developers get frustrated by the “red tape” and waiting times for permissions.</li><li>2. Infra teams get bogged down by repetitive manual tickets for simple access requests.</li></ol><p>I started thinking: What if we could decouple the data from the platform? What if a developer could get exactly what they need — and nothing more — without ever logging into a cloud provider’s UI?</p><p>Introducing Anveesa Vestra(called: Vestra): Cloud Access, Simplified</p><p>That frustration is exactly why I decided to build Vestra</p><p>I wanted to create a solution where developers no longer need to touch the Cloud Console for routine tasks. It’s a tool designed to bridge the gap between infrastructure security and developer productivity.</p><p>With Vestra, you can:</p><ul><li>Self-serve access: Get instant, scoped-down access to specific buckets.</li><li>Stay out of the Console: Perform necessary tasks through a clean, dedicated interface.</li><li>Zero-Trust by default: Maintain high security standards without the manual IAM overhead.</li></ul><h3>Give it a Spin!</h3><p>I didn’t just build this for myself — I built it for the community. If you’ve ever felt the headache of over-complicated IAM policies or just want a cleaner way to handle resource access, I’d love for you to try [Tool Name].</p><p>It’s currently in its early stages, and your feedback is what will help it grow. Whether you’re an SRE looking to offload some tickets or a Developer who just wants to get their work done, this is for you.</p><p>How to get started:</p><ul><li>Check the docs: https://github.com/PandhuWibowo/anveesa-vestra</li></ul><p>I’m really excited to see how this helps your workflow. Don’t be shy with the feedback — the “bugs” are just features I haven’t finished yet! 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ab6fdb1f869" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/developer-now-no-need-access-cloud-anymore-6ab6fdb1f869">Developer now no need access Cloud anymore</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why We Ditched NPM for PNPM?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">(And how we reclaimed 20 minutes of our lives every day)</p><p class="medium-feed-link"><a href="https://blog.devgenius.io/why-we-ditched-npm-for-pnpm-e8296257c694?source=rss-f36a1987a51e------2">Continue reading on Dev Genius »</a></p></div>]]></description>
            <link>https://blog.devgenius.io/why-we-ditched-npm-for-pnpm-e8296257c694?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8296257c694</guid>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[npm]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Sun, 01 Feb 2026 14:08:25 GMT</pubDate>
            <atom:updated>2026-06-30T14:53:25.239Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Introducing go-devops-cutter: A Golang Toolkit to Make DevOps Life Less Painful]]></title>
            <link>https://blog.devgenius.io/introducing-go-devops-cutter-a-golang-toolkit-to-make-devops-life-less-painful-1593f0936961?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1593f0936961</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Sat, 29 Nov 2025 03:48:11 GMT</pubDate>
            <atom:updated>2026-03-24T15:20:23.978Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Before we begin, a quick note:<br> <strong>go-devops-cutter is still in its early stage of development.</strong><br> The core idea, architecture, and initial implementations are in progress, and the project will <strong>go live publicly in the near future</strong>.</blockquote><blockquote>This article is a preview — an introduction to the problem space, why the project exists, and what it aims to solve for the DevOps community.</blockquote><p>DevOps is often described as automation, simplification, and enabling developers to move faster.<br> But if you’ve worked long enough in the field, you know the reality is messier: countless manual tasks, repetitive requests from developers, and complicated infrastructure setups that get in the way of productivity.</p><p>This project — <strong>go-devops-cutter</strong> — was born from those day-to-day frustrations.</p><p>As someone managing cloud operations and infrastructure, I wanted an open-source tool to cut down the repetitive, time-consuming tasks. Tasks that shouldn’t require manual SSHing, searching logs for hours, or transferring files through jump hosts.</p><p>So I built <strong>go-devops-cutter</strong>.</p><h3>🌱 Why I Built This Project</h3><p>After years as a Cloud/DevOps Engineer, I ran into three recurring issues that slowed down both developers and the operations team. Here’s what pushed me to start this open-source project.</p><h3>🔥 1. Developer Database Requests Are Always Painful</h3><p>In my environment, database servers are placed inside a <strong>private network</strong> (for security reasons).<br> This means developers cannot directly access the database from their local machine.</p><p>So what do they do?</p><p>They ask me for:</p><ul><li>A fresh <strong>database backup</strong></li><li>Or a specific slice of the data they need for local development</li></ul><p>This sounds simple, but there are <em>two tricky scenarios</em>:</p><h3>Scenario A — Database installed directly on a VM or Cloud RDS</h3><p>It’s straightforward, but still takes time to run backups and securely deliver the file.</p><h3>Scenario B — Database running inside containers</h3><p>This is where things get messy:</p><ul><li>I need to <strong>enter containers</strong> manually</li><li>If connection is private, I can’t SSH in from local</li><li>I must <strong>SCP to a jump host</strong> first</li><li>Then transfer the file from jump host to my machine</li><li>Then give it to the developers</li></ul><p>All of this… just for a database dump.<br> Too much unnecessary effort, too repetitive, too slow.</p><p>This project aims to <strong>automate those workflows</strong>.</p><h3>🔥 2. Developers Always Ask for Logs — Sometimes Months of Them</h3><p>Another common request:</p><blockquote><em>“Mas, minta log dari tanggal X sampai tanggal Y dong.”</em></blockquote><p>Logs might be on a VM, or inside containers, or behind private networks.<br> And sometimes they want <strong>two months</strong> of logs.</p><p>Manually finding them, filtering by date, extracting them, and sending them is time-consuming.</p><p>I needed a tool that could:</p><ul><li>Access logs no matter where they’re stored</li><li>Extract log slices by date range</li><li>Ship them out to the requester safely</li><li>Do it all from a single CLI/API</li></ul><p>This is the second pillar of go-devops-cutter.</p><h3>🔥 3. Managing Database Access for Multiple Developers With Different Roles Is a Nightmare</h3><p>Every developer needs different access levels:</p><ul><li>Read-only</li><li>Read-write</li><li>Full admin</li><li>Or access to specific databases only</li></ul><p>With many databases across environments, manually managing credentials is slow and prone to mistakes.</p><p>I wanted a simple interface to:</p><ul><li>Create database users with defined roles</li><li>Assign them to one or many databases</li><li>Rotate credentials</li><li>Revoke or disable access</li><li>Do it <strong>programmatically</strong> and consistently</li></ul><p>This is the third use-case that inspired this project.</p><h3>🚀 What Is go-devops-cutter?</h3><p><strong>go-devops-cutter</strong> is a Golang-based DevOps toolkit designed to solve the three problems above:</p><h3>✔ Fast database backup extraction (VM / RDS / containers)</h3><h3>✔ Log slicing by date ranges</h3><h3>✔ Database access management automation</h3><p>It’s designed to be:</p><ul><li><strong>Lightweight</strong></li><li><strong>Fast (thanks to Go)</strong></li><li><strong>Secure</strong></li><li><strong>Easy to integrate with existing infrastructure</strong></li></ul><p>And most importantly:<br> <strong>To save DevOps engineers hours of repetitive manual work.</strong></p><h3>🧩 Architecture and Design Principles</h3><p>The project follows simple principles:</p><h3>1. One command, one job</h3><p>Each command solves a specific DevOps pain point without introducing complexity.</p><h3>2. Works with multiple environments</h3><p>Whether your DB lives on a VM, in RDS, or inside a container, the tool adapts.</p><h3>3. No direct network exposure</h3><p>It respects private networking and secure tunneling policies.</p><h3>4. Open source and extensible</h3><p>Anyone can contribute plugins, handlers, or providers.</p><h3>🛠 What’s Coming Next</h3><p>This project is still evolving, but planned features include:</p><ul><li>Database backup scheduling</li><li>Automated backup distribution</li><li>Multi-cluster log search</li><li>Support for more databases (MySQL, MongoDB)</li><li>REST API for integrations</li><li>CLI improvements</li><li>Secrets management integration</li></ul><h3>🔗 Repository</h3><p>If you want to explore, contribute, or follow the progress of this early-stage open-source project, check out the repo here:</p><p>👉 <a href="https://github.com/PandhuWibowo/go-devops-cutter"><strong>https://github.com/PandhuWibowo/go-devops-cutter</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1593f0936961" width="1" height="1" alt=""><hr><p><a href="https://blog.devgenius.io/introducing-go-devops-cutter-a-golang-toolkit-to-make-devops-life-less-painful-1593f0936961">Introducing go-devops-cutter: A Golang Toolkit to Make DevOps Life Less Painful</a> was originally published in <a href="https://blog.devgenius.io/">Dev Genius</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dilema Antara Cost Bengkak atau Performa Gitu Gitu Aja Tapi Costnya Murah Meriah]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://pandhuwibowo.medium.com/dilema-antara-cost-bengkak-atau-performa-gitu-gitu-aja-tapi-costnya-murah-meriah-b5f791b7f481?source=rss-f36a1987a51e------2"><img src="https://cdn-images-1.medium.com/max/2600/1*j9653mBEYDhemK2DkdX9ug@2x.jpeg" width="3024"></a></p><p class="medium-feed-link"><a href="https://pandhuwibowo.medium.com/dilema-antara-cost-bengkak-atau-performa-gitu-gitu-aja-tapi-costnya-murah-meriah-b5f791b7f481?source=rss-f36a1987a51e------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandhuwibowo.medium.com/dilema-antara-cost-bengkak-atau-performa-gitu-gitu-aja-tapi-costnya-murah-meriah-b5f791b7f481?source=rss-f36a1987a51e------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5f791b7f481</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[habit-building]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[financial-planning]]></category>
            <dc:creator><![CDATA[Pandhu Wibowo]]></dc:creator>
            <pubDate>Sat, 08 Nov 2025 04:39:32 GMT</pubDate>
            <atom:updated>2025-11-08T04:39:32.729Z</atom:updated>
        </item>
    </channel>
</rss>