HN user

stickupkid

33 karma

Software engineer at Canonical. Currently working on the Juju project.

Posts0
Comments26
View on HN
No posts found.

Ignoring Postgres and comparing apples to apples, rqlite has limitations on "safe" SQL statements[1]. This might be a big deal breaker for you than it might for others. As dqlite replicates the pages and not the SQL statements over raft, which means dqlite doesn't have _that_ problem. Using random() and now() are classified as non-deterministic[2].

Using the application to send the time, although not idea could be used as a workaround, but attempting to use non-deterministic functions in triggers becomes a lot harder.

1. https://github.com/rqlite/rqlite#limitations 2. https://www.sqlite.org/deterministic.html

Some are mentioned in the post but I can think of secret management

Hashicorp Vault seamless integration.

In order to supply those needs in Nomad you'll need to spend time finding out how to integrate different solutions, keep them up-to-date, etc

Like how k8s secrets are secure out of the box ?

This isn't highlighted high enough, and the lack of what makes a good PR that shows new contributors the best way forward isn't shown enough.

Yet I standby my statement, you're not blameless here.

(parent post tried to abolish blame and called out the grandparent post as the issue, hence why the lack of continuation)

I don't, you messed up!

The fact that you're actually incentivising contributors to make PRs of any quality and without standards, whilst forcing the burden on to maintainers (without reward) and you do very little (no tutorials about how to make quality PRs, no standards information on what comprises of a good PR, no quality guidance what so ever!).

This seems like a marketing stunt that has backfired and you're saying that you don't deserve some backlash?

I feel the lack of additional type arguments on methods will be considered a mistake in the longer term. Although the way it's designed it can be added in additional revisions but considering it's taken rather a long time to get here, I don't hold much hope for it landing for some time.

Attempting to define a generic Map function turns out to be somewhat troublesome[1]. This would be really painless if you had type arguments, instead, we have to define an interface to allow peeping into the type and creating a type from a zero value.

Don't get me wrong, I do applaud the efforts for better type system, it's just a weakness in the proposal.

1. https://go2goplay.golang.org/p/P7CVwOW9wig (note this panics currently)

It really can (LXD cloud setup from personal experience), the problem is that if you don't serialise your writes then yeah, fun times to be had. There are compromises for all databases. People just like telling others their opinion as fact, and how wrong everybody is apart from themselves of course.

Go Creeping In 7 years ago

Working as part of Juju project, I can tell you for certain that the answer here is yes, very much so.