I meant to add, I understood your point, and what you said is true. And a roll-your-own is going to have a flexibility that a legacy platform will never have.
That "second phase" is going to be about delivering radical next-gen capabilities, which certainly can't be done with legacy platforms. Jawaid On Tue, Aug 13, 2024 at 4:42 PM Alex Balashov via VoiceOps < [email protected]> wrote: > > > On Aug 13, 2024, at 4:07 PM, Jawaid Bazyar <[email protected]> wrote: > > > > That is generally true, though in our case the front-end/orchestration > layer is backend-platform agnostic. This was intentional, and gives > operators the ability to change a subscriber's provisioning from one > platform to another with a few clicks. That way we're not tied-in. Of > course this creates some additional complexity, but, gives us capabilities > I haven't seen offered elsewhere. > > I don't know your specific platform and have no reason to doubt the > veracity of this. > > However, speaking rather generally from my own experience, > backend-agnosticism--as a special case of modularity, functional > decomposition, loose coupling, high cohesion, etc.--is one of those themes > that shows up in technology over and over, and is never quite delivers what > it promises. > > In theory, the UI is agnostic to the backend and can drive anything with > an API-compatible surface. In principle, ORMs are supposed to abstract over > RDBMs so that one is as good as another. In reality, there are more > dependencies and hooks here than meets the eye, and actually ripping out > the incumbent backend, together with its implied promises and contracts and > whatever, will expose that. > > Your platform may be different, but if so, it would be the first that I've > seen. I wouldn't underestimate the staying power and gravitational field of > whatever switch platform you go with. > > -- Alex > > -- > Alex Balashov > Principal Consultant > Evariste Systems LLC > Web: https://evaristesys.com > Tel: +1-706-510-6800 > > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops >
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
