Hacker News new | past | comments | ask | show | jobs | submit login
CloudBeaver – Database Management from Browser (cloudbeaver.io)
101 points by thunderbong on April 11, 2021 | hide | past | favorite | 11 comments



Any relation to https://dbeaver.io/?


Yes, this is from the same group https://github.com/dbeaver/cloudbeaver


Great! DBeaver is absolutely wonderful software, and I hope Serge and his team have amazing success with CloudBeaver.


I came across beaver.io only yesterday and I am already impressed. It was likely that this project was related IMHO.


I have still been using Adminer[0] via a docker image to quickly run an admin interface in a browser.

This looks a lot nicer. I remember the DBeaver name but I've not used it in a long time. I'll be using this instead of Adminer on my next project to give it a whirl.

[0] https://www.adminer.org


Adminer is super convenient, as it fits in single php file.


This is great! DBeaver has always been my favorite DB management tool, being able to run it as a server in a container is fantastic.

When trying to get a remote admin UI for SQLite databases I always had trouble for one reason or another, cloudbeaver may be a good alternative. I'm just a bit sad entity diagrams are not part of the free edition.


The AWS integration in the Enterprise Edition sounds interesting. I'm definitely going to try that out.


Seems useful for some quick administration, but I can't see this replacing a proper desktop application. With the number of results some of my data exploration queries come back with, Firefox would fall over and die.


What is the benefit of going from desktop application to web browser? (DBeaver to CloudBeaver)


You can deploy the browser version with a Docker container in a remote server. With that, instead of running the client in your computer and connecting to the remote database, you can have the client running as a service in your servers. Then you can use all the DBeaver functionality (whatever they are providing in the browser version) by just navigating to it (the desktop application is quite heavy).

Apart from that, I guess that from a team's point of view, you have better control of the database access than if you had to whitelist IPs. Now you can have the same access control policies in your database client than for any other service you are running. Yes, you could do the same by using the native database permissions systems, but it's just a use case I think of.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: