In-house we are utilizing Azure Service Fabric. Although the learning curve is still quite high for Service Fabric, we're finding it makes it easy to develop an on-premise solution that has all of the niceties of a cloud-based solution, just without auto-scaling (i.e. to scale we would have to install more server nodes).
When researching how to build our next generation of software, from our current monolithic, service-oriented architecture, I was turned off from K8 as the amount of new skills required for our development team was just too high. With Service Fabric we can start learning how to decompose our old application into micro-services and let the platform do most of the work for us. It's not perfect by any means, but I'm loving it!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks so much for this.
In-house we are utilizing Azure Service Fabric. Although the learning curve is still quite high for Service Fabric, we're finding it makes it easy to develop an on-premise solution that has all of the niceties of a cloud-based solution, just without auto-scaling (i.e. to scale we would have to install more server nodes).
When researching how to build our next generation of software, from our current monolithic, service-oriented architecture, I was turned off from K8 as the amount of new skills required for our development team was just too high. With Service Fabric we can start learning how to decompose our old application into micro-services and let the platform do most of the work for us. It's not perfect by any means, but I'm loving it!