petard

We have been using Mesos+Marathon+Docker in production for more than year. Mesos has been very reliable, there are a lot of moving parts so it does take some effort to get everything going.

Caveat: We only use it to run state-less applications. Applications like Kafka that require data persistence are run outside Mesos as data persistance is not yet handled reliably with Marathon.

[1] http://datajet.io/One-year-with-Apache-Mesos-The-Good-The-Ba...

I've been in many projects where people would iterate numerous times over architecture while completely forgetting what real-world problem they are actually trying to solve. Architecture becoming art pour l'art.

I don't see the point of the article being that every software developer becomes a fully-fledged UX guy, but understands the context in which the system is going to be used and not get lost in the technical rabbit hole.

only used vegeta and ab and prefer vegeta. has many more options and stats, while still being easy to use as ab.

From my experience running stateful applications should be avoided with the current state of things. We've deployed ElasticSearch, Kafka etc container-less but use containers for all of our stateless services.

What are your memory settings for utilizing the 360GB RAM with ElasticSearch?

> And it makes no frigging sense for a startup or any new project to start with microservices...

Doesn't that really depend on what the startup is doing? If your goal is a SaaS platform things might be different.

> ..you'll often end up with microservices that are divided in suboptimal ways causing a lot of pain.

Or one large monolith that is a mess. Really doesn't matter if you go with monolith or microservice architecture, you can screw up both ways.

502? Oh the irony.