Live data from Hacker News

Relational databases aren’t dinosaurs, they’re sharks

simplethread.com

131–135 of 135 posts

Re: Relational databases aren’t dinosaurs, they’re sharks

#132
post #99

Earlier quoted context omitted.

The type should always include provisions for manual fixes. IMO such an address type should even include a provision for manual geocoding for cases where automated geocoding fails ("This is how I write it, and this is where it's located").

In that case, whats the value of the system? 99% of the time an address is just a “unique” opaque identifier. You ingest the address, then you print it on the parcel. You avoid manipulating or trying to interpret it too much. A system that attempts to codify address to a standard that can’t express all addresses (including their nuance) is useful. You can’t trust any analytics created from it, because by its nature,…

Well, in my case, analytics for planning/scheduling of operations. I need to figure out which service points to cluster together. I need to point out that I specifically don't deal with parcels. Occasional individual outliers (some of these points DO need specifically GPS coordinates because occasionally there's an item like "the side of a shed on a parking lot", where the parking lot doesn't have a postal address) can be dealt with, but having, say, 99.5-99.9% ("best effort") systematization is very useful, especially when looking at how to migrate former units of work (which might involve fighting some organizational structures in a large national company). Without this it's impossible for me for example to estimate the objective function difference between a system that routes operations completely arbitrarily with optimal route length and a system that uses somewhat sub-optimal routes but with vastly lesser "human complexity"; for example, with routes spanning a small set of roads) that doesn't need that much automation (a paper list of locations in order - the status quo of the former system).

> The most important thing to recognise is that any arbitrary address will fit many different address conventions, but each of those conventions will result in a different location.

In my case it definitely should not do that, even with different conventions. Maybe that's one of those international things.

Re: Relational databases aren’t dinosaurs, they’re sharks

#133
post #129

Earlier quoted context omitted.

Oh My God

We've banned this account for repeatedly posting unsubstantive comments and ignoring our request to stop. If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html .

It doesn’t seem like I’m banned

Re: Relational databases aren’t dinosaurs, they’re sharks

#134
post #81
post #26

Another consideration is that, at scale, no sql is way cheaper. I run a service with approx. 900k daily users, each generating about 210 object writes and reads that need to execute within 50ms, and I am running this on firestore for about $350 a month, incl. Elb, waf, regionally replicated compute, managed NLP and translate. I sync the no sql stuff to bigquery for analytical usage. Cheap, and scales without any prob…

> Another consideration is that, at scale, no sql is way cheaper. Define "scale" and "cheaper". I have some SQLite databases that are chewing through over 1K writes per second in production (WAL=on). Many of our transactions resolve within 10-100 microseconds because the application process and the database process are the same thing. SQLite seems to be one of the cheapest options available, being totally free and of…

I have some SQLite databases that are chewing through over 1K writes per second in production (WAL=on).

Is that with synchronous full(2) or normal(1)?

What's your SQLITE_THREADSAFE mode?

Re: Relational databases aren’t dinosaurs, they’re sharks

#135
post #129

Earlier quoted context omitted.

We've banned this account for repeatedly posting unsubstantive comments and ignoring our request to stop. If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html .

It doesn’t seem like I’m banned

Comments by banned users still go through, but they're only visible to you and any other users who have "showdead" turned on in their profile.

If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html.

Post reply on HN