CloudServices/Identity Attached Storage: Difference between revisions

CloudServices/Identity Attached Storage (view source)

Revision as of 20:13, 10 November 2014

1,482 bytes added , 10 November 2014

initial commit

Edwong

Confirmed users

964

edits

@@ Line 1: / Line 1: @@
 = Overview =
-Identity Attached Storage is a synced storage facility
+Identity Attached Storage is simple cloud storage for authenticated user agents.
-= Goals =
+= RoadMap =
+{| class="wikitable"
+|-
+! Milestone !! Name !! Description
+|-
+| M1 || FxA MVP || Partner with FxA Service and accelerate and enable rapid prototyping
+|-
+| M2 || Web Dev MVP || Solve general web dev challenges
+|-
+| M3 || Expanding Service || Expanding the storage to partners
+|}
-= RoadMap =
+= M1 Goals =
+* Partner with an Firefox Accounts (FxA) product (sync, marketplace, Fennec) to drive feature set and scale deployment. From this partnership, we'll acquire key insights, identify value proposition, and potential for next iteration.
+* Build a foundational set of tools (authentication and storage) for Mozillians to rapidly prototype client features with simple cloud services.
+* M1 is good for open community enabling white label implementation of FxA plus FxA storage.
+= M2 Goals =
+* Learning from M1 we can gain clarity on how we can open the product for solving general web development problems.
+= FAQ =
+* Why is FxA required in M1?
+** Building a successful MVP benefits from partnering with client product rather than build an api and hope for adoption.  Products will help refine and force the appropriate decisions earlier in the development process rather than at the point of implementation. FxA simplifies some of the initial challenges that bloat product development.  M2 offers opportunities to decentralize the service.
+* Why this is not a generic kv store?
+** A key difference is that this attached storage behaves more like sync rather than a pure database.