Azure Service Fabric
Explained for Mortals
I know I announced Indexes for this week and I won’t let you down, I promise! I just wanted to share a quick insight I had yesterday on what Azure Service Fabric really is :)
Interestingly enough, the only way to understand full potential of what Azure Service Fabric provides is to have spent years trying to do all of it manually :) You really would have had to suffer the issue of instantiating, orchestrating, monitoring, logging, setting up communication channels, debugging failed networks, etc. in order to realize what you get out of the box.
Azure Service Fabric is a Platform (hence, a PaaS) that runs both on Windows and Linux and that allows you to deploy BOTH containers and standalone (micro)services. Which is also why it's similar but not exactly the same as Kubernetes - it gives you more :))
Service Fabric itself is an orchestrator. Or, for us old timers, that group of people who were bugged every time something would go down - combo of DevOps, Devs, VPs and everybody else who went through pain of running distributed platform (myself included).
It's probably obvious that what it does is takes away the pain and makes sure that your services (or containers) are playing a symphony!
For more details, look up the official docs (they are quite generous anyway)!
Thanks for reading Bitesized Engineering! Subscribe for free to receive new posts and support my work.