With the recent announcement that the Device Manager has gone GA, I thought I would post a beginners guide on implementing a kubernetes device plugin.

I completely agree with the suggestion to use SQLite for simple projects, or even larger projects that need to be more portable.

Recently I've had some really great success using SQLite on an embedded project with decent enough support for concurrency using busy_timeout [https://www.sqlite.org/c3ref/busy_timeout.html] and WAL [https://www.sqlite.org/wal.html].

I work at a travel B2B SaaS company, and we roll out MVP products to our clients all the time. I think the key difference between selling to businesses and consumers is the appetite for risk.

So assuming you have a good product, you have to consider two things: commercial terms and SLA. This is a delicate balancing act when you're trying to shop your MVP. You don't want to underprice because implicitly you're saying the product isn't ready for production. You don't want to overprice, and set expectations too high. You also want to be careful about what kind of level of support you're agreeing to with your product. If it's an MVP, are you going to drop support after 6 months if your business can't support itself?

Good businesses consider these things before they sign-on for an MVP product, make sure you have good answers to these questions.

Thanks a lot, I definitely agree.

How does this stack up versus something like riot.js? http://riotjs.com/

RiotJS couldn't keep it to the original size of about 3 KB, it's about 9 KB now. They market it as a "React-like", but it appears that this one is way more "React-like" than RiotJS ever was.

Pretty cool!