Live data from Hacker News

“It's The Future”

circleci.com

301–310 of 536 posts

Re: “It's The Future”

#301
post #202

"-No, look into microservices. It’s the future. It’s how we do everything now. You take your monolithic app and you split it into like 12 services. One for each job you do. That seems excessive" A 100 times yes. We tried to split our monolithic Rails app into micro-services built in Go. 2 years and many fires later, we decided to abandon the project. It was mostly because the monitoring and alerting were now split in…

Yeah, we do micro services, the "real" kind. Not the "SOA with a new name kind", but the "some services are literally a few douzan lines of code and we have 100x the amount of services as we do devs" kind. The thing is, you need a massive investment in infrastructure to make it happen. But once you do, its great. You can create and deploy a new service in a few seconds. You can rewrite any individual service to be la…

Building Microservices needs discipline, an eye to find reusable components and extracting them and as you said, investment in infrastructure.

Monoliths invariably tend to become spaghetti over time, and completely impossible to any non trivial refactoring. With microservices, interfaces between modules are stable and spaghetti is localized.

Re: “It's The Future”

#302
Well I think that people and developers in particular needs to start realising that companies like docker has gotten really good at marketing them selfs towards them. Most of the stuff you hear about a technology is just marketing stuff that makes you sound smart when telling your peer about a new technology.

Re: “It's The Future”

#303
There was a time when Heroku seemed just as foreign to me as Docker does in this article.

- So shared webhosting is dead, apparently Heroku is the future?

- Why Ruby, why not just PHP?

- Wait, what's Rails? Is that different from Ruby?

- What's MVC, why do I need that for my simple website?

- Ok, so I need to install RubyGems? What's a Gemfile.lock? None of these commands work on Windows.

- I don't like this new text editor. Why can't I just use Dreamweaver?

- You keep talking about Git. Do I need that even if I'm working alone?

- I have to use command line to update my site? Why can't I just use FTP?

- So Github is separate from Git? And my code is stored on Github, not Heroku?

- Wait, I need to install both PGSql and SQLite? Why is this better than MySQL?

- Migrations? Huh?

Re: “It's The Future”

#304
post #191

Earlier quoted context omitted.

As long as the database isn't relational, I guess.

10M rows in a relational database is a very low number (depending on the size of the row of course).

I know, it was a sarcastic follow up to the "now they have big data" part of the original comment.

"SQL doesn't scale". It needs to be in Mongo or whatever NoSQl database is in right now. I have heard all sorts of nonsense regarding "big data" in the last few years.

Re: “It's The Future”

#305

"-No, look into microservices. It’s the future. It’s how we do everything now. You take your monolithic app and you split it into like 12 services. One for each job you do. That seems excessive" A 100 times yes. We tried to split our monolithic Rails app into micro-services built in Go. 2 years and many fires later, we decided to abandon the project. It was mostly because the monitoring and alerting were now split in…

> Any positive experiences with micro-services here?

I'm currently working on a large refactoring effort along these lines. The end goal is to create a modular, potentially distributed system that can be deployed in a variety of configurations, updated piecemeal for different customers, and integrated by our customers with the third-party or in-house code of their choice using defined APIs. We aren't typical of the other examples, though, in that we do literally ship our software to our customers and they run it on their own clusters.

Re: “It's The Future”

#306
post #244

Earlier quoted context omitted.

> But sometimes it's also very easy to please people. Big data: just insert 10M records in a database and suddenly everyone is happy because they now have big data :| Since when is 10M records is considered big data? My goto gauge for big data is that it can't fit in memory on a single machine. And since that means multiple TB[1] these days, most people don't really have big data. [1]: *Heck you can even rent ~2TB fo…

I'd say if it can't fit in RAM, but still can fit on a single SSD it doesn't count as big data either

Not sure how accurate that is, since you can buy 60TB SSDs these days.

Re: “It's The Future”

#307

Earlier quoted context omitted.

10 million rows in a relational database doesn't need to be bad nor is it big data. Rows is a bad measure of "big" when it comes to data. A measurement of bytes and probably more specifically bytes per field and how many fields the records have, as this gives a better indication into the way this will be written and potentially searched. 10 million rows of 5 integer values is pittance for any relational database wort…

Someone once suggested to me that 'big data' begins when it doesn't fit in RAM in a single rack any more.

That's soon going to be on the order of 100 terabytes, so there will be only a handful of companies doing big data ;-)

Re: “It's The Future”

#308
post #62

"Why don’t I just use Google’s thing? "-You think that’s going to be around in 6 months?" Isn't reputation a thing of beauty?

So true. Why people often use "it's backed by Google" as an argument in favor of anything is beyond me.

"it's backed by Google" is the reason I avoided Go for years and is still the only reason I'm nervous using it.

Re: “It's The Future”

#309
post #165
post #17

Obligatory link to "The S stands for simple", a SOAP-bashing classic: http://harmful.cat-v.org/software/xml/soap/simple

If that was ever true it certainly doesn't seem to be true now. All the tools support WSDL-first. All the tools are compatible with each other. Fill in the URL, let it autogenerate the interface, write your code and it all just works.

Because it was the latest trend 10+ years ago, and now people have made it just work because their applications are all built on it and people need actually good tools to use these architectures. It's always about tools, it's not like TCP is the best protocol or anything, it just has the best tooling, ditto for C, POSIX, etc. anything can be a good standard after 15+ years of work on it. Containers will be like that in a couple of years. It's all just cycles man.
Post reply on HN