https://devsummit.aspirationtech.org/index.php?title=Sagrada:_Mozilla_Services,_the_Cloud,_and_You&feed=atom&action=historySagrada: Mozilla Services, the Cloud, and You - Revision history2024-03-29T02:25:15ZRevision history for this page on the wikiMediaWiki 1.35.1https://devsummit.aspirationtech.org/index.php?title=Sagrada:_Mozilla_Services,_the_Cloud,_and_You&diff=475&oldid=prevVivian: 1 revision imported2015-05-05T18:25:08Z<p>1 revision imported</p>
<p><b>New page</b></p><div>mozilla cloud<br />
<br />
* survey of "groovy" things mozilla is doing - services and apps in rob's group<br />
* where do we go from there?<br />
<br />
* is mozilla planning cloud db services?<br />
* will mozilla provide some sort of alternative to google docs, with<br />
more security?<br />
<br />
<br />
what we have now is not a complete cloud solution -- more like amazon<br />
cloud services<br />
<br />
building a platform to provide value-added stuff for firefox<br />
<br />
mozilla has knowledge and infrastructure to host cloud apps, but can't<br />
afford to build and maintain wildly successful web services for free<br />
in perpetuity. how can we do this sustainably without selling out our<br />
users?<br />
<br />
at its heart, mozilla is a nonprofit--there's a nonprofit foundation<br />
that owns the mozilla corporation, a for-profit company<br />
<br />
all the money that the corporation brings in finds its way back to the<br />
foundation. corporation status allows mozilla to do certain kinds of<br />
business deals<br />
<br />
core mission is free software, privacy, standards, security by design<br />
<br />
first service that moz built was sync--passing tabs, history,<br />
bookmarks, and creds between firefox installs (phone, laptop, work,<br />
etc). 10 million sync users. client side encryption.<br />
<br />
next: end user notifications. html5 open standards initiative for site<br />
notifications. removes burden from site builders, gives tools &<br />
choices back to users<br />
<br />
browser ID: browser based identity services<br />
<br />
all of these services share certain features/needs:<br />
* storage (database)<br />
* messaging (queues passing notifications or actions back and forth)<br />
* logging<br />
<br />
right now moz is calling this platform sagrada. includes a key-value<br />
store, message queues, metrics/logging, and then an app framework on<br />
top of that.<br />
<br />
(key-value store) (message queues) (metrics/logging)<br />
\\ || // (linked by http)<br />
[[[[ ------------- app framework ------------- ]]]]<br />
<br />
sync is launched; these pieces are being built based on features<br />
already in sync. these are server-side pieces. app frameworks in<br />
python with pyramid, or in node.js<br />
<br />
http://hg.mozilla.org/services or http://github.com/mozilla-services<br />
<br />
these are all core building blocks that all sorts of applications<br />
need. the first crowd that will be really interested in this will be<br />
firefox extension developers.<br />
<br />
the audience goes beyond that, though: already, you can run your own<br />
sync server.<br />
<br />
key-value store is like a db that just stores keys and values.<br />
sometimes they handle nested values. cassandra, google's big table,<br />
etc.<br />
<br />
* would it be possible to do something like use sync to sync the<br />
contacts in peoples' phones?<br />
-- yeah, that's possible. sync is not a backup service. it's just http<br />
and pushing data around.<br />
<br />
* have you thought about relational stores (like redis)?<br />
-- not really, it doesn't map as clearly to http and transparent,<br />
horizontal storage (ACID). though, right now sync actually has mysql<br />
on the backend for legacy reasons.<br />
<br />
* does the key-value store handle locking, consistently, etc? ACID<br />
(atomicity, consistency, ...)<br />
-- key value store is typically not--there might be latency between<br />
the instant you put data in, and when you can get that data back in a<br />
query. makes building infrastructure without a single point of failure<br />
much easier, but gives up immediate consistency.<br />
<br />
sustainability models<br />
<br />
* payment for usage past a certain point? ie, developer/small-scale<br />
usage might be free, larger storage by organizations or companies<br />
might pay?<br />
* host it yourself? build an ecosystem of hosts providing these services?<br />
* are free models harmful for sustainability reasons?<br />
* does mozilla want to take on the task of providing cloud services?<br />
* building more apps on top of these services--mozilla has a limited<br />
set of applications on the roadmap; there will be room and support for<br />
a larger ecosystem of apps around these services<br />
<br />
not services, but related and worth mentioning: B2G ("Boot 2 Gecko")<br />
<br />
* gecko is the firefox rendering engine--turns html into a rendered<br />
page. works in tandem with spider monkey, the javascript engine.<br />
* gecko is everything inside the window that is not scrollbars, window<br />
header, etc.<br />
* chromeOS, b2g, web as platform<br />
* right now, what you can do with a browser is... browse. as the web<br />
becomes more of a platform, there will be more oportunities for this<br />
kind of system.<br />
<br />
* chrome vs. firefox and moz business model?<br />
-- actually, google's support of moz is not charity. it's payment for<br />
google as the default search engine in firefox.<br />
<br />
* right now, native apps have a more developed platform. soon, html5<br />
and javascript apps will run cross-platform.<br />
* boot 2 gecko will have all html5 and javascript apps and os APIs<br />
<br />
* accesibility built into the core of boot 2 gecko would be really<br />
helpful--chromeOS already does a good job of this<br />
* new operating systems mean that there are screen reader vendors for<br />
that OS yet, so it's hard to get started<br />
* this is primarily targeted at phones, and spoken aloud text and<br />
voice activated behaviors are already part of the landscape<br />
* android was really bad at accessibility at first, now it's nearly<br />
usable for people with vision disabilities, and ice cream sandwich is<br />
going to be much better.</div>Vivian