23 Jun Rule #2 For Using Satellite Services
Solution design with Satellite made easy
YES, there are two basic rules to designing satellite solutions, and NO, these rules are not complex engineering and mathematical rules. It is simply understanding where satellite technology maps into our integrated connected world and for what application satellite works perfectly. As for anything else in life, if you use a tool in the wrong application you can’t blame the tool for not working.
Simple. Somewhat common sense… And then again, we all know common sense is not so common after all.
Many architects will simply not consider satellite because they still believe the 3 myths about satellite – that it is expensive, slow and has a latency problem. The reality of satellite services today is very different and we shared some thoughts on the 3 myths in other InfoPosts.
Remember Rule #2 when you have to deliver a stand-by service on a “pay-per-use” cost model, or you have to provide 99,95% uptime to a business-critical operation, or you have to connect all business premises of the customer and 10% of those are “off-grid” and not connected to the telcos. These are all scenarios where you need satellite and where satellite solutions will be the best cost-performance-reliability option.
And when you need satellite – then use it. Meaning satellite is reliable, it is fast, it handles voice, it costs less than LTE, it is swift to implement, it is available anywhere, it has no dependency on core infrastructure. There is really no reason for you not to include satellite in your network architecture.
There is a range of specialist and niche applications where satellite services are the number 1 choice, for these applications you really do not have another technology solution option. What you do need though is to realise the benefits of satellite, what architecture models fit the nature of satellite services and then simply use satellite in these use cases.