micro

Some of the backend is being moved to micro-services but we're not planning to go overboard with it.

Things are often they way they are because it works on a macro and micro level.

That said, even for a small-time app, consider the weight of trying to run a complicated micro-service-based system on a developer laptop.

You run a thousand different micro-benchmarks on the performance difference between re-binding a cached method handle for a setter, or just calling instance_variable_set.

We are trying to upgrade to a small ec2 from a micro tier.

This happens on top of micro-service and batch processing frameworks we've built in-house to handle our specific use cases.

AND even more excitingly, small micro payments can be made part of the contract, to the third-party verifiers, as part of the contract itself.

If they study went one step further and showed how those micro decisions aggregated into macro inequality, that would be interesting to me as well.

I've seen the same attitude before in tiny SIGs: go take a look the what's left of the classic 16-bit micro (or early 32-bit micro) userbases and you'll see a lot of it.

Please point me to usage of the term micro-studio in London.

There should really be a open micro-payments systems.

You get a micro-workout as a small bonus.

Most "micro-apartments" are significantly bigger than shipping containers (which are 320 sq.

Anyone know what the noise level would be like in these "micro apartments?" I'd imagine with them trying to cram in as much space as possible there would be noise issues with at least one of your neighbors, which would of course effect your ability to stay focussed and get things done at work.

Working on a system right now that would have the need for a "central" application that would need to regularly launch subworker apps for a specific task (planning on running each sub app on it's own micro AWS instance) and then "kill it off" once the job was completed.