News for hackers. Stuff that matters.
Re:Infrastructure Mistakes Companies Should Avoid by dbg31415 on Friday September 30, 2016 @12:47AM (#12610565)
> If you discovered the tool on Hacker News and it's less than 18 months old — 'Danger, Will Robinson!'

You shouldn't fear new things. Keep it simple, keep it smart, and embrace what works for your team. Don't shun things because they're old, don't shun things because they're new. Shun complexity.

How about a real-world examples? Slack, Google Docs, and ZenHub. All of these added value right out the gate.

I first read about Slack in February 2014 on Hacker News.

* We Don’t Sell Saddles Here – Medium || https://medium.com/@stewart/we-dont-sell-saddles-here-4c5952...

Started playing with it, then started using it. It's helped my team move much faster. Slack added value. No reason not to use it. Same for ZenHub, same for Zapier, same for Docker, same for a bunch of other tools where I can say, first-hand, that being an early-adopter paid off vs. using something "tried and true."

Oh, and on that note, I freakin love Marker! (=

* Marker - Annotated Screenshots Sent to any Bug Tracking Tool || https://getmarker.io/

Re:Infrastructure Mistakes Companies Should Avoid by snom380 on Friday September 30, 2016 @03:47AM (#12611045)
From the article, it doesn't seem like he's talking about tools like Slack. If that goes down, maybe it affects your productivity, but probably not your production systems.

What he warns against is betting too early on core technologies like service discovery, deployment systems (Docker etc), database systems (MongoDB) And from reading HN posts, it sure seems like there's no shortage of people being burnt by that.

Re:Infrastructure Mistakes Companies Should Avoid by avifreedman on Friday September 30, 2016 @03:56AM (#12611072)
Yep, sorry if it didn't come through clearly enough.

I was talking about (without trying to pick on any particular projects/vendors) infrastructure glue components - db, deployment/orchestration, storage, discovery, ...

Maybe 'tool' was the wrong word, and 'component' would have been more clear.

Re:Infrastructure Mistakes Companies Should Avoid by jacques_chester on Friday September 30, 2016 @11:46AM (#12613147)
How do you feel about PaaSes like Cloud Foundry or OpenShift?

They are, to greater or lesser degrees, able to present a uniform platform to developers across various backends (CF runs on OpenStack, AWS, Azure, GCP, vSphere or raw hardware via RackHD).

So long as you deploy your own services using the same tooling (BOSH), it's possible to hoist and relocate a lot more easily than relying directly on the IaaS's services.

Disclosure: I work for Pivotal, the majority contributor of engineering to Cloud Foundry and BOSH.

Re:Infrastructure Mistakes Companies Should Avoid by avifreedman on Saturday October 01, 2016 @03:03AM (#12616835)
I think they can be pretty efficient and if a handle is kept on what's deployed on top, can be not that much overhead over the cost of the infra (whether it's owned or cloud). But that keeping a handle on things is key - starting w/o a DBA is nice but if no one is tracking tables or how they're used things can get pretty expensive :)

Specifically re CF - have seen a few companies use CF to do multi-infrastructure, but a lot of the companies we work with have 5-10 roles and just run them via config mgmt to deploy or now docker +/- k8s, and don't use PaaS at all.

Re:Infrastructure Mistakes Companies Should Avoid by jacques_chester on Saturday October 01, 2016 @09:08AM (#12617685)
Thanks for coming back, I was worried that a late reply would be overlooked.

> But that keeping a handle on things is key - starting w/o a DBA is nice but if no one is tracking tables or how they're used things can get pretty expensive :)

At Pivotal we ran into this problem in building service brokers that worked by interacting with single, large, efficient shared services. Most services lack the strength of isolation that you are getting for the apps themselves. So on a shared database, queue, cache etc, the noisy neighbour can really begin to hurt.

In our 2nd generation of these service brokers we changed our approach. Previously asking the service broker for a service returned almost immediately (create account/endpoint/schema/queue/bucket/whatever). Now we actually go and provision an entirely new, isolated service instance. Luckily BOSH makes this relatively easy to do.

Essentially we've recreated the journey that led to containers: realising that while the efficiency of shared instances is nice, it's more important to be able to enforce functional and non-functional isolation. So now the services are on par with the apps in terms of their platform behaviour.

The outcome is the same: ops no longer have heavily gateway against bad developers, because only those developers will be affected by their errors. I have a very long analogy involving sharehouses that I will skip on this occasion.

> but a lot of the companies we work with have 5-10 roles and just run them via config mgmt to deploy or now docker +/- k8s, and don't use PaaS at all.

Yeah, the jump from nothing to all-the-things is a pretty big one for people who are solving the partial problem they see directly in front of them. Dynamic languages, NoSQL etc are all much more approachable than their alternatives, because you can build in smaller steps.

We're working on it -- PCFDev and BOSH bootloader are two main prongs and there's more to come. If you want to give any more feedback of kvetching, please feel free to email me ([email protected]) and I'll connect you to the right people.

Re:Infrastructure Mistakes Companies Should Avoid by dom0 on Friday September 30, 2016 @04:44AM (#12611231)
I wouldn't consider Docker a deployment system (at all).
Re:Infrastructure Mistakes Companies Should Avoid by dwaltrip on Friday September 30, 2016 @03:38AM (#12611006)
> You shouldn't fear new things Keep it simple, keep it smart, and embrace what works for your team. Don't shun things because they're old, don't shun things because they're new. Shun complexity.

Often times, new things haven't fully mastered the complexity of the target domain. Also, they might work now, but will it work next year, if the project or service is abandoned? Using new things is fine, but we should be aware of these potential drawbacks.

The examples you give are great, but how many other tools were posted in 2014 and since have gone kaput? Gotta watch out for survivorship bias.

Re:Infrastructure Mistakes Companies Should Avoid by bbrazil on Friday September 30, 2016 @05:26AM (#12611384)
I like the idea of innovation tokens: http://mcfunley.com/choose-boring-technology

Basically you get 3 things per project where you can use something that's not tried and true.

Re:Infrastructure Mistakes Companies Should Avoid by rdtsc on Friday September 30, 2016 @01:44AM (#12610694)
> You shouldn't fear new things.

I found one easy way is to just ask the person using the technology why they are using it. As long as they understand the trade-off and understand how it works, that's fine. If they say because they've seen stories on HN or at latest meetup someone mentioned, or it's "async so therefore faster", then be worried.

I used to be that person out of college who didn't know and just went by whatever seemed more popular or whichever project had the coolest front page with most futuristic looking hexagons and such on it.

Re:Infrastructure Mistakes Companies Should Avoid by collyw on Friday September 30, 2016 @05:50AM (#12611450)
This! If they just repeat the marketing blurb from s/Mongo's/<hip new tech>/ website, then they generally don''t have a clue what they are doing.
Re:Infrastructure Mistakes Companies Should Avoid by dbg31415 on Thursday October 06, 2016 @07:36PM (#12657004)