TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

“It's The Future”

1323 点作者 knowbody将近 9 年前

86 条评论

rajeshp1986将近 9 年前
The article perfectly summarizes my frustration and sentiment. These days I hear these buzzwords all time. I work as a consultant for an enterprise product and most people whom I meet they somehow catch these buzzwords and blurt it out in front of everyone during meetings and discussions to either showoff that they know technology and things that are in the market these days(also latest iphone, apple news, tesla, space exploration and what not) or I feel they are somewhat trying to hide their insecurities.<p>Anyway long story short, most of these people do not really understand why they need all this rocket science to manage &lt; 500 internal users. One of the new buzzwords I am hearing these days is mostly related to bigdata and machine learning. One of my managers came to me and asked me why dont we integrate our product with hadoop it will solve the performance problems as it can handle lot of data.<p>I am frustrated by the industry as a whole. I feel industry is simply following marketing trends. Imagine the no. of man-hours are put into investigating technologies and projects dropped mid-way realizing the technology stack is still immature or not suitable for at all.
评论 #12304836 未加载
评论 #12304459 未加载
评论 #12304126 未加载
评论 #12305000 未加载
评论 #12304475 未加载
评论 #12304124 未加载
评论 #12304013 未加载
评论 #12304136 未加载
评论 #12305087 未加载
评论 #12304835 未加载
评论 #12304161 未加载
评论 #12305170 未加载
评论 #12306364 未加载
评论 #12308523 未加载
评论 #12315706 未加载
评论 #12310799 未加载
评论 #12304660 未加载
评论 #12304892 未加载
评论 #12304561 未加载
评论 #12304357 未加载
mrhektor将近 9 年前
&quot;-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.<p>That seems excessive&quot;<p>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 into many different pieces. Also, the team spent too much time debating standards etc. I think micro-services can be valuable, but we definitely didn&#x27;t do it right, and I think a lot of companies get it wrong. Any positive experiences with micro-services here?
评论 #12303587 未加载
评论 #12304327 未加载
评论 #12303653 未加载
评论 #12303798 未加载
评论 #12303629 未加载
评论 #12303619 未加载
评论 #12303639 未加载
评论 #12303764 未加载
评论 #12303945 未加载
评论 #12304372 未加载
评论 #12304065 未加载
评论 #12304802 未加载
评论 #12303609 未加载
评论 #12309283 未加载
评论 #12304779 未加载
评论 #12304163 未加载
评论 #12303906 未加载
评论 #12304494 未加载
评论 #12304022 未加载
评论 #12303748 未加载
评论 #12303582 未加载
评论 #12317440 未加载
评论 #12303757 未加载
评论 #12304683 未加载
评论 #12307483 未加载
评论 #12304649 未加载
评论 #12303946 未加载
评论 #12303735 未加载
pbiggar将近 9 年前
Author here.<p>To answer some questions: yes this is obviously poking fun at Docker, but I also do really believe in Docker. See the follow-up for more on that: <a href="https:&#x2F;&#x2F;circleci.com&#x2F;blog&#x2F;it-really-is-the-future&#x2F;" rel="nofollow">https:&#x2F;&#x2F;circleci.com&#x2F;blog&#x2F;it-really-is-the-future&#x2F;</a><p>In a self-indulgent moment I made a &quot;making of&quot; podcast about this blog post, which is kinda interesting (more about business than tech): <a href="http:&#x2F;&#x2F;www.heavybit.com&#x2F;library&#x2F;podcasts&#x2F;to-be-continuous&#x2F;ep-16-its-the-future&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.heavybit.com&#x2F;library&#x2F;podcasts&#x2F;to-be-continuous&#x2F;ep...</a><p>And if you like this post you&#x27;ll probably like the rest of the podcast: <a href="http:&#x2F;&#x2F;www.heavybit.com&#x2F;library&#x2F;podcasts&#x2F;to-be-continuous&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.heavybit.com&#x2F;library&#x2F;podcasts&#x2F;to-be-continuous&#x2F;</a>
评论 #12306383 未加载
评论 #12306665 未加载
评论 #12307134 未加载
rjvir将近 9 年前
There was a time when Heroku seemed just as foreign to me as Docker does in this article.<p>- So shared webhosting is dead, apparently Heroku is the future?<p>- Why Ruby, why not just PHP?<p>- Wait, what&#x27;s Rails? Is that different from Ruby?<p>- What&#x27;s MVC, why do I need that for my simple website?<p>- Ok, so I need to install RubyGems? What&#x27;s a Gemfile.lock? None of these commands work on Windows.<p>- I don&#x27;t like this new text editor. Why can&#x27;t I just use Dreamweaver?<p>- You keep talking about Git. Do I need that even if I&#x27;m working alone?<p>- I have to use command line to update my site? Why can&#x27;t I just use FTP?<p>- So Github is separate from Git? And my code is stored on Github, not Heroku?<p>- Wait, I need to install both PGSql and SQLite? Why is this better than MySQL?<p>- Migrations? Huh?
评论 #12305681 未加载
评论 #12308353 未加载
nathell将近 9 年前
Obligatory link to &quot;The S stands for simple&quot;, a SOAP-bashing classic: <a href="http:&#x2F;&#x2F;harmful.cat-v.org&#x2F;software&#x2F;xml&#x2F;soap&#x2F;simple" rel="nofollow">http:&#x2F;&#x2F;harmful.cat-v.org&#x2F;software&#x2F;xml&#x2F;soap&#x2F;simple</a>
评论 #12304059 未加载
评论 #12303522 未加载
评论 #12304149 未加载
chukye将近 9 年前
Man, I dont think this is the future at all. OK, Docker is good and has its propose, and is very good on what its do: &quot;Run only one process in one brand new kernel&quot;, but beyond than that, its just a daemon that uses and abuses of linux containers, you can easily scale, but is a pain in the ass to upgrade apps, also you <i>need</i> to run only <i>one</i> process on that. Does not looks like the future for me to have 30 different linux containers running just only one process in each of them, dude, you have a kernel in your hand, why the hell you will run only one process on it? (what the heck, you can protect yourself and scale without be the bitch of a daemon, you just need to know your best friend kernel), you dont need to make micro services for everything, its good ok, but its not the solution for everything like the people are saying...<p>I really dont have any idea why the people are are so excited about &quot;docker&quot; all the things.
评论 #12304165 未加载
评论 #12306210 未加载
评论 #12304248 未加载
评论 #12307568 未加载
epalmer将近 9 年前
I am going to ramble. Just move on if you don&#x27;t care to hear the ramblings of a 62 year old development manager.<p>I&#x27;m pretty docker ignorant. I think I get it in concept. I manage &gt;150 web sites (~15,000 pages total) that are php based with eXist-db and oracle (overkill but forced to use it) for database backends. My team develops on mac os x and pushes code to RHEL. We have never had a compatability problem between os x and RHEL except for some mgmt scripts in bash that were easily coded around.<p>Big data to me is a 400 MB apache log file.<p>I go home grateful I don&#x27;t have to be in the buzz word mix.<p>I do read a lot about technology and over time that informs some changes like using apache camel for middleware, splunk for log file analysis yada dada...<p>I have had bosses that brought me buzz word solutions that don&#x27;t ever match the problems we have. I hate that but right now I am not in that position. My boss leaves technology decisions to us.<p>Least you think we are not modern at all we do use a CDN, git and more.<p>Some days I get anxiety from reading HN, feeling stupid. Some days I get a lift from HN from reading articles like this one and the comments.<p>I am so glad I&#x27;m not in the business of chasing technology.
hoechst将近 9 年前
Please also read the followup (<a href="https:&#x2F;&#x2F;circleci.com&#x2F;blog&#x2F;it-really-is-the-future&#x2F;" rel="nofollow">https:&#x2F;&#x2F;circleci.com&#x2F;blog&#x2F;it-really-is-the-future&#x2F;</a>).<p>I read both articles a year ago and it really helped me grasp the whole container movement.
robteix将近 9 年前
&quot;Why don’t I just use Google’s thing?<p>&quot;-You think that’s going to be around in 6 months?&quot;<p>Isn&#x27;t reputation a thing of beauty?
评论 #12303975 未加载
评论 #12303675 未加载
评论 #12305452 未加载
TickleSteve将近 9 年前
Sometimes it seems the webdev world is unaware of the complexity its creating simply to execute instructions....
评论 #12303787 未加载
评论 #12303506 未加载
lambdacomplete将近 9 年前
There are 2 major issues with this:<p>1) Small teams (~1-5 people) trying to seem &quot;big&quot; by working at Google&#x27;s scale.<p>2) Heroku&#x27;s prices. We are currently (successfully so far) migrating a small Django project from bare Amazon EC2 instances to ECS with Docker. Even using 3 EC2 micro instances (1 vCPU, 1 GB RAM) for the Docker cluster we would spend ~8 USD&#x2F;month&#x2F;instance. With Heroku the minimum would be 25 USD&#x2F;month&#x2F;dyno. That&#x27;s a 3x increase in expenses.<p>It&#x27;s very possible to take advantage of technologies like containers without getting too caught in the hype.
评论 #12303656 未加载
评论 #12304529 未加载
评论 #12304208 未加载
评论 #12303640 未加载
评论 #12303659 未加载
LukeB_UK将近 9 年前
Previous discussion from 434 days ago: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9688383" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9688383</a>
xchaotic将近 9 年前
I think I will be fine, thanks. I&#x27;ll stick to my shell scripts, so far they&#x27;ve outlived any other devops fad.
评论 #12303784 未加载
评论 #12303780 未加载
评论 #12303960 未加载
nickjj将近 9 年前
Or just put your app(s) into containers and run them through docker compose on a single VPS. That bypasses about 99% of the things listed in this article.<p>You can still easily set things up so it&#x27;s a git based deploy which is hands free after the initial push.<p>Now you have a single $5-10&#x2F;month server that runs your app&#x27;s stack without a big fuss. Of course it&#x27;s not &quot;web scale&quot; with massive resiliency but when you&#x27;re just starting out, 1 server instance is totally fine and exactly what you want.<p>I&#x27;ve ran many projects for years on 1 server that did &quot;business mission critical&quot; tasks like accepting payments, etc..
mangeletti将近 9 年前
I wonder if the original HN &quot;Heroku is Dead...&quot; title will cost Heroku money &#x2F; market share in indirect ways.<p>When I see titles like that (despite the fact that it was intended as sarcasm), I think to myself, e.g., &quot;I bet at least hundreds of people who scrolled past it thought it was sincere, and now they will have this subconscious &#x27;Heroku is Dead... Docker...&#x27; thought at times when deploying projects. Maybe they&#x27;ll even check out Docker. Maybe these hundreds of people will represent a tipping point of sorts for Heroku-&gt;Docker migrations, because one of them will write a really great blog post about it, and it will receive thousands of views...&quot; (alternate endings of the same thought continue to be brute-forced for a few moments).<p>Along the same vein of thinking, back in 2008 I had this &quot;realization&quot; that Google could control the world by simply showing results based on headline titles (e.g., a search for &quot;Obama&quot; during the election could have resulted in articles &#x2F; results whose titles have words&#x2F;phrases whose presences are positively correlated to lower or higher stress levels, assumptions, other emotions, etc., resulting in a net positive or negative sentiment, respectively, about the subject of the search query, all while simply scanning the results to determine which one to click).
评论 #12305367 未加载
oneplane将近 9 年前
This pretty much sums it up. New stuff, stacked on existing stuff, with the theory that older stuff was hard, and new stuff is better, but you still needs the old stuff, so you basically end up doing exactly what you did, but now with more stuff in between, adding cost, complexity and additional failure modes while solving nothing.<p>Any of the proposed problems that containerization was supposed to fix are already fixed by using proper configuration management. In almost all cases so far, people yammering on about docker and containers (and CoreOS), it ended up being their idea of configuration management, because they didn&#x27;t have any in the first place.<p>Say you want to fix your &#x27;problems&#x27; with setting up servers, how about doing it the right way. You will need deployment services, regardless of containers, VMs or bare metal. You will also need configuration management services, and monitoring. Containers and special distributions solve none of it, knowledge to run systems is still required and not actually fixing your problems and layering stuff on top of it doesn&#x27;t actually help.<p>Get something like SaltStack or Chef, and configure the <i></i><i></i> out of everything. It doesn&#x27;t care what you&#x27;re running on, and actually solves the problems that need fixing.
nathan_f77将近 9 年前
I&#x27;ve spun up a lot of kubernetes clusters to test it out. A few months ago I also tested out Flynn, Deis, Deis Workflow, Openstack, and a lot of other options. I still haven&#x27;t found a simple bootstrap script that gets everything set up on AWS and lets me simply deploy my application. And it&#x27;s true that storage still seems to be an unsolved problem with kubernetes.<p>Heroku is great, and free for small services. On the other hand, a highly-available kubernetes cluster is going to set you back at least $100 per month, which is just too much for small startups and side projects before they take off.<p>I think I&#x27;m going to forget everything and head towards <a href="http:&#x2F;&#x2F;serverless.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;serverless.com&#x2F;</a>. No Heroku, no Docker, no micro-services, no servers. Just everything running on AWS Lambda and DynamoDB. And everything static in S3 behind Cloudfront.<p>Or maybe just Firebase. But I really am tired of managing servers.
评论 #12303896 未加载
评论 #12305262 未加载
评论 #12303897 未加载
jakozaur将近 9 年前
Thumb rule: Divide number of backend engineers by 5 you get optimal number of micro-services.
评论 #12304530 未加载
评论 #12304608 未加载
lopatin将近 9 年前
I got a genuine laugh out of this quote &quot;Yeah, BDSM. It’s San Francisco. Everyone’s into distributed systems and BDSM.&quot;.
评论 #12304807 未加载
评论 #12304468 未加载
eddd将近 9 年前
Making sort of funny articles about Docker doesn&#x27;t change the fact that circleci&#x27;s support for docker is horrible. I don&#x27;t use it on prod (and I probably won&#x27;t) but since circleci forces me to use ubuntu 12.04 which is not something I use on prod I want a docker container which looks like my production host. Having said that - circle really tries to support docker, but It doesn&#x27;t.<p>I have to use ECS for caching (I am not happy about it)<p>Builds might fail due to the custom docker version&#x2F;compilation<p>You can mock docker, but people are using it in one way or another and you should support it properly.
seanhandley将近 9 年前
This needs a &quot;(2015)&quot; adding to the title.
评论 #12304233 未加载
评论 #12303808 未加载
评论 #12309894 未加载
room271将近 9 年前
Most commenters don&#x27;t seem to realise that this is satirical, and that the author actually thinks Docker is &#x27;the future&#x27;:<p><a href="https:&#x2F;&#x2F;circleci.com&#x2F;blog&#x2F;it-really-is-the-future&#x2F;" rel="nofollow">https:&#x2F;&#x2F;circleci.com&#x2F;blog&#x2F;it-really-is-the-future&#x2F;</a><p>But there is, as the author notes, truth in the satire.
hellofunk将近 9 年前
I assume this entire article is one piece of sarcasm. Because after reading it, how could any sane person not prefer Heroku?
评论 #12303518 未加载
评论 #12304175 未加载
评论 #12304258 未加载
sandGorgon将近 9 年前
show me an easy way to push a rails application to aws (with docker) that uses RDS ?<p>is there ANY way i can spin up a server, add the ssh keys to some configuration file somewhere and just &quot;docker-magic push&quot; and have my rails application running ?<p>or do &quot;docker-magic bundle exec db:migrate&quot; and have that command run on the server.<p>Or push a Procfile with worker definitions and have the PAAS automatically pick it up, add it to supervisord&#x2F;systemd and run it ?
评论 #12303971 未加载
评论 #12303570 未加载
评论 #12303525 未加载
评论 #12303691 未加载
评论 #12303618 未加载
cocktailpeanuts将近 9 年前
Glad to know there&#x27;s the same kind of hipsterism going on in the backend world as much as in the frontend world.<p>You could basically substitute all these backend buzzwords with &quot;Webpack&quot;, &quot;Grunt&quot;, &quot;Gulp&quot;, &quot;Requirejs&quot;, &quot;React&quot;, &quot;Angular&quot;, &quot;Ember&quot;, &quot;Backbone&quot;, etc. and it would have same effect on the readers--they think you&#x27;re an annoying hipster.
joeblau将近 9 年前
<a href="https:&#x2F;&#x2F;www.gitignore.io" rel="nofollow">https:&#x2F;&#x2F;www.gitignore.io</a> runs on Heroku and it gets 40k+ visitors a month on a free Dyno. I use Heroku because I don&#x27;t want an IAAS solution, I want a PAAS solution. If I wasn&#x27;t using Heroku, I would probably find another PAAS, before switching to Docker (even though I do love Docker).
评论 #12303537 未加载
评论 #12303766 未加载
评论 #12303524 未加载
djhworld将近 9 年前
One thing that I liked about Heroku was the ease of deployment for Java applications (or any language for that matter as long as you had the right build pack)<p>Since they upped the cost of their small tier, I moved to Digital Ocean and installed Dokku, which gives me that Heroku-like deployment experience so managing my (admittedly very small) website isn&#x27;t that much of a hassle.
评论 #12303694 未加载
dredmorbius将近 9 年前
In an earlier age, all we had to hate were frameworks.<p><a href="http:&#x2F;&#x2F;discuss.joelonsoftware.com&#x2F;?joel.3.219431.12" rel="nofollow">http:&#x2F;&#x2F;discuss.joelonsoftware.com&#x2F;?joel.3.219431.12</a><p>(Factory factory factory factory.)
nicolas_t将近 9 年前
Out of topic but, man, is coreos not ready for prime time. I&#x27;ve been using it following the stable channel and ended up having to turn off automated updates because it would break docker (docker would just hang with the last 4 updates)... Not a very convincing test of coreos :)
jondubois将近 9 年前
Kubernetes&#x2F;Docker will become increasingly accessible to developers and it will loosen the reliance on lock-in PaaS like Heroku - This is the future; I&#x27;m betting everything on it.<p>With tools like Rancher <a href="http:&#x2F;&#x2F;rancher.com" rel="nofollow">http:&#x2F;&#x2F;rancher.com</a>, you can already see things moving in that direction. Next step is rancher-as-a-service.<p>When it comes to developers, I think open systems will always prevail in the end (it&#x27;s just more flexible).
评论 #12303607 未加载
评论 #12303711 未加载
qwertyuiop924将近 9 年前
Don&#x27;t listen to hype. Look at the problems you need to solve. If you need a big, complex, distributed system, than maybe microservices are a good idea. If you&#x27;re building a simple webapp... not so much. Things that work in the large don&#x27;t necessarily work in the small.<p>I write stuff in Scheme. I&#x27;m a hobbyist, there&#x27;s no reason for me not to, and I love the language. The apps I write are sometimes single-threaded (or coroutine-based) monoliths. But I only have one machine available for me, and the things I&#x27;m writing are fairly simple. It&#x27;s good ENOUGH. And Worse really is Better[1].<p>1:and I truly mean that in the Gabriel sense. As in the New Jersey model. Not any other way.
评论 #12307543 未加载
cerebellum42将近 9 年前
This definitely reflects some of my experiences when trying out Docker and some of the other stuff associated with it.<p>Serious question though: I would absolutely love to have an introduction on how to use Docker to deploy one or two web applications that use a typical amount of backend services, say some sort of database and a redis server. All of this would probably run on a single VM (whether Amazon, DigitalOcean, Linode, ...) and you mainly use Docker to isolate the applications from each other in terms of the environment&#x2F;dependencies that they need.<p>How do I do this with Docker in a way that gets me an easy deploy process? (Or maybe the question is actually, should I even do this with Docker?)
评论 #12309448 未加载
joryhatton将近 9 年前
&gt; 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.<p><i>reader implements and gets massive bill for personal blog hosting</i><p>&quot;Am I doing this right?&quot;
tedmiston将近 9 年前
I guess this is meant to be hyperbolic but honestly it&#x27;s true.<p>&gt; So I just need to split my simple CRUD app into 12 microservices, each with their own APIs which call each others’ APIs but handle failure resiliently, put them into Docker containers, launch a fleet of 8 machines which are Docker hosts running CoreOS, “orchestrate” them using a small Kubernetes cluster running etcd, figure out the “open questions” of networking and storage, and then I continuously deliver multiple redundant copies of each microservice to my fleet. Is that it?<p>&gt; -Yes! Isn’t it glorious?<p>&gt; I’m going back to Heroku.
StreamBright将近 9 年前
What a nice clickbait title. A is better than B, even though A is an apple while B is an orange, and we use them for entirely different purposes. Some functionality provided by Heroku can be replaced with Docker, and some missing features of Heroku are in the Docker infra, that can be added to Heroku using software (like service discovery: <a href="https:&#x2F;&#x2F;blog.heroku.com&#x2F;managing_your_microservices_on_heroku_with_netflix_s_eureka" rel="nofollow">https:&#x2F;&#x2F;blog.heroku.com&#x2F;managing_your_microservices_on_herok...</a>)
评论 #12303810 未加载
linkregister将近 9 年前
I actually learned a couple of things from this article even though it&#x27;s satire. I struggled through the de-monolithing of an application into microservices and then into Docker containers. Do people actually do this without having pressing issues that haven&#x27;t lead them to this path? Is there any reason to spread into microservices unless the monolith is not keeping up with requests?<p>I would have never considered Docker containers unless artifact preservation&#x2F;isolation and deployment issues hadn&#x27;t forced me to look toward a solution.
golergka将近 9 年前
Look, if you&#x27;re a one man shop doing a small project — do LAMP. Do perl. Do cgi. Do whatever you&#x27;re comfortable with; if you try to switch to the latest silver bullet tech, you&#x27;ll just get disappointed.<p>But if you&#x27;re a CTO with a startup with 10+ server-side developers and plan to hire at least as much in near future, suddenly all these dockers and microservices actually make sense.<p>So, unless you&#x27;ll start conversations with _who_ you are and _what problem_ are you trying to solve, of course the other side will seem stupid.
评论 #12303781 未加载
QuantumRoar将近 9 年前
I&#x27;m not a web developer but I sometimes put some programs on the web for me and my friends. I use FreeBSD Jails for that.<p>Can someone explain to me the advantages of Docker compared to Jails?
评论 #12303884 未加载
jwmoz将近 9 年前
Reminds me of <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=b2F-DItXtZs" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=b2F-DItXtZs</a>
raverbashing将近 9 年前
Also<p>Hitler uses Docker: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=PivpCKEiQOQ" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=PivpCKEiQOQ</a>
评论 #12304527 未加载
imtringued将近 9 年前
Since we are seeing so many &quot;ads&quot; here in this discussion. Does the average HN reader prefer this type of advertising to regular adsense ads? There is no violation of privacy, no autoplaying video, they are actually relevant to the discussion and it&#x27;s obvious that they are trying to sell you something. Oh and probably the most important thing si you can downvote them.
评论 #12303983 未加载
h8x0rd将近 9 年前
He slowly caressed his docker image while tenderly inserting it in the continuous delivery pipeline. The slow throbbing of the Jenkins service increased in intensity as the automated tests started firing off in a crescendo of etcd writes leaving a quivering micro-service that lay panting in its pod. That was a memorable deployment. The first of many that night...
geggam将近 9 年前
See .... microservices are where you take a process using IPC and force it to go over a network and use TCP ...then you pretend it will run better and scale more but avoid the whole 10x infrastructure growth and the fact the devops team has tripled in size to manage the frankenstein ... dont forget to add in the whole SDN layer the network guys absolutely love
forgottenacc56将近 9 年前
I&#x27;m not sure I get the message.
评论 #12303435 未加载
评论 #12303835 未加载
discordianfish将近 9 年前
Hype is as bad as seeing a promising technology just as hype without trying understand the problems it might solve.<p>This is quite frustrating for both people who are aware of those issues and trying to fix them as well as the people missing out on the real advantages of such technologies.<p>This reminds me of similar sentiment around virtualization and cloud computing later in my peer group:<p>Some sold VMs as security feature and people focused their criticism on that, without understanding other advantages like quick&#x2F;self-service provisioning of systems. Later one, cloud computing was trivialized as &quot;it now just somebody elses computer&quot; which completely ignored advantages like no ramp up costs and the ability to problematically manage your systems life cycle.<p>PS: Considering every new thing a fad probably also makes you consider &#x27;hadoop&#x27; the latest shit in big data processing and assume today&#x27;s tech companies hipster are fighting over wordpress plugins. (Like, really?)
beweinreich将近 9 年前
As someone who recently drove down the path of learning all the new &quot;hotness&quot; in the DevOps world, I can safely say I came out of it with two learnings:<p>1. I have a much better understanding of what&#x27;s happening behind-the-scenes<p>2. For most small startups, you should seriously consider the time (and therefore, cost) of investing in your own infrastructure.<p>For point #1, I think understanding your options and how they benefit your company is essential for you transition from a small -&gt; medium -&gt; large size company. The paradigms you learn by virtue of researching the new technologies might end up being applicable in other parts of your development process.<p>On point #2, I partially regret not deploying to Heroku, seeing where our system became stressed, and optimizing. Attempting to scale for things you don&#x27;t know about yet is tough, and can lead you down a path of wasted time and money.
farorm将近 9 年前
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.
jfoutz将近 9 年前
&gt; So I just need to split my simple CRUD app into 12 microservices, each with their own APIs which call each others’ APIs but handle failure resiliently, put them into Docker containers, launch a fleet of 8 machines which are Docker hosts running CoreOS, “orchestrate” them using a small Kubernetes cluster running etcd, figure out the “open questions” of networking and storage, and then I continuously deliver multiple redundant copies of each microservice to my fleet. Is that it?<p><i>exactly. I mean look, if you have a lifestyle business that&#x27;s only going to support 5-10 people, it&#x27;s totally a waste of time. if you have some hope of scaling this is the way to go. I get it, just use Heroku. It&#x27;s easy and convenient. If you&#x27;re planning on a billion dollar exit, this way is way better.</i><p>&gt; I need to decide if i believe my own hype?<p><i>yeah. sorry.</i>
EGreg将近 9 年前
You know what&#x27;s better than microservices? Nodes. Nodes running open source software that can power a distributed network.<p>Microservices often hit the same database. You want to be able to split up the database. Not just into shards, but into distributed nodes.<p>And by doing this, you split up the whole stack.
laithshadeed将近 9 年前
I believe microservice is the wrong term used to describe SOA. The word &#x27;micro&#x27; make it looks simple &amp; applicable for tiny apps 10-50K SLOC. I believe you should start chopping off your monolithic app only when it reach &gt; 100K SLOC. Still you can split it up by well defined modules with clear interface, without necessarily using SOA if it is running on same box.<p>Having monolithic app does not make it bad. What makes it bad is not having proper modules with proper interfaces.<p>SOA comes handy when you want to distribute your workload, so now we have proper modules but those modules needs more computing power, so split them up into boxes and pay the pain for managing that, because you have no option.
brightball将近 9 年前
As the author of that &quot;Docker is the Heroku Killer&quot; post that was popular a couple of years ago I have to say that I agree with this.<p>When I wrote that article it was largely focused on the potential for Docker to create a bunch of Heroku competitors as well as a simplified development experience across multiple languages.<p>The businesses aren&#x27;t there yet although a ton are trying. The local dev experience has not materialized yet either outside of native Linux due to performance issues with volumes that only a 3rd party rsync plugin have come close to fixing.<p>I still use and advocate for Heroku pretty heavily for just about any non-enterprise environment.
评论 #12304747 未加载
评论 #12309217 未加载
jpalomaki将近 9 年前
When it comes to micro services and containers, we are are missing fairly detailed descriptions of real world architectures from successful projects. And actually that applies to many other technologies as well.<p>When it comes to micro service, it would be interesting to know simple things like what kind of services were created, how large are, how communiction is handled, how large team(s) behind the service etc.<p>For some companies these are of course trade secrets, but sometimes opening things up might be good marketing. An example is Backblaze with their very detailed descriptions of their storage pods.
评论 #12304401 未加载
mtrycz将近 9 年前
Is there a computer-voice teddy-bear version of this?<p>I find them much better than walls of text.
spriggan3将近 9 年前
Clickbait titles like that don&#x27;t make me want to do business with circleci , it feels like a business full of immature kids yelling at each others. Not even going to click on the link.
atulatul将近 9 年前
Not exact but somewhat similar feelings expressed here: Let Me Just Code: <a href="http:&#x2F;&#x2F;www.drdobbs.com&#x2F;tools&#x2F;just-let-me-code&#x2F;240168735" rel="nofollow">http:&#x2F;&#x2F;www.drdobbs.com&#x2F;tools&#x2F;just-let-me-code&#x2F;240168735</a><p>Getting Back To Coding <a href="http:&#x2F;&#x2F;www.drdobbs.com&#x2F;architecture-and-design&#x2F;getting-back-to-coding&#x2F;240168771" rel="nofollow">http:&#x2F;&#x2F;www.drdobbs.com&#x2F;architecture-and-design&#x2F;getting-back-...</a>
nickbauman将近 9 年前
What containers do for you is two and only two coarse-grained things. 1. Make you more productive rolling out validated infra 2. Better utilize your hardware. Both of these things imply that you were using VM&#x2F;AMIs before and you were hand-crafting your entire stack using things like Chef and Ansible. If you weren&#x27;t doing that before (like, if you were using Google App Engine or Elastic Beanstalk or Lambda), Docker will make you <i>less</i> productive than you are today.
Almaviva将近 9 年前
I think words are very powerful, in particular &quot;microservices&quot; vs &quot;monolith&quot;. By accepting those words, we imply the conclusion: microservices sound sexy and lean and elegant - who can argue with separation of concerns? And a monolith is a big unchangeable rock.<p>I think we need a better word for apps that are single tight self-contained systems than &quot;monolith&quot;. You can design elegant interfaces, and avoid creating a sloppy mess, with function calls or objects too.
josh_carterPDX将近 9 年前
It&#x27;s amazing that an article from a year ago can still create a buzz on HN like this. Goes to show there are still a lot of people talking about this.
DonHopkins将近 9 年前
Where do Beowulf Clusters fit into all of this?
评论 #12304799 未加载
oelmekki将近 9 年前
&quot;Hi, my name is dokku, and I have no idea what you&#x27;re talking about&quot; :)<p>This rant sounds just like any rant from old dev mocking a new tech. &quot;This is less efficient, this is too complicated, this can&#x27;t be taken seriously, this won&#x27;t last&quot;.<p>Creating a character obsessed with &quot;this is dead&quot; hardly dissimulate the obsession with &quot;this won&#x27;t work&quot;. Do whatever you please, we don&#x27;t care. But don&#x27;t mock others about what they please.<p>Passing through that, let&#x27;s address the critics.<p>Microservices and docker are not necessarily tied. I write only monolithic apps, and use them with docker through dokku.<p>Etcd is a microservice problem, not a docker one.<p>You don&#x27;t need coreos or kubernetes to use docker in production. You need them if you want massively scaled applications, just like you would have many servers running the same app with replication without docker. Most of us don&#x27;t need that (and those who need it probably won&#x27;t find it more complicated than what is needed to do that without docker).<p>If you don&#x27;t want to manage servers, well, don&#x27;t manage them. That&#x27;s what cloud services are made for. But please tolerate some people love devops and not spending much direct money into infrastructure.
评论 #12303977 未加载
评论 #12304456 未加载
评论 #12303797 未加载
wyldfire将近 9 年前
I must&#x27;ve missed a tech cycle (or two) - I had heard of Heroku but didn&#x27;t know what it did. I&#x27;ve used lxc and Docker and read bits about CoreOS&#x2F;rkt&#x2F;appc&#x2F;kubernetes&#x2F;etcd.<p>I know it&#x27;s tongue-in-cheek but few if any of these new fangled things are critically dependent on one another.
colemannerd将近 9 年前
This comment is over simplistic and reads like it was written by someone who doesn&#x27;t know what they&#x27;re talking about. All of these technologies have their place, but they should be adopted incrementally and where it makes sense. Posting a frenetic conversation benefits no one.
评论 #12307641 未加载
评论 #12307636 未加载
a-priori将近 9 年前
There&#x27;s a theory in economics about the optimal size of a firm. How big should a company be? The optimal size could be infinite, where all of society acts as one firm. Think Communist-style command economy. Or it could be one, where everyone acts as networks of individual contractors or single-owner businesses. Think anarcho-capitalism. But in reality it&#x27;s neither extreme and falls somewhere in the middle; why?<p>It turns out that the optimal size depends on the balance between the overhead costs associated with allocating resources within one firm and the transaction costs associated with two firms doing business with each other. The overhead costs are higher with large firms because there&#x27;s more internal resources, including people, to allocate. On the other hand, transaction costs are higher with small firms because each firm does less themselves so they need to transact more with others to accomplish their goals.<p>As the relative costs vary over time, the optimal size varies too, and firms in an industry will grow and shrink. If it increases, then you&#x27;ll see mergers and acquisitions produce larger firms. If it decreases then you&#x27;ll see firms start splitting or small startups disrupting their lumbering competition.<p>I suspect a similar thing happens in software, where there&#x27;s an optimal service size. It could be infinite, where it makes sense to build large monoliths to reduce the cost of two systems communicating. Or it could be one, where it&#x27;s optimal to break the system at as fine a granularity as possible (function level?).<p>The optimal size depends on the balance of costs. All else being equal, by drawing a service boundary between two bits of functionality you shrink the services on either side but you increase the number of services and add communication costs for them to exchange data and commands.<p>How these costs balance out depends on the technology, and there are competing forces at work. As languages, libraries and frameworks improve, we can manage larger systems at lower costs. That tends to increase the optimal service size. As platforms, protocols and infrastructure tools improve, the costs to run large numbers of services decreases. That tends to decrease the optimal service size.<p>The microservices movement, and to an extent the serverless movement, assume that in the medium- and long-term the technological improvements are going to tip the scales sharply in favour of small services. I agree that&#x27;s likely the case. But we&#x27;re not there yet, except in some specialized cases such as large distributed organizations (Conway&#x27;s law). But it&#x27;s going to be at least a few years before it&#x27;s worthwhile to build most software systems in a microservice architecture.
thearn4将近 9 年前
This is structured like one of those Xtranormal do-it-yourself cartoons from a few years back.
partycoder将近 9 年前
Well, repeating buzzwords and pushing for early technology adoption for the sake of early technology adoption seems to be dumb, as the article implies.<p>But new technology is necessary and early adopters are necessary. Iteration is necessary. Don&#x27;t punish it.
wjd2030将近 9 年前
I love everything about this.
reledi将近 9 年前
The post got one critical detail wrong. The microservices won&#x27;t have their own API. APIs are dead. They&#x27;ll use Kafka for messaging. That&#x27;s the future.
cdnsteve将近 9 年前
Duplicate story: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9688383" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9688383</a>
samhunta将近 9 年前
This reminds me of React state. Sagas, selectors, constants, components, containers, routes, reducers, actions, connectors, shoot me.
daveheq将近 9 年前
Check back next year for Docker is dead article.
vpol将近 9 年前
Yet another comparison of hot and soft.
评论 #12303534 未加载
krisgenre将近 9 年前
Is there really something called &quot;Ew&quot; ? Its hard to Google something thats just two chars.
评论 #12307303 未加载
评论 #12321192 未加载
jgalt212将近 9 年前
Question:<p>Is there an advantage to using docker when it takes 3 hours to rebuild our relatively small database?
评论 #12304060 未加载
rendambathu将近 9 年前
this old gem is back trending now!
rjcrystal将近 9 年前
doesn&#x27;t anyone think about performance anymore? I mean just add more vms or increase their config, no one talks about efficient resource utilization asfaik. And there might be times where you containerizing everything is an over overkill.
评论 #12304551 未加载
snambi将近 9 年前
Really Hilarious and Reality. Lot of noise about docker, kubernates, microservices etc.
saynsedit将近 9 年前
Wow, what a strawman. Seems like someone was blowing off some steam.
评论 #12304332 未加载
SurrealSoul将近 9 年前
&quot;I thought Mongo was web scale?&quot;<p>This joke will never get old to me
audessuscest将近 9 年前
Is it a blank page ? I don&#x27;t see any text.
评论 #12303584 未加载
评论 #12303755 未加载
评论 #12303462 未加载
mrich将近 9 年前
Lovin&#x27; it!
_pmf_将近 9 年前
Did you just tell me to go containerize myself?
trevyn将近 9 年前
(2015)
marknadal将近 9 年前
Self admittedly, I am one of the P2P psychotic pundits. This is a good reminder that we need to tone our language down.<p>That said, if you can get your system to work with a single Heroku box, you really truly can simplify your life. That is what we&#x27;re trying to do with <a href="http:&#x2F;&#x2F;gun.js.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;gun.js.org&#x2F;</a> , be able to start with a single machine and no configuration&#x2F;setup&#x2F;complexity. Then grow out.<p>We just had a discussion on the WebPlatform Podcast about all of this P2P stuff (<a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=NYiArgkAklE" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=NYiArgkAklE</a>) although, like I said, I probably got too jargony.<p>But props to circleci for calling out the elephant in the room. Great marketing actually.
clifanatic将近 9 年前
I&#x27;m sure I could go back 5 years and see an almost identical complaint about Heroku.
bbcbasic将近 9 年前
Solution: .NET
jondubois将近 9 年前
That&#x27;s why we started <a href="https:&#x2F;&#x2F;baasil.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;baasil.io&#x2F;</a>.<p>The idea is you can deploy any app to any infrastructure of your choice (inside Docker containers). This means that you are not locked into Heroku and it gives you much more flexibility.<p>It&#x27;s basically a hosted Rancher <a href="http:&#x2F;&#x2F;rancher.com&#x2F;" rel="nofollow">http:&#x2F;&#x2F;rancher.com&#x2F;</a> service with a focus on a specific stack.<p>I think in the future, there will be a lot of services like Baasil.io (specializing in various stacks&#x2F;frameworks) and managed by various open source communities.<p>Docker and Kubernetes WILL become more accessible to developers - I would bet my life on it.<p>I&#x27;m currently building a CLI tool to allow deploying in a single command - So you can get the simplicity of Heroku while not losing any flexibility&#x2F;control over your architecture.
评论 #12303474 未加载