inssein

Currently only Postgres and MySQL.

It is currently closed source. The documentation repo is what I am currently using as a temporary website.

Fair feedback. That said, a lot of SaaS companies exists today which require a database connection in order to operate. They all also offen on-prem, but for enterpise sales only.

Everything I have is fairly automated so I think it'd be trivial to offer an on-prem version at some point, but currently still figuring things out.

As another idea, since all the changes are described in an AST, I could offer a "undo" in the query log for INSERT action. The UPDATE action would require a bit more work as I don't track the previous data (and it could be changed in another system as well).

Every action against a data source is logged and query-able.

At my current startup, giving acess to everyone at the company to use a traditional tool (dbeaver, datagrip, etc) is not simple because our databases are not publically accessible. This means every employee would need an ssh key to a bastion, and our onboarding / offboarding process would involve adding / delete users constantly.

With Aidmin, they can invite users to their workspace and utilize Signle Sign-On for added security.

That is exactly my early goal.

Currently, the column based access should help limit modifications to only specific columns. That said, I have heard this feedback and definitely have started thinking about an approval / pull request based workflow.

I was surprised that Mike Krieger (Cofounder & CTO of Instagram) spends ~30 hours a week coding.

It doesn't seem like most CTO's, especially at big companies do a lot of coding anymore.

Still pretty early, but I am working on a web based database editor that has a lot of other niceties built on top (column based permissioning + rbac).

https://app.aidmin.io

Not really defending Dyson, but they have a public statement on CADR, and also just a note that CBC reviewed the older model.

https://www.dyson.co.uk/air-treatment/purifiers/CADR

Might want to elaborate a bit.

It is true that from a feature point of view, Elastic's own offering wins out, but from a perspective of uptime, cost, and performance, AWS wins.

Agreed.

We actually were customers of Elastic's offering for a while, but they went down 3 times in a quarter, which was simply unacceptable. We had to switch, and have been okay since. Our bill is also more than half of what it used to be.

The AWS implementation is quite limited in many ways, and there could be a point where we switch back or host it ourselves.

> A great alternative to Auth0, Firebase Auth and AWS Cognito

Can you elaborate a bit on how it's a great alternative, or what is different?

I agree in principal that we need to make that simple. React can work without a compiler, but it wouldn't be as pleasant without JSX. Same goes for the rest of the stack, there are so many DX improvements in either using SVGs as components, or simply the dev profiling / debugging.

ElasticCo's offering is no better, and has its own shortcomings. The biggest shortcoming is its actually not multi-az. We were down 3 times in 2018, and unfortunately had to switch to AWS ESS. Majority of their outages were also faults of their load balancer.

We've had a few of the problems described here, but so far its better then being down.

SEDNA Systems | Vancouver, BC | Full Time | ONSITE | https://www.sedna.com

We are looking for a Senior Frontend Developer who has experience with React, Redux, and Typescript.

More details can be found at https://sednasystems.bamboohr.com/jobs/view.php?id=19

Quickly skimmed this.. how is comparing Cloud Spanner to a VM running MySQL comparable?

Ramadan was my most productive month last year (hard to measure this year as I started at a new job just before Ramadan). There are no food related distractions (no thinking about lunch, getting up for water, going to the washroom, etc). The key was adjusting my schedule a little bit (start work later) to ensure you get enough proper sleep.