Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Elasticsearch was never a database

paradedb.com

Post reply on HN
Print view View original

71–80 of 109 posts

Re: Elasticsearch was never a database

#71

Post by almosthere »

bigfatkitten wrote: post #51
victor106 wrote: post #31

Earlier quoted context omitted.

> Accenture They messed up a $30 million dollar project big time at a previous company. My cto swore to never recommend them

How are they still in business? I’ve either been involved with or adjacent to dozens of Accenture projects at 5 companies over the last 20 years, and not a single one had a satisfactory outcome. I’ve never heard a single story of “Accenture came in, and we got what we wanted, on time and on budget.” Cases of “we got a minimum viable solution for $100m instead of $30m, and it was four years late” seem more typical.

It's just that they're only seeing money to build and a place to make excuses on being late.

If you hire your own people you can make them feel how well the business is doing and get features out the door tomorrow and build to the larger thing over time.

Re: Elasticsearch was never a database

#72

Post by nwallin »

9rx wrote: post #47
victor106 wrote: post #31

Earlier quoted context omitted.

> Accenture They messed up a $30 million dollar project big time at a previous company. My cto swore to never recommend them

I've seen some mess-ups in my life, but they started sticking out like a sore thumb long, long, long, long before anywhere close to $30 million was spent on it. What does a $30 million dollar mess-up look like?

I am not OP and am not speaking for them.

"A $30 million mess-up" can look like (at least) two things. It can be $30 million was spent on a project that earned $0 revenue and was ultimately canceled, or it can look like $x was spent on a project to win a $30 million contract but a competitor won the contract instead.

Re: Elasticsearch was never a database

#73

Post by zbentley »

rpdillon wrote: post #56
_joel wrote: post #27

Earlier quoted context omitted.

MySQL isn't mine either, it's Larry Ellison's.

Well, "My" is the name of the author's daughter, rather than a reference to who owns it.

> Larry Ellison ... who owns it.

> who

Do not fall into the trap of anthropomorphizing Larry Ellison!

https://www.youtube.com/watch?v=-zRN7XLCRhc&t=2300s

Re: Elasticsearch was never a database

#74

Post by aPoCoMiLogin »

kubi07 wrote: post #40
speedgoose wrote: post #11

Accenture managed to build a data platform for my company with Elasticsearch as the primary database. I raised concerns early during the process but their software architect told me they never had any issues. I assume he didn’t lie. I was only an user so I didn’t fight and decided to not make my work rely on their work.

I worked in a company that used elastic search as main db. It worked, company made alot of money from that project. It was a wrong decision but helped us complete the project very fast. We needed search capability and a db. ES did it both. Problems that we faced by using elastic search: High load, high Ram usage : db goes down, more ram needed. Luckily we had ES experts in infra team, helped us alot.(ecommerce compan…

most of these is more lack of experience than the DB fault. most systems have its quirks, so you have to get used to it.

Re: Elasticsearch was never a database

#75

Post by aPoCoMiLogin »

cluckindan wrote: post #13

”That means a recently acknowledged write may not show up until the next refresh.” Which is why you supply the parameter refresh: ”wait_for” in your writes. This forces a refresh and waits for it to happen before completing the request. ”schema migrations require moving the entire system of record into a new structure, under load, with no safety net” Use index aliases. Create new index using the new mapping, make a r…

it's the other way around: `wait_for` waits for the next refresh (there is configurable refresh interval, 1s by default), `refresh: true` forces refresh without waiting for the next refresh interval.

the difference is that waiting for refresh assures that the data will be available for search after the "insert" finishes. forcing refresh might be foot gun that will criple the servers.

Re: Elasticsearch was never a database

#76

Post by marcosdumay »

Quarrelsome wrote: post #58
lvspiff wrote: post #5

Everything is a database if you believe hard enough Feel like the christmas story kid -- >simplicity, and world-class performance, get started with XXXXXXXX. A crummy commercial?

ram is a database, you just need bigger capacitors.

That's literally the original MySQL philosophy.

And it was good for a lot of things.

Re: Elasticsearch was never a database

#77

Post by 1_1xdev1 »

unethical_ban wrote: post #3

I work in infosec and several popular platforms use elasticsearch for log storage and analysis. I would never. Ever. Bet my savings on ES being stable enough to always be online to take in data, or predictable in retaining the data it took in. It feels very best-effort and as a consultant, I recommend orgs use some other system for retaining their logs, even a raw filesystem with rolling zips, before relying on ES un…

You have to slap something durable and a queue in front of it.

Elastic’s own consultants will tell you this …

Re: Elasticsearch was never a database

#78

Post by rawgabbit »

9rx wrote: post #47
victor106 wrote: post #31

Earlier quoted context omitted.

> Accenture They messed up a $30 million dollar project big time at a previous company. My cto swore to never recommend them

I've seen some mess-ups in my life, but they started sticking out like a sore thumb long, long, long, long before anywhere close to $30 million was spent on it. What does a $30 million dollar mess-up look like?

Teams of consultants on site, some remote, and many offshore. Tons of documents are created and many environments and DevOps pipelines are stood up. First code release is when the people who push buttons touch the system for the first time. It is crap. Several more code releases attempt to make the system usable. Eventually another consultant or two are brought to evaluate the project and they say the project violated every best practice and common sense rule. Most egregiously the internal stakeholders who voiced serious concerns at the beginning of the project were dismissed or forced out etc.

Re: Elasticsearch was never a database

#80

Post by rpdillon »

zbentley wrote: post #73
rpdillon wrote: post #56

Earlier quoted context omitted.

Well, "My" is the name of the author's daughter, rather than a reference to who owns it.

> Larry Ellison ... who owns it. > who Do not fall into the trap of anthropomorphizing Larry Ellison! https://www.youtube.com/watch?v=-zRN7XLCRhc&t=2300s

Thanks, made my day
Post reply on HN