507 karma · joined November 12, 2014
BTW - the more I dove into Marathon the more I discovered how thin wrapper it is above mesos, that does most of the work including - container runtime, pulling resources, starting tasks, handling registries, and now even health checks!
The argument is usually around mesos' two level scheduling paradigm with which i'm familiar, but still don't see it's practical advantages over simple master scheduler.
Does someone have any insight on this topic? (assume docker containers will be used anyway and that a single application/framework will work on the cluster)
I wrote this article a while ago about how I hate that kind of interviews, and actually how I personally interview. Swear to god this was before that friend told me about his process, but they miraculously managed to exactly ask all the questions I considered wrong in that article!
A feature that Win 10 has and I was missing in mac (maybe they have it by now) was that desktops doesn't share taskbar and open windows states. So if you Alt+Tab you see only windows in current desktop. Same as using taskbar.
A feature I'm still missing is to save the state of all opened windows, and to have different icons on taskbar and desktop per virtual desktop (like separate computers).
Also there's a bug where chrome windows from all desktops just to the first desktop after waking from sleep.
If you don't trust MS you can trust one of the organisations that certified them for the strictest compliance and regulations in the public cloud space.
Also, Azure has the best suite of compliance\certifications that demonstrated their commitments.
BTW, Have you read the terms and conditions before speculating on them?
Yes, Cloud Services and VMs are two different things, however, Azure's IaaS was built on top of this concept up until when they migrated to ARM and VMs. The way it used to be, was that Cloud Services was Microsoft's PaaS, and when they introduced IaaS (Yes Azure had PaaS first), they built it on top of cloud services. So essentially IaaS built on top of PaaS. Most people would expect it to work the other way around, and so that's exactly what they did with the new stuff - They invested heavily in re-doing the entire IaaS stack, and then built PaaS components on top of it. Regarding ARM, VMs, the new stuff- We call it 'new' to differentiate from the 'classic' stuff, but it shouldn't be considered as such. It is old enough, stable enough and it the recommended way to do stuff on Azure.
If you are doing just IaaS - there's no question there. Use the ARM model. Cloud Services did have nice features mostly for programming model, and code deploy, but there are ways to do that with ARM as well. There is not a single direct replacement to Cloud Services, and it makes the transition harder. this is because the new model has different architecture and layering of the stack. If you are looking for these features, I recommend looking at a PaaS framework in the new stack like Service Fabric.
Service Fabric is not equivalent to Lambda, we have Azure Functions for that. SF is a cluster orchastration framework (think mesos) and it also has a rich .net and java sdk for developing Microservices that will be orchastrated on the cluster. it can also run exe \ containers. it is not server-less at all. It is nothing like API Gateway.
App Services is just web site as a service. I wouldn't call it PaaS but I understand this term is subjective.
Cloud Service is an old concept that we never recommend for new workloads, so I think it doesn't belong on this article.
Virtual Machines is self explenatory and it's very much like EC2 unlike who the article present it.
API Apps is not a proxy, it is an API. You could host you web API (any web framework) here. It is the same as website but with some semantic difference and cool swagger integration.
Virtual Network is not just for hybrid scenarios, it is the fundemantal container of all IaaS based resources in Azure.
Traffic Manages is not a like a classic Load Balancer (as the comparison suggests). It is a "Smart DNS" service for multi-region geo deployment.
Data Lake Analytics foes not "hold" any data. Data Lake Store does. Analytics is a batch processing technology that can process data from Store, but you can use Spark or whatever to do that as well.
Data Lake Store - see above. I think they confused this one with Data Factory.
I don't find any problem criticising what's wrong and commending what's right. I do that openly with "my employer" products, and the competition as well.
Here is my original X1 Carbon review: http://blog.itaysk.com/2013/05/04/lenovo-x1-carbon-touch-rev... And here are my thoughts on the X1 Yoga: http://blog.itaysk.com/2016/12/30/from-lenovo-x1-carbon-to-l...