service fabric vs kubernetes
It is important to think about the concept of service fabric vs kubernetes. Service fabric is when you are doing something that has benefits to the customer, whereas kubernetes is when you are doing something that is a cost to the customer.
To be an effective service fabric provider, you should ensure that your business is scalable, that the product/service is scalable, and that your customers are scalable. If your business is scalable, then the product or service that you are offering should be scalable as well. If your customers are scalable, then you should be designing for scalability. If you are both scalable and scalable, you should be designing for both.
So how do you know if the product or service you’re offering is scalable? For example: you may be dealing with a product whose sole use case is a very small group of three people. You may not even know they even exist. If the product or service has not scaled, then it is not scalable.
To take the example of a small group of three people, if you don’t know how many customers you have, you can’t be sure if your product is scalable. There are many reasons that may go against a product’s scalability, but only a select few should be valid.
This is one of those reason. But in the case of a service, if you have no idea how many users there are, it is definitely not scalable. So even though the service is small scale, the service provider is not necessarily scalable.
This is a huge point. As a case in point, I recently launched a new product and was doing everything right (making sure I had a great UI, testing it thoroughly, etc). Then I got a customer who had no clue what the product was about and thought I was making a joke. I had to explain what the product was, its purpose, and the reason I was launching it.
This is one of those things that should be obvious, but it’s not. There are probably 5x as many services out right now as there are users. That’s still probably not scalable. It is true that a lot of these services are not scalable, but in the long run they are much better for the user.
the reason I was going to start a service fabric vs kubernetes debate is because kubernetes is the default service for most people. I don’t have enough data to say why, but I’d like to think if I were to compare the two I’d choose kubernetes. It is also true though that most people are using these services for the wrong reasons.
One reason I think service fabric may be a better fit for people is that they have lower costs than kubernetes. Kubernetes is a multi-vendor project that basically gives us the ability to run our own containerized cluster. When you have to purchase a cluster with $5k to $10k dollars, you are basically going to have to pay that money so you can have one service running.
The second reason I think we’re going to see better results with kubernetes is that we can provide services that are highly automated with kubernetes. Like service fabric, we provide a high level of automation. The way this works is we can use our kubernetes cluster to provide multiple services on one node.