Skip to main content

"Amazon Echo" and "OK Google"?

Have you ever used Amazon's Echo? What about "OK Google"? A friend of mine demonstrated Echo and I was very impressed; I have also been a "OK Google" user since I bought my first Android phone about 9 months ago. And there are plenty of pros and cons for them both.
For example while I like to listen to BBC and NPR news I never appreciated audio books.
One of the killer features of the Echo is it's "always on" feature. This is also a little spooky because someone could be listening and it's a short hop from Apple cracking iPhones to playing back Echo's audio (There is a Google dashboard flag for disabling backing up OK Google commands so I imagine there is one for Echo.)

The second killer feature for the Echo is that it now comes in 3 varieties. (i) a puck called Dot intended to be connected to a speaker or stereo, (ii) a battery powered speaker called Tap (iii) and the original Echo. Since they are dedicated for their purpose the UX is simple and to the point.

And while Google's Chromecast and Chromeaudio are cool on their own they require specialized Chrome clients and servers to make everything function. And while my Nexus 6 is a little more portable when compared to the Dot I'm not usually telling google what I want to listen to when I'm on a plane. So the use case for Alexa and OK Google are pretty much the same.

And while Alexa is an amazing feat unto itself Amazon is about selling stuff. Their Amazon music is just not as good as Google Play Music. Google needs some better hardware and Amazon needs to play better with Google... at least I hope they learn something; it's bad enough that they share ad and search info.

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…