Select Page

We have a continuous improvement focus with regards to Azure Serverless for Self-Service Logistics Automation.

Medium.com is a publishing service, connecting writers with readers.

We find interesting independent information there and this discussion on serverless is a good summary of why we are interested in serverless.

The Medium paper has implications for companies using established ISVs, where the vendor is constrained by their overheads to a “one size fits all” roadmap that is proving an imperfect fit for diverging end-customer needs.

Is bigger better?

Delivering cost-effective scale across a large customer-base used to be a strength for ISVs, but serverless delivers the same capacity without upfront investment. Fixed infrastructure can deliver a lower price point for stable demand, but maintenance responsibility distracts, and when needs change inflexibility costs.

Without needing to throw the baby out with the bathwater, there are now cost-effective options for customers with unfulfilled needs, who are caught up with ISV development roadmaps that aren’t delivering full value.

Nimble serverless creates the room to provide a flexible bespoke middleware.

10 years ago, bespoke had become a dirty word with failed in-house projects built on expensive hardware. With serverless, the cost, maintenance and “speed to market” disadvantages need no longer apply.

A bespoke middleware solution with a trusted project team can cost-effectively automate individual requirements, with outcomes exceeding the sum of the parts e.g. a means to automate “last mile” parts of the business that couldn’t previously be reached and aggregating more information into management analytics.

Modern ISVs are already familiar with optimizing the use of the right tool for the right job i.e. heterogeneous cloud and related computing concepts like polymorphism.

Middleware allows the end-user customer to do the same thing.

Enterprise technologies like SAML/SSO, Blazor, CosmosDB and PowerBI make this all possible.

Serverless is swinging the pendulum back from economy of scale being the driver to nimble software solutions better delivering on automation promises for more of the customer business.

What happens when the wheels fall off?

“Democratizing Digital” provides a means for customers to get what they pay for, where it’s difficult to establish all requirements at purchase, and an emerging critical requirement might leave stakeholders up a creek without a paddle.

It’s tricky for customers buying enterprise software solutions, sifting through the vendor promises and requirement complexities.

On the one hand, there’s vendors like the $100M/year turnover US marketing-software company that promises a lot, but is nowhere to be found when reality doesn’t meet the sales messages.

On the other hand, there are ISVs trying to deliver while managing complexity and change. Even organizing the necessary human resources is a puzzle e.g. Software Roles

Employing middleware provides a nuanced way forward, and the structural flex to find cost-effective and maintainable ways out of tight “business requirement” corners.

Conclusion

The Corpfleet vision is to connect all the vertical solutions within a middleware framework, where unique end-customer requirements reside, helping all stakeholders and enabling procurement best practice.

Serverless technologies like CosmosDB provide a means for middleware to be responsive and reliable in the face of changing complexity.

The concept is fulfilling for software engineers, who are able to work in harmony with stakeholders, defaulting to saying yes instead of no.