HN user

sourcesmith

98 karma
Posts1
Comments48
View on HN
Why NoSQL 5 years ago

If you want to include Postgres jsonb columns in that then a partial index of the expression of a NOT of the jsonb contains jsonb operator.

Why NoSQL 5 years ago

> Their section on reliable replications can be resolved by keeping a log of the changes made to the database rather than a log of the queries.

You'd need to define a representation of that log, which ends up being equivalent to writing a NoSQL datastore.

I think this covered by relational DBs redo/rollback/write-ahead log; whatever you want to call it.

There were a lot of Y2K related tasks in the course of many developers generally activity. Where I worked at the time, there were not developers solely dedicated to Y2K work. The Y2K issue pretty much caused an employment boom for software developers though.

In reality, that would be GET /user GET settings; the cost for the unneeded associated fields at that point of time is typically not significant for many backends as they stored in aggregate and text based responses compress well.

If the data is not particular dynamic then you can cache the entire representation deriving a future benefit.

Graph base queries tend to lend themselves to adhoc query patterns and I would be concerned about unpredictable patterns of loading. If the backend store is distributed then graph QL looks more attractive to me. If the datastore stores related attributes in aggregate there seems to be little benefit since different parts of an adhoc graph would different levels of 'cachability'.

I have found an application for GraphQL in storing soft-defined triggers or other criteria on data.

I think this has already been addressed by the sibling comment to my question. Insulation does not have to impermeable. Its purpose to prevent the loss of air carrying heat with it, not the transfer of moisture/humidity.

I suspect GDPR would have been sufficient threat since not all people involved in a scanned email were guaranteed to be Gmail users, so gaining consent would have been problematic.

ORMs Are Backwards 7 years ago

Same. When writing complex queries, Hibernate just got in the way. MyBatis just lets you map any result set to objects as you see fit. I also make use non-standard features such as GIS, gin basesd queries, arrays and json in Postgres and this is just easier with MyBatis since I am still writing the queries in SQL. Performance seemed better too.

No but they help. You can find figures of a 15%-38% reduction in bugs for TypeScript versus JavaScript. So that does not consider the additional effect of strong versus weak typing.

Java 12 7 years ago

Bad decisions can be made using any technology. Java has a lot of crufty legacy APIs because, well it has a legacy. I gave up using JSPs years ago for Freemarker. I now use Vert.x rather than servlet contains which gives me a node.js environment but with access to the Java ecosystems and basic things like mature logging frameworks, as well as more advanced features (oh and multithreading in a single process).

Despite Spring being Enterprise it still scales down to simpler apps pretty well due to its modularity.

These can be build into a single jar app that is easy to build and deploy, and combined with a database migration library, maintain their own database schemas. Very, very usable.

Yes, I probably would not use Java on the frontend unless it was for a technical audience.