Distelli is a welcome addition that doesn't tie you to a single cloud provider and actually works for more complex deployment systems. Glad to see them scaling up and getting attention outside of Seattle
Amazing progress and speed on Shippable compared to competition. Nice to see such a core part of the devops world getting improved. Whole CI/CD world only works if it is easy to test and ship. Most of the build systems have high friction and many companies don't understand how fragile these core systems are. Very worthwhile thing to outsource instead of hiring a Jenkins expert to scale it.
Looking forward to seeing more progress from this group in the months ahead.
This is an article with no attempt to understand the state of the art outside of what Airbus wanted written and is PR spin. Most of the techniques here were used in the 737NG program in the late 90s
This is nothing new and isn't different from Boeing in anything they mentioned in the article. Yes the 787 had issues, but the same types of testing occurred. The 787 was fundamentally different from previous Boeing aircraft with lots of primary components made by subcontractors. Lack of rigor and believing things would just work (too optimistic) from what I have heard on the outside.
Iron birds, flight tests, etc are the requirements from the certification authorities. I.e. this is a fluff piece acting as journalism where the title and conclusions don't match the data.
Very glad that Jeff wrote this up and he deservers mad credit for documenting something that has been frustrating me for years. People don't realize how hard doing this right is and discount the hard work that goes into making large systems scale in a stable manner.
It isn't just load testing but more that the whole system should be considered suspect. If you don't act defensively at all steps you will be hosed by something you thought will never happen. Just had a good talk about this last weekend. Memory, TCP, and all other rock-solid things can and will have issues in large systems.
Arrival rate and dequeue/processing time are the keys here. Unbounded queues are easy.. Just limit the queue size. Of course this isn't what the user of the service wants and leads to a very bad experience