Add a comparison page to the site. #30
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,66 @@ | ||||||
| --- | ||||||
| title: Comparison to alternatives | ||||||
| sort_rank: 30 | ||||||
| --- | ||||||
|
|
||||||
| # Comparisons | ||||||
|
|
||||||
| We are often asked how Xmidt+Webpa compares to some alternative. It's a great | ||||||
|
There was a problem hiding this comment.
Suggested change
There was a problem hiding this comment. It might be nice to explain what XMiDT and WebPA are briefly, to make it clear why here at the beginning we are saying "XMiDT+WebPA" but towards the end we're only talking about XMiDT. |
||||||
| question. By itself Xmidt is difficult to compare directly to other systems | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| primarily due to the fundamental differences in architecture & different project | ||||||
| goals. | ||||||
|
|
||||||
| Xmidt by design is **not** coupled with any data models. | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| This allows for inclusion of all manner of data models. TR-181, TR-104, custom | ||||||
| Msgpack or JSON are all no problem. Any system tightly coupled with one of the | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| `TR-181` | `TR-104` | `TR-357` | etc, fundamentally couple the service life of | ||||||
| the entire ecosystem to the use of these particular models. Xmidt's architecture | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| is designed to avoid this coupling. None of the other existing services have | ||||||
| this design goal as a core system value. | ||||||
|
|
||||||
| Xmidt, Webpa, Codex and the ecosystem are designed to be an 'à la carte' | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| solution. This includes the cloud components, the client components and the | ||||||
| data models available. You get the choice of which services you want to deploy. | ||||||
| The service you need may be to access the existing TR-181 or TR-104 data | ||||||
| model on your device (Webpa+Webpa Client). It may be an alternative cloud | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| managed event scheduler (Aker Client) or something that is custom and | ||||||
| proprietary to your needs. | ||||||
|
|
||||||
| The Xmidt community's focus is to give you the easy to use building blocks so | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| you can best assemble the system that works best for your use cases. | ||||||
|
There was a problem hiding this comment.
Suggested change
Two |
||||||
|
|
||||||
| # Comparison Table of Xmidt+Webpa to TR-069+ACS & USP | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| To help provide a basic comparison between the 3 solutions we usually get | ||||||
| questions about, we are limited the scope to just TR-181 or similar access. | ||||||
|
There was a problem hiding this comment.
Suggested change
There was a problem hiding this comment. Whose scope are we limiting? XMiDT/WebPA's scope and the services we deploy on our side? Or focusing on a subset of functionality provided by the other solutions? I assume the first, but think it might be nice to clarify a bit. |
||||||
|
|
||||||
| TR-069 and USP/TR-369 appear only available as proprietary only solution end | ||||||
|
There was a problem hiding this comment.
Suggested change
Are there multiple solutions or just one? I made it plural because I assume there is more than one. |
||||||
| to end. | ||||||
|
|
||||||
|
|
||||||
| | Category | TR-069<sup>[2]</sup> | USP<sup>[2]</sup> | Xmidt+Webpa | | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| |:------------------------------------------------------------------|:--------------------------------------------:|:---------------------------------------------:|:----------------------------------------:| | ||||||
| |End-to-End Open Source Solution | <i class="fas fa-times-circle no"></i> | <i class="fas fa-times-circle no"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
|
There was a problem hiding this comment. Is there a reason to use the |
||||||
| |All Components Available via Business Friendly Apache 2.0 License | <i class="fas fa-times-circle no"></i> | <i class="fas fa-times-circle no"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Zero Licensing Costs | <i class="fas fa-times-circle no"></i> | <i class="fas fa-times-circle no"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Inclusive and Extensible Ecosystem at Client or Server Levels | <i class="fas fa-times-circle no"></i> | <i class="fas fa-times-circle no"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Supports Multiple Management Servers | <i class="fas fa-times-circle no"></i> | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Has Efficient Data Encoding | <i class="fas fa-times-circle no"></i> | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Has an Always-On Communication Mechanism | <i class="fas fa-times-circle no"></i> | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Utilizes a Device:2 (TR-181i2) Driven Data Model | <i class="fas fa-times-circle no"></i> | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Schema Drive Protocol Definition | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
|
There was a problem hiding this comment. What is Schema Drive Protocol? Should this be Schema Driven Protocol? |
||||||
| |Defines a Robust Set of Operations | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |May Leverage a Transport Layer Security Mechanism | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Provides an Access Control Mechanism<sup>[1]</sup> | 1/2 | <i class="fas fa-check-circle yes"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Provides a Secure Clean/Screen Solution for 3rd Party Services | <i class="fas fa-times-circle no"></i> | <i class="fas fa-times-circle no"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Easy to Scale (100 - +50M CPEs)<sup>[3]</sup> | <i class="fas fa-times-circle no"></i> | <i class="fas fa-question-circle maybe"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Easy to Scale (100 - +100K events/second)<sup>[3]</sup> | <i class="fas fa-times-circle no"></i> | <i class="fas fa-question-circle maybe"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Upgradable Without Outages at Scale<sup>[3]</sup> | <i class="fas fa-question-circle maybe"></i> | <i class="fas fa-question-circle maybe"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
| |Functions Properly With Complete Datacenter Failure<sup>[3]</sup> | <i class="fas fa-question-circle maybe"></i> | <i class="fas fa-question-circle maybe"></i> | <i class="fas fa-check-circle yes"></i> | | ||||||
|
There was a problem hiding this comment. Maybe this could be worded slightly differently? I read this as "XMiDT keeps working even if every datacenter it's in fails" which pretty much seems impossible. I think this is supposed to tell us "in a multi datacenter setup, if one datacenter completely fails XMiDT will continue to function properly". Not sure a succinct way to say that.
Comment on lines
+41
to
+59
There was a problem hiding this comment. It might be nice to explain how XMiDT accomplishes some of these things? Not sure that we want to include that on this page, but maybe another page where we go into some amount of detail explaining how we check each of these boxes and more information about how to set XMiDT up to accomplish these things. It can help add credibility to our claims. There was a problem hiding this comment. Good points. I'll see if I can do better with this. |
||||||
|
|
||||||
|
|
||||||
| Notes: | ||||||
|
|
||||||
| * `[1]` - This is an optional 'à la carte' Xmidt feature where one available approach is to use `partner-id`. | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| * `[2]` - Depends on your vendor. | ||||||
| * `[3]` - Xmidt behavior confirmed by the Comcast team. | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.