Why not use hip hop?

Isn't that a bit of a misnomer, they are integrating with existing delivery services. From the subject I figured they were providing their own? Either way... cool....

i feel like a lot of people seem to jump on to "schemaless" dbs because they feel the can just dump whatever they want into the database. they also run into a problem later on when they realize that they need to care about data integrity and types.

Or you have a data structure that would require a lot of tables for what equates to a single record of interest.

In my last job, we were presenting search, and display of classified listings for cars. The normalized data required, iirc, 28 join operations to get most of the data for a single record (for display), about 12 iirc for the search support (not including geo/location based searches), and a second lookup for related data.

This could be replaced by a single query in a non-sql database. There is a real cost to these kinds of structures in SQL... There are a LOT of use cases where a single record structured as a complete object is much better than having to break up said structure into dozens of fields.

ive used impress js before for presentations at work. Easy to use and it can do some fun things. using powerpoint or any type of office application on a mac is always a pain.

Isn't running a database in a container sort of bad practice? Especially if it does a lot of io

No. In terms of io and other kinds of overhead, you are always better off running your database on a container rather than a VM. The majority of public cloud database services are either running inside containers, or in the process of migrating to containers.

An additional advantage of containers is that you can start running them on top of a VM, and then migrate to bare metal later, as your infrastructure requirements evolve.

I think in my head I had container ON A VM. Which just inherits the problem of running it on a VM. Is there a good linux tool for limiting the IO of a process or user?

Networking uses tc and disk uses the block I/O controller. https://www.kernel.org/doc/Documentation/cgroups/blkio-contr...

Looks pretty cool. While you are building stuff, can you add in dynamic alerts so that I can create alerts around events I care about?

You can add alerts on summary metrics - and you can have up to five summary metrics on a plugin.

If you are consuming a published plugin, you get alerts on whatever summary metrics the plugin author selected. If you are authoring a plugin, you can pick up to five metrics to be your summary metrics, then you can create alert thresholds on those metrics.

Linux containers have been awesome for helping me sandbox user generate code. Has anyone actually had experience with using Mesos in the real world?

That's all that they are good for adding security that would otherwise not exist. Outside of that under a PaaS, I don't see what they add.

Does anyone have some good reading material to start getting into functional languages?

This book is one route in. It's intended for those who've programmed before but not necessarily with functional languages. I suspect intros to any of the functional languages would be fine (e.g Haskell, Scala, F#). There's even a Coursera course on Scala.

I just had this discussion with my friend today. While it is true that building a simple simple api from scratch is pretty quick, the hack-it-super-quickly api gets really hairy really quickly. Later you have to spend a lot of time refactoring to make the API scalable and easy to add endpoints and functionality. And usually you realize you have to refactor when the poop starts hitting the fan and the hacked together solution isn't holding its weight anymore.

I started off using my own implementation and was thinking about switching to docker... what made you switch away from docker?

Hey guys, for an honest and transparent account of what Docker can and cannot do, and whether it makes sense to use and improve it vs. build your own, come say hi on #docker@freenode.

If we think it makes more sense to build your own, we'll tell you, and will share our experience to save you time while we're at it. The more containers out there, the better for everyone :)

It's poorly documented (so you'll need to dig into the source to figure out how to use it) and at least when I was using it did not play well when scripted (like sending commands to the container). It also wasn't terribly reliable (a command might work one but not the next time) and it seemed like it was in a state of transition. (moving towards a RESTful API?) I just think if you use it now you'll end up writing stuff (at least) twice.

Not that raw LXC is much better... It all seems very immature.

Can you give us some examples on where it is poorly documented so that we can fix those issues?

Also, if you can let us know what you were doing when the command didn't work the same way every time? Have you filed any issues for those yet? If not, can you, or tell me here and I can do it for you. If we don't know about your issues, it is hard for us to fix them.

Thanks