Skip to main content

Amazon... would the real hammock please stand up

Buyer's beware

Eagles Nest Outfitters Hammocks
Bear Butt Hammocks
Hobo Hammocks
Pro Ventures
Live Infinitely
Nature's Hangout

Let's face it there isn't much difference between these hammocks. My guess is that they all use the same fabrics, same hardware, and same ropes or straps. They all have the same costs centers:

  • internet e-store
  • social media and other advertising
  • reselling through Amazon
  • salaries
  • office space and related
  • materials and manufacturing costs
  • warranty costs
There is no way that any of these startups is individually tooling up a manufacturing complex in order to produce the product. And there is a good chance they they never actually negotiated with the factory. Having a hint of how this works it's likely that they negotiated with a US based rep.

And so we have so many different hammock companies.

One thing I like about Hobo Hammocks is that they give back by feeding the homeless. On the other hand they are also charging about $5-15 more than the lowest. Keep in mind that Amazon is a store and they are not very responsible about what they put on their shelves. At least when you go to the grocery store they tell you he cost per ounce, count, etc.

The cheapest I saw a hammock for was $18. The color choices were pretty bold but it was very strong.

UPDATE... as I predicted ... they are all the same:




UPDATE 2: some other things that seem to stick out. [a] how many of the hammock sellers are actually outfitters many seem to sell branded swag [b] one product startups without a real web presence

I have an outstanding email into the sales department at ENO. If they are actually manufacturing in the US I'd pay a little extra. This other practice of just marketing some crap product just does not sit well.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…