tisba

Screenshot: https://dsc.tisba.de/KY59HOE9ms.png

That service is actually a batteries included hosting service for the very well made desktop file sharing tool Dropshare (https://getdropsha.re/).

(sorry, might be a little OT)

When I hear or read about "microservices", I always have some articles from Martin Fowler in my head (among others):

* http://martinfowler.com/articles/distributed-objects-microse... and http://martinfowler.com/bliki/MicroservicePrerequisites.html (IMO both a very important read)

I think most people are running into the issue, that they think "microservices" are something new and hip and they don't have a clue on how to break down problems a meaningful way.

PS: Another VERY interesting read, and also maybe a bit unrelated to container hosting is "Testing Strategies in a Microservice Architecture": http://martinfowler.com/articles/microservice-testing/. I'd love to hear some more thoughts about that and how services like giantswarm could help with that...

There are a couple solutions that do that - none of them I find sufficient. If you want to clone live traffic, that's probably okay, but recording traffic and replaying it in a usable fashion is a non-trivial task. e.g. systems tend to be dynamic so your recordings would need to be dynamic too in order to be realistic.

Okay, that's true. But the question was about confirming the target's ownership. And that is something you cannot ensure via DNS entries.

this is especially challenging actually. just because you own the domain name, doesn't mean you own the infrastructure you are pointing your DNS records to!

So adding DNS records is pretty useless to provide proof that you own the resources under test.

You are referring to the error rate? :) We actually did about 800M additional requests two days after I've written the post.

I have no idea, why this ended up here, but if you are interested in some technical details what SF does: http://blog.stormforger.com/2014/05/27/load-testing-an-inter...