TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: How many of you open up your production DBs to internal users?

1 点作者 lunarcave4 个月前
I know all the reasons why this isn&#x27;t a good idea, but everywhere I&#x27;ve worked, people do it to prevent ad-hoc requests from people who don&#x27;t have access.<p>My feeling is that this is a &quot;open secret&quot; that most SMBs do it, but I&#x27;m keen to hear:<p>1. Whether you &#x2F; your company does it 2. If you avoided it, how did you do that

4 条评论

cebert4 个月前
We can’t do this in the industry I work in. We’re subject to regulatory compliance requirements like SOC2, FedRamp, and CJIS. If an auditor found that access to production databases wasn’t limited on a per-need basis and that access was audited, we’d face significant consequences.
评论 #42799334 未加载
gregjor4 个月前
No direct access, but we have a custom report builder tool in the (internal) web app that lets users write SQL queries (SELECT only) against a read-only replica of the production database. They can name and save those, even put them in their navigation menu.
评论 #42799309 未加载
tianzhou4 个月前
Check out Bytebase which handles all human-to-db operations (schema change, ad-hoc change, ad-hoc query). Disclaimer: I am the co-founder.
keyurishah4 个月前
we have opened up in read only mode. new fancy name is &quot;self serve analytics&quot;
评论 #42799344 未加载