mediumConceptDesignMidSenior
What do network slicing and edge computing change for the systems that sell and provision a service?
4 min readUpdated 2026-08-15
Answer
Short answer
They turn a service into a parameterised, capacity-constrained thing with a location. The catalogue must model performance characteristics and a site, the order flow gains a serviceability and reservation step that can legitimately say no, and SLA measurement has to feed billing.
Was this answer helpful?
Likely follow-ups
- Where in the order journey does serviceability belong, and what does the customer see when it fails?
- How would you model a service whose latency target only holds relative to a particular edge site?
- What has to be true before you can offer a service credit for a missed latency target?
- Which parts of an enterprise slice order are still a manual commercial process, and why?
Related questions
- A flash sale decrements stock from many threads. Do you go optimistic or pessimistic, and how do you prove nothing oversold?mediumSame kind of round: design5 min
- You are building a user-profile service. Key-value store or document database: what decides it?mediumSame kind of round: design4 min
- What is the KV cache, and why does it decide how many users one GPU can serve?hardSame kind of round: concept4 min
- Your team wants to expose internal systems to an agent through MCP servers. What does the Model Context Protocol standardise, and what does it leave you to secure?hardSame kind of round: concept5 min