Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi All, I also think that this will be a great addition to Apache and I should be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > stack for web & mobile applications based on RESTful APIs, as an Apache > Incubator podling. > > Here is a link to the proposal: >https://wiki.apache.org/incubator/UsergridProposal > > It is also pasted below: > > = Usergrid Proposal = > > == Abstract == > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > applications, based on RESTful APIs. > > > == Proposal == > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) > composed > of an integrated distributed NoSQL database, application layer and client > tier with SDKs for developers looking to rapidly build web and/or mobile > applications. It provides elementary services (user registration & > management, data storage, file storage, queues) and retrieval features > (full > text search, geolocation search, joins) to power common app features. > > It is a multi-tenant system designed for deployment to public cloud > environments (such as Amazon Web Services, Rackspace, etc.) or to run on > traditional server infrastructures so that anyone can run their own private > BaaS deployment. > > For architects and back-end teams, it aims to provide a distributed, easily > extendable, operationally predictable and highly scalable solution. For > front-end developers, it aims to simplify the development process by > enabling them to rapidly build and operate mobile and web applications > without requiring backend expertise. > > > == Background == > > Developing web or mobile applications obviously necessitates writing and > maintaining more than just front-end code. Even simple applications can > implicitly rely on server code being run to store users, perform database > queries, serve images and video files, etc. Developing and maintaining such > backend services requires skills not always available or expected of app > development teams. Beyond that, the proliferation of apps inside of > companies leads to the creation of many different, ad-hoc, unequally > maintained backend solutions created by employees and contractors alike and > hosted on a wide variety of environments. This is causing poor resource > usage, operational issues, as well as security, privacy & compliance > concerns. > > In response to this problem, companies have long tried to standardize their > server-side stack or unify them behind an ESB or API strategy. > Backends-as-a-Service follow a similar approach but their unique > characteristic is strongly tying 1) a persistence tier (typically a > database), 2) a server-side application tier delivering a set of common > services and 3) a set of client-side application interface mechanisms. For > example, a BaaS could package 1) MongoDB with 2) a node.js application that > offers access through 3) WebSockets. In the case of Usergrid, the trifecta > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > The Backend-as-a-Service approach has steadily gained popularity in the > last > few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, > each operating tens of thousands of apps for tens of thousands of > developers. The trend has already reached large organizations as well, with > global companies such as Korea Telecom internally building a privately-run > BaaS platform. But so far, there have been limited options for developers > that want a non-proprietary, open option for hosting and providing these > services themselves, or for enterprise and government users who want to > provide these capabilities from their own data centers, especially on a > very > large scale. > > > == Rationale == > > The issue this proposal deals with is implicit in the name. > Backend-as-a-Service platforms are usually offered solely as proprietary > cloud services. They are typically closed sourced, hosted on public clouds, > and require subscription payment. Usergrid opens the playing field, by > making a fully-featured BaaS platform freely available to all. This > includes > developers that previously could not afford them, such as mobile > enthusiasts, small boutiques, and cost-sensitive startups. This also > includes large companies that benefit from a reference implementation they > can deploy in trust, or extend to their needs without losing time writing > less-vetted, less-performant boilerplate functionality. > > Usergrid has been open source since 2011 and has grown as an independent > project, garnering 11 primary committers, 35 total contributors, 260+ > participants on its mailing list, with 3,700+ commits, 200+ external > contributions, 350+ stars and
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
WSO2 affiliation? On Sep 24, 2013, at 9:49 AM, Dulitha Rasanga Wijewantha wrote: > As I have requested before can you add me into the committer list as well. I > am interested in contributing to user-grid. > > Thanks > > Dulitha R. Wijewantha Software Engineer > Tel: 94112793140 | Mobile:94112793140 > dulit...@gmail.com |http://dulithawijewantha.com > > On Sep 24, 2013, at 7:05 PM, Jim Jagielski wrote: > >> Added. >> >> On Sep 24, 2013, at 9:24 AM, Nirmal Fernando wrote: >> >>> Hi Jim, >>> >>> On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski wrote: >>> No problem... usually, when someone simply sez they are interested in contributing, I take that as an indication that when the podling is started, they will, well, find time to contribute. I don't interpret that as a "please add me as a committer", which is a formal request to be added as part of the proposal. That's why you weren't added, but I'll add you now. >>> >>> Thanks. >>> Am I correct in assuming that the affiliation is WSO2? >>> >>> Yes. >>> On Sep 24, 2013, at 8:21 AM, Nirmal Fernando wrote: > Hi Jim, > > As you can see below, I've showed my interest to join this project, but it > seems like I sent the email using a different > email address (not what I've subscribed to general incubator from) and > email went to moderation. :( > > As I showed my interest before the voting started up, could you please add > me into the committers list? or else please let me know how to add myself > as a committer. > > Thanks > > On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando < nirmal070...@apache.org>wrote: > >> Hi All, >> >> I also think that this will be a great addition to Apache and I should be >> able to find some time to contribute to this project. Especially on the >> deployment/integration aspects on PaaSes and different IaaSes. >> >> Nirmal Fernando, >> PPMC Member and Committer of Apache Stratos, >> Senior Software Engineer, WSO2 >> >> On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: >> >>> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service >>> stack for web & mobile applications based on RESTful APIs, as an Apache >>> Incubator podling. >>> >>> Here is a link to the proposal: >>> https://wiki.apache.org/incubator/UsergridProposal >>> >>> It is also pasted below: >>> >>> = Usergrid Proposal = >>> >>> == Abstract == >>> >>> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile >>> applications, based on RESTful APIs. >>> >>> >>> == Proposal == >>> >>> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) >>> composed >>> of an integrated distributed NoSQL database, application layer and client >>> tier with SDKs for developers looking to rapidly build web and/or mobile >>> applications. It provides elementary services (user registration & >>> management, data storage, file storage, queues) and retrieval features >>> (full >>> text search, geolocation search, joins) to power common app features. >>> >>> It is a multi-tenant system designed for deployment to public cloud >>> environments (such as Amazon Web Services, Rackspace, etc.) or to run on >>> traditional server infrastructures so that anyone can run their own >>> private >>> BaaS deployment. >>> >>> For architects and back-end teams, it aims to provide a distributed, >>> easily >>> extendable, operationally predictable and highly scalable solution. For >>> front-end developers, it aims to simplify the development process by >>> enabling them to rapidly build and operate mobile and web applications >>> without requiring backend expertise. >>> >>> >>> == Background == >>> >>> Developing web or mobile applications obviously necessitates writing and >>> maintaining more than just front-end code. Even simple applications can >>> implicitly rely on server code being run to store users, perform database >>> queries, serve images and video files, etc. Developing and maintaining >>> such >>> backend services requires skills not always available or expected of app >>> development teams. Beyond that, the proliferation of apps inside of >>> companies leads to the creation of many different, ad-hoc, unequally >>> maintained backend solutions created by employees and contractors alike >>> and >>> hosted on a wide variety of environments. This is causing poor resource >>> usage, operational issues, as well as security, privacy & compliance >>> concerns. >>> >>> In response to this problem, companies have long tried to standardize >>> their >>> se
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Correction: Imesh Gunaratne Committer & PPMC Member, Apache Stratos (Incubating) Technical Lead, WSO2 Inc Thanks Imesh On Tue, Sep 24, 2013 at 7:02 PM, Imesh Gunaratne wrote: > Hi Jim, > > Thanks for your clarification. > > I could not express my interest in joining Usergrid as a committer before > we started the Voting process. > If it is not a problem, please add me as a committer. > > Thanks > > Imesh Gunaratne > Committer & PMC Member, Apache Stratos > Technical Lead, WSO2 Inc > > > On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski wrote: > >> No problem... usually, when someone simply sez they are interested >> in contributing, I take that as an indication that when the podling >> is started, they will, well, find time to contribute. I don't >> interpret that as a "please add me as a committer", which is a >> formal request to be added as part of the proposal. That's why >> you weren't added, but I'll add you now. >> >> Am I correct in assuming that the affiliation is WSO2? >> >> On Sep 24, 2013, at 8:21 AM, Nirmal Fernando >> wrote: >> >> > Hi Jim, >> > >> > As you can see below, I've showed my interest to join this project, but >> it >> > seems like I sent the email using a different >> > email address (not what I've subscribed to general incubator from) and >> > email went to moderation. :( >> > >> > As I showed my interest before the voting started up, could you please >> add >> > me into the committers list? or else please let me know how to add >> myself >> > as a committer. >> > >> > Thanks >> > >> > On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando < >> nirmal070...@apache.org>wrote: >> > >> >> Hi All, >> >> >> >> I also think that this will be a great addition to Apache and I should >> be >> >> able to find some time to contribute to this project. Especially on the >> >> deployment/integration aspects on PaaSes and different IaaSes. >> >> >> >> Nirmal Fernando, >> >> PPMC Member and Committer of Apache Stratos, >> >> Senior Software Engineer, WSO2 >> >> >> >> On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski >> wrote: >> >> >> >>> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service >> >>> stack for web & mobile applications based on RESTful APIs, as an >> Apache >> >>> Incubator podling. >> >>> >> >>> Here is a link to the proposal: >> >>> https://wiki.apache.org/incubator/UsergridProposal >> >>> >> >>> It is also pasted below: >> >>> >> >>> = Usergrid Proposal = >> >>> >> >>> == Abstract == >> >>> >> >>> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile >> >>> applications, based on RESTful APIs. >> >>> >> >>> >> >>> == Proposal == >> >>> >> >>> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) >> >>> composed >> >>> of an integrated distributed NoSQL database, application layer and >> client >> >>> tier with SDKs for developers looking to rapidly build web and/or >> mobile >> >>> applications. It provides elementary services (user registration & >> >>> management, data storage, file storage, queues) and retrieval features >> >>> (full >> >>> text search, geolocation search, joins) to power common app features. >> >>> >> >>> It is a multi-tenant system designed for deployment to public cloud >> >>> environments (such as Amazon Web Services, Rackspace, etc.) or to run >> on >> >>> traditional server infrastructures so that anyone can run their own >> >>> private >> >>> BaaS deployment. >> >>> >> >>> For architects and back-end teams, it aims to provide a distributed, >> >>> easily >> >>> extendable, operationally predictable and highly scalable solution. >> For >> >>> front-end developers, it aims to simplify the development process by >> >>> enabling them to rapidly build and operate mobile and web applications >> >>> without requiring backend expertise. >> >>> >> >>> >> >>> == Background == >> >>> >> >>> Developing web or mobile applications obviously necessitates writing >> and >> >>> maintaining more than just front-end code. Even simple applications >> can >> >>> implicitly rely on server code being run to store users, perform >> database >> >>> queries, serve images and video files, etc. Developing and maintaining >> >>> such >> >>> backend services requires skills not always available or expected of >> app >> >>> development teams. Beyond that, the proliferation of apps inside of >> >>> companies leads to the creation of many different, ad-hoc, unequally >> >>> maintained backend solutions created by employees and contractors >> alike >> >>> and >> >>> hosted on a wide variety of environments. This is causing poor >> resource >> >>> usage, operational issues, as well as security, privacy & compliance >> >>> concerns. >> >>> >> >>> In response to this problem, companies have long tried to standardize >> >>> their >> >>> server-side stack or unify them behind an ESB or API strategy. >> >>> Backends-as-a-Service follow a similar approach but their unique >> >>> characteristic is strongly tying 1) a persistence tier (typically
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
As I have requested before can you add me into the committer list as well. I am interested in contributing to user-grid. Thanks Dulitha R. Wijewantha Software Engineer Tel: 94112793140 | Mobile:94112793140 dulit...@gmail.com |http://dulithawijewantha.com > On Sep 24, 2013, at 7:05 PM, Jim Jagielski wrote: > > Added. > >> On Sep 24, 2013, at 9:24 AM, Nirmal Fernando wrote: >> >> Hi Jim, >> >>> On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski wrote: >>> >>> No problem... usually, when someone simply sez they are interested >>> in contributing, I take that as an indication that when the podling >>> is started, they will, well, find time to contribute. I don't >>> interpret that as a "please add me as a committer", which is a >>> formal request to be added as part of the proposal. That's why >>> you weren't added, but I'll add you now. >> >> Thanks. >> >>> >>> Am I correct in assuming that the affiliation is WSO2? >> >> Yes. >> >>> >>> On Sep 24, 2013, at 8:21 AM, Nirmal Fernando >>> wrote: >>> Hi Jim, As you can see below, I've showed my interest to join this project, but >>> it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please >>> add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando < >>> nirmal070...@apache.org>wrote: > Hi All, > > I also think that this will be a great addition to Apache and I should >>> be > able to find some time to contribute to this project. Especially on the > deployment/integration aspects on PaaSes and different IaaSes. > > Nirmal Fernando, > PPMC Member and Committer of Apache Stratos, > Senior Software Engineer, WSO2 > >> On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: >> >> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service >> stack for web & mobile applications based on RESTful APIs, as an Apache >> Incubator podling. >> >> Here is a link to the proposal: >> https://wiki.apache.org/incubator/UsergridProposal >> >> It is also pasted below: >> >> = Usergrid Proposal = >> >> == Abstract == >> >> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile >> applications, based on RESTful APIs. >> >> >> == Proposal == >> >> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) >> composed >> of an integrated distributed NoSQL database, application layer and >>> client >> tier with SDKs for developers looking to rapidly build web and/or >>> mobile >> applications. It provides elementary services (user registration & >> management, data storage, file storage, queues) and retrieval features >> (full >> text search, geolocation search, joins) to power common app features. >> >> It is a multi-tenant system designed for deployment to public cloud >> environments (such as Amazon Web Services, Rackspace, etc.) or to run >>> on >> traditional server infrastructures so that anyone can run their own >> private >> BaaS deployment. >> >> For architects and back-end teams, it aims to provide a distributed, >> easily >> extendable, operationally predictable and highly scalable solution. For >> front-end developers, it aims to simplify the development process by >> enabling them to rapidly build and operate mobile and web applications >> without requiring backend expertise. >> >> >> == Background == >> >> Developing web or mobile applications obviously necessitates writing >>> and >> maintaining more than just front-end code. Even simple applications can >> implicitly rely on server code being run to store users, perform >>> database >> queries, serve images and video files, etc. Developing and maintaining >> such >> backend services requires skills not always available or expected of >>> app >> development teams. Beyond that, the proliferation of apps inside of >> companies leads to the creation of many different, ad-hoc, unequally >> maintained backend solutions created by employees and contractors alike >> and >> hosted on a wide variety of environments. This is causing poor resource >> usage, operational issues, as well as security, privacy & compliance >> concerns. >> >> In response to this problem, companies have long tried to standardize >> their >> server-side stack or unify them behind an ESB or API strategy. >> Backends-as-a-Service follow a similar approach but their unique >> characteristic is strongly tying 1) a persistence tier (typically a >> database), 2) a s
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Added. On Sep 24, 2013, at 9:24 AM, Nirmal Fernando wrote: > Hi Jim, > > On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski wrote: > >> No problem... usually, when someone simply sez they are interested >> in contributing, I take that as an indication that when the podling >> is started, they will, well, find time to contribute. I don't >> interpret that as a "please add me as a committer", which is a >> formal request to be added as part of the proposal. That's why >> you weren't added, but I'll add you now. >> > > Thanks. > >> >> Am I correct in assuming that the affiliation is WSO2? >> > > Yes. > >> >> On Sep 24, 2013, at 8:21 AM, Nirmal Fernando >> wrote: >> >>> Hi Jim, >>> >>> As you can see below, I've showed my interest to join this project, but >> it >>> seems like I sent the email using a different >>> email address (not what I've subscribed to general incubator from) and >>> email went to moderation. :( >>> >>> As I showed my interest before the voting started up, could you please >> add >>> me into the committers list? or else please let me know how to add myself >>> as a committer. >>> >>> Thanks >>> >>> On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando < >> nirmal070...@apache.org>wrote: >>> Hi All, I also think that this will be a great addition to Apache and I should >> be able to find some time to contribute to this project. Especially on the deployment/integration aspects on PaaSes and different IaaSes. Nirmal Fernando, PPMC Member and Committer of Apache Stratos, Senior Software Engineer, WSO2 On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > stack for web & mobile applications based on RESTful APIs, as an Apache > Incubator podling. > > Here is a link to the proposal: > https://wiki.apache.org/incubator/UsergridProposal > > It is also pasted below: > > = Usergrid Proposal = > > == Abstract == > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > applications, based on RESTful APIs. > > > == Proposal == > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) > composed > of an integrated distributed NoSQL database, application layer and >> client > tier with SDKs for developers looking to rapidly build web and/or >> mobile > applications. It provides elementary services (user registration & > management, data storage, file storage, queues) and retrieval features > (full > text search, geolocation search, joins) to power common app features. > > It is a multi-tenant system designed for deployment to public cloud > environments (such as Amazon Web Services, Rackspace, etc.) or to run >> on > traditional server infrastructures so that anyone can run their own > private > BaaS deployment. > > For architects and back-end teams, it aims to provide a distributed, > easily > extendable, operationally predictable and highly scalable solution. For > front-end developers, it aims to simplify the development process by > enabling them to rapidly build and operate mobile and web applications > without requiring backend expertise. > > > == Background == > > Developing web or mobile applications obviously necessitates writing >> and > maintaining more than just front-end code. Even simple applications can > implicitly rely on server code being run to store users, perform >> database > queries, serve images and video files, etc. Developing and maintaining > such > backend services requires skills not always available or expected of >> app > development teams. Beyond that, the proliferation of apps inside of > companies leads to the creation of many different, ad-hoc, unequally > maintained backend solutions created by employees and contractors alike > and > hosted on a wide variety of environments. This is causing poor resource > usage, operational issues, as well as security, privacy & compliance > concerns. > > In response to this problem, companies have long tried to standardize > their > server-side stack or unify them behind an ESB or API strategy. > Backends-as-a-Service follow a similar approach but their unique > characteristic is strongly tying 1) a persistence tier (typically a > database), 2) a server-side application tier delivering a set of common > services and 3) a set of client-side application interface mechanisms. >> For > example, a BaaS could package 1) MongoDB with 2) a node.js application > that > offers access through 3) WebSockets. In the case of Usergrid, the >> trifecta > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > The Backend-as-a-Service approach has steadily gained popul
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi Jim, Thanks for your clarification. I could not express my interest in joining Usergrid as a committer before we started the Voting process. If it is not a problem, please add me as a committer. Thanks Imesh Gunaratne Committer & PMC Member, Apache Stratos Technical Lead, WSO2 Inc On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski wrote: > No problem... usually, when someone simply sez they are interested > in contributing, I take that as an indication that when the podling > is started, they will, well, find time to contribute. I don't > interpret that as a "please add me as a committer", which is a > formal request to be added as part of the proposal. That's why > you weren't added, but I'll add you now. > > Am I correct in assuming that the affiliation is WSO2? > > On Sep 24, 2013, at 8:21 AM, Nirmal Fernando > wrote: > > > Hi Jim, > > > > As you can see below, I've showed my interest to join this project, but > it > > seems like I sent the email using a different > > email address (not what I've subscribed to general incubator from) and > > email went to moderation. :( > > > > As I showed my interest before the voting started up, could you please > add > > me into the committers list? or else please let me know how to add myself > > as a committer. > > > > Thanks > > > > On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando < > nirmal070...@apache.org>wrote: > > > >> Hi All, > >> > >> I also think that this will be a great addition to Apache and I should > be > >> able to find some time to contribute to this project. Especially on the > >> deployment/integration aspects on PaaSes and different IaaSes. > >> > >> Nirmal Fernando, > >> PPMC Member and Committer of Apache Stratos, > >> Senior Software Engineer, WSO2 > >> > >> On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: > >> > >>> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > >>> stack for web & mobile applications based on RESTful APIs, as an Apache > >>> Incubator podling. > >>> > >>> Here is a link to the proposal: > >>> https://wiki.apache.org/incubator/UsergridProposal > >>> > >>> It is also pasted below: > >>> > >>> = Usergrid Proposal = > >>> > >>> == Abstract == > >>> > >>> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > >>> applications, based on RESTful APIs. > >>> > >>> > >>> == Proposal == > >>> > >>> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) > >>> composed > >>> of an integrated distributed NoSQL database, application layer and > client > >>> tier with SDKs for developers looking to rapidly build web and/or > mobile > >>> applications. It provides elementary services (user registration & > >>> management, data storage, file storage, queues) and retrieval features > >>> (full > >>> text search, geolocation search, joins) to power common app features. > >>> > >>> It is a multi-tenant system designed for deployment to public cloud > >>> environments (such as Amazon Web Services, Rackspace, etc.) or to run > on > >>> traditional server infrastructures so that anyone can run their own > >>> private > >>> BaaS deployment. > >>> > >>> For architects and back-end teams, it aims to provide a distributed, > >>> easily > >>> extendable, operationally predictable and highly scalable solution. For > >>> front-end developers, it aims to simplify the development process by > >>> enabling them to rapidly build and operate mobile and web applications > >>> without requiring backend expertise. > >>> > >>> > >>> == Background == > >>> > >>> Developing web or mobile applications obviously necessitates writing > and > >>> maintaining more than just front-end code. Even simple applications can > >>> implicitly rely on server code being run to store users, perform > database > >>> queries, serve images and video files, etc. Developing and maintaining > >>> such > >>> backend services requires skills not always available or expected of > app > >>> development teams. Beyond that, the proliferation of apps inside of > >>> companies leads to the creation of many different, ad-hoc, unequally > >>> maintained backend solutions created by employees and contractors alike > >>> and > >>> hosted on a wide variety of environments. This is causing poor resource > >>> usage, operational issues, as well as security, privacy & compliance > >>> concerns. > >>> > >>> In response to this problem, companies have long tried to standardize > >>> their > >>> server-side stack or unify them behind an ESB or API strategy. > >>> Backends-as-a-Service follow a similar approach but their unique > >>> characteristic is strongly tying 1) a persistence tier (typically a > >>> database), 2) a server-side application tier delivering a set of common > >>> services and 3) a set of client-side application interface mechanisms. > For > >>> example, a BaaS could package 1) MongoDB with 2) a node.js application > >>> that > >>> offers access through 3) WebSockets. In the case of Usergrid, the > trifecta > >>> is
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi Jim, On Tue, Sep 24, 2013 at 6:29 PM, Jim Jagielski wrote: > No problem... usually, when someone simply sez they are interested > in contributing, I take that as an indication that when the podling > is started, they will, well, find time to contribute. I don't > interpret that as a "please add me as a committer", which is a > formal request to be added as part of the proposal. That's why > you weren't added, but I'll add you now. > Thanks. > > Am I correct in assuming that the affiliation is WSO2? > Yes. > > On Sep 24, 2013, at 8:21 AM, Nirmal Fernando > wrote: > > > Hi Jim, > > > > As you can see below, I've showed my interest to join this project, but > it > > seems like I sent the email using a different > > email address (not what I've subscribed to general incubator from) and > > email went to moderation. :( > > > > As I showed my interest before the voting started up, could you please > add > > me into the committers list? or else please let me know how to add myself > > as a committer. > > > > Thanks > > > > On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando < > nirmal070...@apache.org>wrote: > > > >> Hi All, > >> > >> I also think that this will be a great addition to Apache and I should > be > >> able to find some time to contribute to this project. Especially on the > >> deployment/integration aspects on PaaSes and different IaaSes. > >> > >> Nirmal Fernando, > >> PPMC Member and Committer of Apache Stratos, > >> Senior Software Engineer, WSO2 > >> > >> On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: > >> > >>> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > >>> stack for web & mobile applications based on RESTful APIs, as an Apache > >>> Incubator podling. > >>> > >>> Here is a link to the proposal: > >>> https://wiki.apache.org/incubator/UsergridProposal > >>> > >>> It is also pasted below: > >>> > >>> = Usergrid Proposal = > >>> > >>> == Abstract == > >>> > >>> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > >>> applications, based on RESTful APIs. > >>> > >>> > >>> == Proposal == > >>> > >>> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) > >>> composed > >>> of an integrated distributed NoSQL database, application layer and > client > >>> tier with SDKs for developers looking to rapidly build web and/or > mobile > >>> applications. It provides elementary services (user registration & > >>> management, data storage, file storage, queues) and retrieval features > >>> (full > >>> text search, geolocation search, joins) to power common app features. > >>> > >>> It is a multi-tenant system designed for deployment to public cloud > >>> environments (such as Amazon Web Services, Rackspace, etc.) or to run > on > >>> traditional server infrastructures so that anyone can run their own > >>> private > >>> BaaS deployment. > >>> > >>> For architects and back-end teams, it aims to provide a distributed, > >>> easily > >>> extendable, operationally predictable and highly scalable solution. For > >>> front-end developers, it aims to simplify the development process by > >>> enabling them to rapidly build and operate mobile and web applications > >>> without requiring backend expertise. > >>> > >>> > >>> == Background == > >>> > >>> Developing web or mobile applications obviously necessitates writing > and > >>> maintaining more than just front-end code. Even simple applications can > >>> implicitly rely on server code being run to store users, perform > database > >>> queries, serve images and video files, etc. Developing and maintaining > >>> such > >>> backend services requires skills not always available or expected of > app > >>> development teams. Beyond that, the proliferation of apps inside of > >>> companies leads to the creation of many different, ad-hoc, unequally > >>> maintained backend solutions created by employees and contractors alike > >>> and > >>> hosted on a wide variety of environments. This is causing poor resource > >>> usage, operational issues, as well as security, privacy & compliance > >>> concerns. > >>> > >>> In response to this problem, companies have long tried to standardize > >>> their > >>> server-side stack or unify them behind an ESB or API strategy. > >>> Backends-as-a-Service follow a similar approach but their unique > >>> characteristic is strongly tying 1) a persistence tier (typically a > >>> database), 2) a server-side application tier delivering a set of common > >>> services and 3) a set of client-side application interface mechanisms. > For > >>> example, a BaaS could package 1) MongoDB with 2) a node.js application > >>> that > >>> offers access through 3) WebSockets. In the case of Usergrid, the > trifecta > >>> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > >>> > >>> The Backend-as-a-Service approach has steadily gained popularity in the > >>> last > >>> few years with cloud providers such Parse.com, Stackmob.com and > >>> Kinvey.com, > >>> each operating ten
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
No problem... usually, when someone simply sez they are interested in contributing, I take that as an indication that when the podling is started, they will, well, find time to contribute. I don't interpret that as a "please add me as a committer", which is a formal request to be added as part of the proposal. That's why you weren't added, but I'll add you now. Am I correct in assuming that the affiliation is WSO2? On Sep 24, 2013, at 8:21 AM, Nirmal Fernando wrote: > Hi Jim, > > As you can see below, I've showed my interest to join this project, but it > seems like I sent the email using a different > email address (not what I've subscribed to general incubator from) and > email went to moderation. :( > > As I showed my interest before the voting started up, could you please add > me into the committers list? or else please let me know how to add myself > as a committer. > > Thanks > > On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando > wrote: > >> Hi All, >> >> I also think that this will be a great addition to Apache and I should be >> able to find some time to contribute to this project. Especially on the >> deployment/integration aspects on PaaSes and different IaaSes. >> >> Nirmal Fernando, >> PPMC Member and Committer of Apache Stratos, >> Senior Software Engineer, WSO2 >> >> On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: >> >>> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service >>> stack for web & mobile applications based on RESTful APIs, as an Apache >>> Incubator podling. >>> >>> Here is a link to the proposal: >>> https://wiki.apache.org/incubator/UsergridProposal >>> >>> It is also pasted below: >>> >>> = Usergrid Proposal = >>> >>> == Abstract == >>> >>> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile >>> applications, based on RESTful APIs. >>> >>> >>> == Proposal == >>> >>> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) >>> composed >>> of an integrated distributed NoSQL database, application layer and client >>> tier with SDKs for developers looking to rapidly build web and/or mobile >>> applications. It provides elementary services (user registration & >>> management, data storage, file storage, queues) and retrieval features >>> (full >>> text search, geolocation search, joins) to power common app features. >>> >>> It is a multi-tenant system designed for deployment to public cloud >>> environments (such as Amazon Web Services, Rackspace, etc.) or to run on >>> traditional server infrastructures so that anyone can run their own >>> private >>> BaaS deployment. >>> >>> For architects and back-end teams, it aims to provide a distributed, >>> easily >>> extendable, operationally predictable and highly scalable solution. For >>> front-end developers, it aims to simplify the development process by >>> enabling them to rapidly build and operate mobile and web applications >>> without requiring backend expertise. >>> >>> >>> == Background == >>> >>> Developing web or mobile applications obviously necessitates writing and >>> maintaining more than just front-end code. Even simple applications can >>> implicitly rely on server code being run to store users, perform database >>> queries, serve images and video files, etc. Developing and maintaining >>> such >>> backend services requires skills not always available or expected of app >>> development teams. Beyond that, the proliferation of apps inside of >>> companies leads to the creation of many different, ad-hoc, unequally >>> maintained backend solutions created by employees and contractors alike >>> and >>> hosted on a wide variety of environments. This is causing poor resource >>> usage, operational issues, as well as security, privacy & compliance >>> concerns. >>> >>> In response to this problem, companies have long tried to standardize >>> their >>> server-side stack or unify them behind an ESB or API strategy. >>> Backends-as-a-Service follow a similar approach but their unique >>> characteristic is strongly tying 1) a persistence tier (typically a >>> database), 2) a server-side application tier delivering a set of common >>> services and 3) a set of client-side application interface mechanisms. For >>> example, a BaaS could package 1) MongoDB with 2) a node.js application >>> that >>> offers access through 3) WebSockets. In the case of Usergrid, the trifecta >>> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. >>> >>> The Backend-as-a-Service approach has steadily gained popularity in the >>> last >>> few years with cloud providers such Parse.com, Stackmob.com and >>> Kinvey.com, >>> each operating tens of thousands of apps for tens of thousands of >>> developers. The trend has already reached large organizations as well, >>> with >>> global companies such as Korea Telecom internally building a privately-run >>> BaaS platform. But so far, there have been limited options for developers >>> that want a non-proprietary, open option
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi Jim, As you can see below, I've showed my interest to join this project, but it seems like I sent the email using a different email address (not what I've subscribed to general incubator from) and email went to moderation. :( As I showed my interest before the voting started up, could you please add me into the committers list? or else please let me know how to add myself as a committer. Thanks On Mon, Sep 23, 2013 at 2:46 PM, Nirmal Fernando wrote: > Hi All, > > I also think that this will be a great addition to Apache and I should be > able to find some time to contribute to this project. Especially on the > deployment/integration aspects on PaaSes and different IaaSes. > > Nirmal Fernando, > PPMC Member and Committer of Apache Stratos, > Senior Software Engineer, WSO2 > > On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: > >> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service >> stack for web & mobile applications based on RESTful APIs, as an Apache >> Incubator podling. >> >> Here is a link to the proposal: >>https://wiki.apache.org/incubator/UsergridProposal >> >> It is also pasted below: >> >> = Usergrid Proposal = >> >> == Abstract == >> >> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile >> applications, based on RESTful APIs. >> >> >> == Proposal == >> >> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) >> composed >> of an integrated distributed NoSQL database, application layer and client >> tier with SDKs for developers looking to rapidly build web and/or mobile >> applications. It provides elementary services (user registration & >> management, data storage, file storage, queues) and retrieval features >> (full >> text search, geolocation search, joins) to power common app features. >> >> It is a multi-tenant system designed for deployment to public cloud >> environments (such as Amazon Web Services, Rackspace, etc.) or to run on >> traditional server infrastructures so that anyone can run their own >> private >> BaaS deployment. >> >> For architects and back-end teams, it aims to provide a distributed, >> easily >> extendable, operationally predictable and highly scalable solution. For >> front-end developers, it aims to simplify the development process by >> enabling them to rapidly build and operate mobile and web applications >> without requiring backend expertise. >> >> >> == Background == >> >> Developing web or mobile applications obviously necessitates writing and >> maintaining more than just front-end code. Even simple applications can >> implicitly rely on server code being run to store users, perform database >> queries, serve images and video files, etc. Developing and maintaining >> such >> backend services requires skills not always available or expected of app >> development teams. Beyond that, the proliferation of apps inside of >> companies leads to the creation of many different, ad-hoc, unequally >> maintained backend solutions created by employees and contractors alike >> and >> hosted on a wide variety of environments. This is causing poor resource >> usage, operational issues, as well as security, privacy & compliance >> concerns. >> >> In response to this problem, companies have long tried to standardize >> their >> server-side stack or unify them behind an ESB or API strategy. >> Backends-as-a-Service follow a similar approach but their unique >> characteristic is strongly tying 1) a persistence tier (typically a >> database), 2) a server-side application tier delivering a set of common >> services and 3) a set of client-side application interface mechanisms. For >> example, a BaaS could package 1) MongoDB with 2) a node.js application >> that >> offers access through 3) WebSockets. In the case of Usergrid, the trifecta >> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. >> >> The Backend-as-a-Service approach has steadily gained popularity in the >> last >> few years with cloud providers such Parse.com, Stackmob.com and >> Kinvey.com, >> each operating tens of thousands of apps for tens of thousands of >> developers. The trend has already reached large organizations as well, >> with >> global companies such as Korea Telecom internally building a privately-run >> BaaS platform. But so far, there have been limited options for developers >> that want a non-proprietary, open option for hosting and providing these >> services themselves, or for enterprise and government users who want to >> provide these capabilities from their own data centers, especially on a >> very >> large scale. >> >> >> == Rationale == >> >> The issue this proposal deals with is implicit in the name. >> Backend-as-a-Service platforms are usually offered solely as proprietary >> cloud services. They are typically closed sourced, hosted on public >> clouds, >> and require subscription payment. Usergrid opens the playing field, by >> making a fully-featured BaaS platform freely available to all. This >> includes >> dev
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
It's great to see many cool and exciting new projects joining Apache Incubator. +1 from my side On Fri, Sep 20, 2013 at 3:54 PM, Sanjiva Weerawarana wrote: > +1 - there's a lot of overlap / commonality of objective between BaaS and > the set of services provided by Apache Stratos (incubating) to developers > of apps. I'm very happy to see this come to ASF and will be happy to mentor > if you guys need another one. > > Cheers, > > Sanjiva. > > > On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: > > > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > > stack for web & mobile applications based on RESTful APIs, as an Apache > > Incubator podling. > > > > Here is a link to the proposal: > >https://wiki.apache.org/incubator/UsergridProposal > > > > It is also pasted below: > > > > = Usergrid Proposal = > > > > == Abstract == > > > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > > applications, based on RESTful APIs. > > > > > > == Proposal == > > > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) > > composed > > of an integrated distributed NoSQL database, application layer and client > > tier with SDKs for developers looking to rapidly build web and/or mobile > > applications. It provides elementary services (user registration & > > management, data storage, file storage, queues) and retrieval features > > (full > > text search, geolocation search, joins) to power common app features. > > > > It is a multi-tenant system designed for deployment to public cloud > > environments (such as Amazon Web Services, Rackspace, etc.) or to run on > > traditional server infrastructures so that anyone can run their own > private > > BaaS deployment. > > > > For architects and back-end teams, it aims to provide a distributed, > easily > > extendable, operationally predictable and highly scalable solution. For > > front-end developers, it aims to simplify the development process by > > enabling them to rapidly build and operate mobile and web applications > > without requiring backend expertise. > > > > > > == Background == > > > > Developing web or mobile applications obviously necessitates writing and > > maintaining more than just front-end code. Even simple applications can > > implicitly rely on server code being run to store users, perform database > > queries, serve images and video files, etc. Developing and maintaining > such > > backend services requires skills not always available or expected of app > > development teams. Beyond that, the proliferation of apps inside of > > companies leads to the creation of many different, ad-hoc, unequally > > maintained backend solutions created by employees and contractors alike > and > > hosted on a wide variety of environments. This is causing poor resource > > usage, operational issues, as well as security, privacy & compliance > > concerns. > > > > In response to this problem, companies have long tried to standardize > their > > server-side stack or unify them behind an ESB or API strategy. > > Backends-as-a-Service follow a similar approach but their unique > > characteristic is strongly tying 1) a persistence tier (typically a > > database), 2) a server-side application tier delivering a set of common > > services and 3) a set of client-side application interface mechanisms. > For > > example, a BaaS could package 1) MongoDB with 2) a node.js application > that > > offers access through 3) WebSockets. In the case of Usergrid, the > trifecta > > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > > > The Backend-as-a-Service approach has steadily gained popularity in the > > last > > few years with cloud providers such Parse.com, Stackmob.com and > Kinvey.com, > > each operating tens of thousands of apps for tens of thousands of > > developers. The trend has already reached large organizations as well, > with > > global companies such as Korea Telecom internally building a > privately-run > > BaaS platform. But so far, there have been limited options for developers > > that want a non-proprietary, open option for hosting and providing these > > services themselves, or for enterprise and government users who want to > > provide these capabilities from their own data centers, especially on a > > very > > large scale. > > > > > > == Rationale == > > > > The issue this proposal deals with is implicit in the name. > > Backend-as-a-Service platforms are usually offered solely as proprietary > > cloud services. They are typically closed sourced, hosted on public > clouds, > > and require subscription payment. Usergrid opens the playing field, by > > making a fully-featured BaaS platform freely available to all. This > > includes > > developers that previously could not afford them, such as mobile > > enthusiasts, small boutiques, and cost-sensitive startups. This also > > includes large companies that benefit from a reference implementation > they > > can deploy in trust, or extend to the
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Of course :-). Apache is a great place to level everyone's interests .. On Mon, Sep 23, 2013 at 9:43 PM, Jim Jagielski wrote: > Yes, just as WSO2 has a financial interest in seeing Stratos > successful, so we need to make it clear from the start of > a level playing field with no "favorites" and allow the > community to determine its own course and direction. > > On Sep 23, 2013, at 10:19 AM, Sanjiva Weerawarana > wrote: > > > Of course not Jim - I do realize you're involved with OpenShift and I > > didn't by any means suggest an exclusive binding to Apache Stratos > > (Incubating) :-). > > > > BTW I offered to mentor .. but its fine. I can see sensitivities here for > > some reason. > > > > Sanjiva. > > > > > > On Mon, Sep 23, 2013 at 6:11 PM, Jim Jagielski wrote: > > > >> Of course collaboration and cross-pollination is important and should > >> be encouraged. However, I didn't want the podling to think that > >> Stratos, at the expense of other PaaS offerings, was to be > >> a "priority". I'm sure you understand the importance of keeping > >> things clear with new podlings... sometimes misunderstanding > >> can happen in the most innocuous ways. > >> > >> On Sep 22, 2013, at 6:58 PM, Sanjiva Weerawarana > wrote: > >> > >>> On Sun, Sep 22, 2013 at 9:36 PM, Luciano Resende >>> wrote: > >>> > On Sun, Sep 22, 2013 at 8:59 AM, Jim Jagielski > wrote: > > > Certainly that is a decision to be made by the Usergrid community > > itself and not something to be "encouraged" by the ASF. > > > > > +1 > > >>> > >>> Nothing in my mail suggested otherwise. > >>> > >>> OTOH, as an ASF Member, it always pleases me when ASF projects > >> collaborate > >>> with each other. Certainly the ASF *should* encourage that. Jim isn't > >> that > >>> any longer the case? > >>> > >>> Sanjiva. > >>> -- > >>> Sanjiva Weerawarana, Ph.D. > >>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > >>> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880| > +1 > >>> 650 265 8311 > >>> blog: http://sanjiva.weerawarana.org/ > >>> > >>> Lean . Enterprise . Middleware > >> > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> > > > > > > -- > > Sanjiva Weerawarana, Ph.D. > > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > > email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880| +1 > > 650 265 8311 > > blog: http://sanjiva.weerawarana.org/ > > > > Lean . Enterprise . Middleware > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Yes, just as WSO2 has a financial interest in seeing Stratos successful, so we need to make it clear from the start of a level playing field with no "favorites" and allow the community to determine its own course and direction. On Sep 23, 2013, at 10:19 AM, Sanjiva Weerawarana wrote: > Of course not Jim - I do realize you're involved with OpenShift and I > didn't by any means suggest an exclusive binding to Apache Stratos > (Incubating) :-). > > BTW I offered to mentor .. but its fine. I can see sensitivities here for > some reason. > > Sanjiva. > > > On Mon, Sep 23, 2013 at 6:11 PM, Jim Jagielski wrote: > >> Of course collaboration and cross-pollination is important and should >> be encouraged. However, I didn't want the podling to think that >> Stratos, at the expense of other PaaS offerings, was to be >> a "priority". I'm sure you understand the importance of keeping >> things clear with new podlings... sometimes misunderstanding >> can happen in the most innocuous ways. >> >> On Sep 22, 2013, at 6:58 PM, Sanjiva Weerawarana wrote: >> >>> On Sun, Sep 22, 2013 at 9:36 PM, Luciano Resende >> wrote: >>> On Sun, Sep 22, 2013 at 8:59 AM, Jim Jagielski wrote: > Certainly that is a decision to be made by the Usergrid community > itself and not something to be "encouraged" by the ASF. > > +1 >>> >>> Nothing in my mail suggested otherwise. >>> >>> OTOH, as an ASF Member, it always pleases me when ASF projects >> collaborate >>> with each other. Certainly the ASF *should* encourage that. Jim isn't >> that >>> any longer the case? >>> >>> Sanjiva. >>> -- >>> Sanjiva Weerawarana, Ph.D. >>> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ >>> email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880| +1 >>> 650 265 8311 >>> blog: http://sanjiva.weerawarana.org/ >>> >>> Lean . Enterprise . Middleware >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Of course not Jim - I do realize you're involved with OpenShift and I didn't by any means suggest an exclusive binding to Apache Stratos (Incubating) :-). BTW I offered to mentor .. but its fine. I can see sensitivities here for some reason. Sanjiva. On Mon, Sep 23, 2013 at 6:11 PM, Jim Jagielski wrote: > Of course collaboration and cross-pollination is important and should > be encouraged. However, I didn't want the podling to think that > Stratos, at the expense of other PaaS offerings, was to be > a "priority". I'm sure you understand the importance of keeping > things clear with new podlings... sometimes misunderstanding > can happen in the most innocuous ways. > > On Sep 22, 2013, at 6:58 PM, Sanjiva Weerawarana wrote: > > > On Sun, Sep 22, 2013 at 9:36 PM, Luciano Resende >wrote: > > > >> On Sun, Sep 22, 2013 at 8:59 AM, Jim Jagielski wrote: > >> > >>> Certainly that is a decision to be made by the Usergrid community > >>> itself and not something to be "encouraged" by the ASF. > >>> > >>> > >> +1 > >> > > > > Nothing in my mail suggested otherwise. > > > > OTOH, as an ASF Member, it always pleases me when ASF projects > collaborate > > with each other. Certainly the ASF *should* encourage that. Jim isn't > that > > any longer the case? > > > > Sanjiva. > > -- > > Sanjiva Weerawarana, Ph.D. > > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > > email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880| +1 > > 650 265 8311 > > blog: http://sanjiva.weerawarana.org/ > > > > Lean . Enterprise . Middleware > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Of course collaboration and cross-pollination is important and should be encouraged. However, I didn't want the podling to think that Stratos, at the expense of other PaaS offerings, was to be a "priority". I'm sure you understand the importance of keeping things clear with new podlings... sometimes misunderstanding can happen in the most innocuous ways. On Sep 22, 2013, at 6:58 PM, Sanjiva Weerawarana wrote: > On Sun, Sep 22, 2013 at 9:36 PM, Luciano Resende wrote: > >> On Sun, Sep 22, 2013 at 8:59 AM, Jim Jagielski wrote: >> >>> Certainly that is a decision to be made by the Usergrid community >>> itself and not something to be "encouraged" by the ASF. >>> >>> >> +1 >> > > Nothing in my mail suggested otherwise. > > OTOH, as an ASF Member, it always pleases me when ASF projects collaborate > with each other. Certainly the ASF *should* encourage that. Jim isn't that > any longer the case? > > Sanjiva. > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi, I am working on something similar when this project caught my attention. I had a look at the usergrid projects (stack, portal, etc..) in GitHub and I am very much interested in contributing to this project where ever I can. Thanks, *Niranjan Karunanandham* Senior Software Engineer M: +94 777 749 661 On Mon, Sep 23, 2013 at 1:08 PM, Alex Karasulu wrote: > Hi Sanjiva, > > Please excuse my late response I've been travelling over the weekend. > More inline ... > > On Mon, Sep 23, 2013 at 1:58 AM, Sanjiva Weerawarana > wrote: > > On Sun, Sep 22, 2013 at 9:36 PM, Luciano Resende >wrote: > > > >> On Sun, Sep 22, 2013 at 8:59 AM, Jim Jagielski wrote: > >> > >> > Certainly that is a decision to be made by the Usergrid community > >> > itself and not something to be "encouraged" by the ASF. > >> > > >> > > >> +1 > >> > > > > Nothing in my mail suggested otherwise. > > Indeed. > > > OTOH, as an ASF Member, it always pleases me when ASF projects > collaborate > > with each other. Certainly the ASF *should* encourage that. Jim isn't > that > > any longer the case? > > We're definitely encouraging the community in this regard, and we see > a natural synergy as you do. I think with time, as these and other > possibilities present themselves, the community will certainly take > them into account. It's merely a matter of time and consideration. > Incubation will be a great opportunity to for these bonds to form > between projects. > > Best, > Alex > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi All, I am interested in contributing to the user-grid project. +1 for the incubator proposal. It would be great to have an open source BaaS stack under the apache umbrella. To further my understanding - I will be referring the user-grid project found at github. Thanks. On Mon, Sep 23, 2013 at 1:08 PM, Alex Karasulu wrote: > Hi Sanjiva, > > Please excuse my late response I've been travelling over the weekend. > More inline ... > > On Mon, Sep 23, 2013 at 1:58 AM, Sanjiva Weerawarana > wrote: > > On Sun, Sep 22, 2013 at 9:36 PM, Luciano Resende >wrote: > > > >> On Sun, Sep 22, 2013 at 8:59 AM, Jim Jagielski wrote: > >> > >> > Certainly that is a decision to be made by the Usergrid community > >> > itself and not something to be "encouraged" by the ASF. > >> > > >> > > >> +1 > >> > > > > Nothing in my mail suggested otherwise. > > Indeed. > > > OTOH, as an ASF Member, it always pleases me when ASF projects > collaborate > > with each other. Certainly the ASF *should* encourage that. Jim isn't > that > > any longer the case? > > We're definitely encouraging the community in this regard, and we see > a natural synergy as you do. I think with time, as these and other > possibilities present themselves, the community will certainly take > them into account. It's merely a matter of time and consideration. > Incubation will be a great opportunity to for these bonds to form > between projects. > > Best, > Alex > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- *Dulitha R. Wijewantha** Software Engineer* Tel: 94112793140 | Mobile: 94112793140 dulit...@gmail.com | http://dulithawijewantha.com
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi Sanjiva, Please excuse my late response I've been travelling over the weekend. More inline ... On Mon, Sep 23, 2013 at 1:58 AM, Sanjiva Weerawarana wrote: > On Sun, Sep 22, 2013 at 9:36 PM, Luciano Resende wrote: > >> On Sun, Sep 22, 2013 at 8:59 AM, Jim Jagielski wrote: >> >> > Certainly that is a decision to be made by the Usergrid community >> > itself and not something to be "encouraged" by the ASF. >> > >> > >> +1 >> > > Nothing in my mail suggested otherwise. Indeed. > OTOH, as an ASF Member, it always pleases me when ASF projects collaborate > with each other. Certainly the ASF *should* encourage that. Jim isn't that > any longer the case? We're definitely encouraging the community in this regard, and we see a natural synergy as you do. I think with time, as these and other possibilities present themselves, the community will certainly take them into account. It's merely a matter of time and consideration. Incubation will be a great opportunity to for these bonds to form between projects. Best, Alex - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
On Sun, Sep 22, 2013 at 9:36 PM, Luciano Resende wrote: > On Sun, Sep 22, 2013 at 8:59 AM, Jim Jagielski wrote: > > > Certainly that is a decision to be made by the Usergrid community > > itself and not something to be "encouraged" by the ASF. > > > > > +1 > Nothing in my mail suggested otherwise. OTOH, as an ASF Member, it always pleases me when ASF projects collaborate with each other. Certainly the ASF *should* encourage that. Jim isn't that any longer the case? Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
On Sun, Sep 22, 2013 at 8:59 AM, Jim Jagielski wrote: > Certainly that is a decision to be made by the Usergrid community > itself and not something to be "encouraged" by the ASF. > > +1 -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Certainly that is a decision to be made by the Usergrid community itself and not something to be "encouraged" by the ASF. On Sep 21, 2013, at 12:41 AM, Sanjiva Weerawarana wrote: > One other aspect- with my Stratos hat on I'd like to see these services > (optionally) running on the Stratos PaaS framework .. that way the services > inherit an elastic execution platform and more. So I see this as a win-win > relationship. > > Sanjiva. > > > On Fri, Sep 20, 2013 at 7:24 PM, Sanjiva Weerawarana wrote: > >> +1 - there's a lot of overlap / commonality of objective between BaaS and >> the set of services provided by Apache Stratos (incubating) to developers >> of apps. I'm very happy to see this come to ASF and will be happy to mentor >> if you guys need another one. >> >> Cheers, >> >> Sanjiva. >> >> >> On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: >> >>> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service >>> stack for web & mobile applications based on RESTful APIs, as an Apache >>> Incubator podling. >>> >>> Here is a link to the proposal: >>> https://wiki.apache.org/incubator/UsergridProposal >>> >>> It is also pasted below: >>> >>> = Usergrid Proposal = >>> >>> == Abstract == >>> >>> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile >>> applications, based on RESTful APIs. >>> >>> >>> == Proposal == >>> >>> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) >>> composed >>> of an integrated distributed NoSQL database, application layer and client >>> tier with SDKs for developers looking to rapidly build web and/or mobile >>> applications. It provides elementary services (user registration & >>> management, data storage, file storage, queues) and retrieval features >>> (full >>> text search, geolocation search, joins) to power common app features. >>> >>> It is a multi-tenant system designed for deployment to public cloud >>> environments (such as Amazon Web Services, Rackspace, etc.) or to run on >>> traditional server infrastructures so that anyone can run their own >>> private >>> BaaS deployment. >>> >>> For architects and back-end teams, it aims to provide a distributed, >>> easily >>> extendable, operationally predictable and highly scalable solution. For >>> front-end developers, it aims to simplify the development process by >>> enabling them to rapidly build and operate mobile and web applications >>> without requiring backend expertise. >>> >>> >>> == Background == >>> >>> Developing web or mobile applications obviously necessitates writing and >>> maintaining more than just front-end code. Even simple applications can >>> implicitly rely on server code being run to store users, perform database >>> queries, serve images and video files, etc. Developing and maintaining >>> such >>> backend services requires skills not always available or expected of app >>> development teams. Beyond that, the proliferation of apps inside of >>> companies leads to the creation of many different, ad-hoc, unequally >>> maintained backend solutions created by employees and contractors alike >>> and >>> hosted on a wide variety of environments. This is causing poor resource >>> usage, operational issues, as well as security, privacy & compliance >>> concerns. >>> >>> In response to this problem, companies have long tried to standardize >>> their >>> server-side stack or unify them behind an ESB or API strategy. >>> Backends-as-a-Service follow a similar approach but their unique >>> characteristic is strongly tying 1) a persistence tier (typically a >>> database), 2) a server-side application tier delivering a set of common >>> services and 3) a set of client-side application interface mechanisms. For >>> example, a BaaS could package 1) MongoDB with 2) a node.js application >>> that >>> offers access through 3) WebSockets. In the case of Usergrid, the trifecta >>> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. >>> >>> The Backend-as-a-Service approach has steadily gained popularity in the >>> last >>> few years with cloud providers such Parse.com, Stackmob.com and >>> Kinvey.com, >>> each operating tens of thousands of apps for tens of thousands of >>> developers. The trend has already reached large organizations as well, >>> with >>> global companies such as Korea Telecom internally building a privately-run >>> BaaS platform. But so far, there have been limited options for developers >>> that want a non-proprietary, open option for hosting and providing these >>> services themselves, or for enterprise and government users who want to >>> provide these capabilities from their own data centers, especially on a >>> very >>> large scale. >>> >>> >>> == Rationale == >>> >>> The issue this proposal deals with is implicit in the name. >>> Backend-as-a-Service platforms are usually offered solely as proprietary >>> cloud services. They are typically closed sourced, hosted on public >>> clouds, >>> and require subscripti
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
One other aspect- with my Stratos hat on I'd like to see these services (optionally) running on the Stratos PaaS framework .. that way the services inherit an elastic execution platform and more. So I see this as a win-win relationship. Sanjiva. On Fri, Sep 20, 2013 at 7:24 PM, Sanjiva Weerawarana wrote: > +1 - there's a lot of overlap / commonality of objective between BaaS and > the set of services provided by Apache Stratos (incubating) to developers > of apps. I'm very happy to see this come to ASF and will be happy to mentor > if you guys need another one. > > Cheers, > > Sanjiva. > > > On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: > >> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service >> stack for web & mobile applications based on RESTful APIs, as an Apache >> Incubator podling. >> >> Here is a link to the proposal: >>https://wiki.apache.org/incubator/UsergridProposal >> >> It is also pasted below: >> >> = Usergrid Proposal = >> >> == Abstract == >> >> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile >> applications, based on RESTful APIs. >> >> >> == Proposal == >> >> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) >> composed >> of an integrated distributed NoSQL database, application layer and client >> tier with SDKs for developers looking to rapidly build web and/or mobile >> applications. It provides elementary services (user registration & >> management, data storage, file storage, queues) and retrieval features >> (full >> text search, geolocation search, joins) to power common app features. >> >> It is a multi-tenant system designed for deployment to public cloud >> environments (such as Amazon Web Services, Rackspace, etc.) or to run on >> traditional server infrastructures so that anyone can run their own >> private >> BaaS deployment. >> >> For architects and back-end teams, it aims to provide a distributed, >> easily >> extendable, operationally predictable and highly scalable solution. For >> front-end developers, it aims to simplify the development process by >> enabling them to rapidly build and operate mobile and web applications >> without requiring backend expertise. >> >> >> == Background == >> >> Developing web or mobile applications obviously necessitates writing and >> maintaining more than just front-end code. Even simple applications can >> implicitly rely on server code being run to store users, perform database >> queries, serve images and video files, etc. Developing and maintaining >> such >> backend services requires skills not always available or expected of app >> development teams. Beyond that, the proliferation of apps inside of >> companies leads to the creation of many different, ad-hoc, unequally >> maintained backend solutions created by employees and contractors alike >> and >> hosted on a wide variety of environments. This is causing poor resource >> usage, operational issues, as well as security, privacy & compliance >> concerns. >> >> In response to this problem, companies have long tried to standardize >> their >> server-side stack or unify them behind an ESB or API strategy. >> Backends-as-a-Service follow a similar approach but their unique >> characteristic is strongly tying 1) a persistence tier (typically a >> database), 2) a server-side application tier delivering a set of common >> services and 3) a set of client-side application interface mechanisms. For >> example, a BaaS could package 1) MongoDB with 2) a node.js application >> that >> offers access through 3) WebSockets. In the case of Usergrid, the trifecta >> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. >> >> The Backend-as-a-Service approach has steadily gained popularity in the >> last >> few years with cloud providers such Parse.com, Stackmob.com and >> Kinvey.com, >> each operating tens of thousands of apps for tens of thousands of >> developers. The trend has already reached large organizations as well, >> with >> global companies such as Korea Telecom internally building a privately-run >> BaaS platform. But so far, there have been limited options for developers >> that want a non-proprietary, open option for hosting and providing these >> services themselves, or for enterprise and government users who want to >> provide these capabilities from their own data centers, especially on a >> very >> large scale. >> >> >> == Rationale == >> >> The issue this proposal deals with is implicit in the name. >> Backend-as-a-Service platforms are usually offered solely as proprietary >> cloud services. They are typically closed sourced, hosted on public >> clouds, >> and require subscription payment. Usergrid opens the playing field, by >> making a fully-featured BaaS platform freely available to all. This >> includes >> developers that previously could not afford them, such as mobile >> enthusiasts, small boutiques, and cost-sensitive startups. This also >> includes large companies that benefit from a reference
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
+1 - there's a lot of overlap / commonality of objective between BaaS and the set of services provided by Apache Stratos (incubating) to developers of apps. I'm very happy to see this come to ASF and will be happy to mentor if you guys need another one. Cheers, Sanjiva. On Mon, Sep 16, 2013 at 7:09 PM, Jim Jagielski wrote: > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > stack for web & mobile applications based on RESTful APIs, as an Apache > Incubator podling. > > Here is a link to the proposal: >https://wiki.apache.org/incubator/UsergridProposal > > It is also pasted below: > > = Usergrid Proposal = > > == Abstract == > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > applications, based on RESTful APIs. > > > == Proposal == > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) > composed > of an integrated distributed NoSQL database, application layer and client > tier with SDKs for developers looking to rapidly build web and/or mobile > applications. It provides elementary services (user registration & > management, data storage, file storage, queues) and retrieval features > (full > text search, geolocation search, joins) to power common app features. > > It is a multi-tenant system designed for deployment to public cloud > environments (such as Amazon Web Services, Rackspace, etc.) or to run on > traditional server infrastructures so that anyone can run their own private > BaaS deployment. > > For architects and back-end teams, it aims to provide a distributed, easily > extendable, operationally predictable and highly scalable solution. For > front-end developers, it aims to simplify the development process by > enabling them to rapidly build and operate mobile and web applications > without requiring backend expertise. > > > == Background == > > Developing web or mobile applications obviously necessitates writing and > maintaining more than just front-end code. Even simple applications can > implicitly rely on server code being run to store users, perform database > queries, serve images and video files, etc. Developing and maintaining such > backend services requires skills not always available or expected of app > development teams. Beyond that, the proliferation of apps inside of > companies leads to the creation of many different, ad-hoc, unequally > maintained backend solutions created by employees and contractors alike and > hosted on a wide variety of environments. This is causing poor resource > usage, operational issues, as well as security, privacy & compliance > concerns. > > In response to this problem, companies have long tried to standardize their > server-side stack or unify them behind an ESB or API strategy. > Backends-as-a-Service follow a similar approach but their unique > characteristic is strongly tying 1) a persistence tier (typically a > database), 2) a server-side application tier delivering a set of common > services and 3) a set of client-side application interface mechanisms. For > example, a BaaS could package 1) MongoDB with 2) a node.js application that > offers access through 3) WebSockets. In the case of Usergrid, the trifecta > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > The Backend-as-a-Service approach has steadily gained popularity in the > last > few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, > each operating tens of thousands of apps for tens of thousands of > developers. The trend has already reached large organizations as well, with > global companies such as Korea Telecom internally building a privately-run > BaaS platform. But so far, there have been limited options for developers > that want a non-proprietary, open option for hosting and providing these > services themselves, or for enterprise and government users who want to > provide these capabilities from their own data centers, especially on a > very > large scale. > > > == Rationale == > > The issue this proposal deals with is implicit in the name. > Backend-as-a-Service platforms are usually offered solely as proprietary > cloud services. They are typically closed sourced, hosted on public clouds, > and require subscription payment. Usergrid opens the playing field, by > making a fully-featured BaaS platform freely available to all. This > includes > developers that previously could not afford them, such as mobile > enthusiasts, small boutiques, and cost-sensitive startups. This also > includes large companies that benefit from a reference implementation they > can deploy in trust, or extend to their needs without losing time writing > less-vetted, less-performant boilerplate functionality. > > Usergrid has been open source since 2011 and has grown as an independent > project, garnering 11 primary committers, 35 total contributors, 260+ > participants on its mailing list, with 3,700+ commits, 200+ external > contributions, 350+ stars and 100+ forks on Github, not to mention s
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Start of next week I plan on starting a formal VOTE... On Sep 17, 2013, at 9:58 AM, Alex Karasulu wrote: > On Tue, Sep 17, 2013 at 1:57 PM, Lieven Govaerts > wrote: > > SNIP ... > >> As I'm setting up a similar infrastructure for a mobile application >> now, this project interests me a lot. I have made some different >> design choices so it'll be interesting to compare the benefits of my >> approach against choices made by the usergrid team. > > We welcome your opinions, and your involvement. This is exactly what > we've been looking forward to. > >> I'll dig into the code more deeply and join (with contributions) were I can. > > Awesome! > >> Definitely a good addition to the apache incubator! > > Thanks, > -- Alex > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
On Tue, Sep 17, 2013 at 1:57 PM, Lieven Govaerts wrote: SNIP ... > As I'm setting up a similar infrastructure for a mobile application > now, this project interests me a lot. I have made some different > design choices so it'll be interesting to compare the benefits of my > approach against choices made by the usergrid team. We welcome your opinions, and your involvement. This is exactly what we've been looking forward to. > I'll dig into the code more deeply and join (with contributions) were I can. Awesome! > Definitely a good addition to the apache incubator! Thanks, -- Alex - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
On Mon, Sep 16, 2013 at 3:39 PM, Jim Jagielski wrote: > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > stack for web & mobile applications based on RESTful APIs, as an Apache > Incubator podling. > > Here is a link to the proposal: >https://wiki.apache.org/incubator/UsergridProposal > > It is also pasted below: > > = Usergrid Proposal = > > == Abstract == > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > applications, based on RESTful APIs. > > > == Proposal == > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed > of an integrated distributed NoSQL database, application layer and client > tier with SDKs for developers looking to rapidly build web and/or mobile > applications. It provides elementary services (user registration & > management, data storage, file storage, queues) and retrieval features (full > text search, geolocation search, joins) to power common app features. > > It is a multi-tenant system designed for deployment to public cloud > environments (such as Amazon Web Services, Rackspace, etc.) or to run on > traditional server infrastructures so that anyone can run their own private > BaaS deployment. > > For architects and back-end teams, it aims to provide a distributed, easily > extendable, operationally predictable and highly scalable solution. For > front-end developers, it aims to simplify the development process by > enabling them to rapidly build and operate mobile and web applications > without requiring backend expertise. > > > == Background == > > Developing web or mobile applications obviously necessitates writing and > maintaining more than just front-end code. Even simple applications can > implicitly rely on server code being run to store users, perform database > queries, serve images and video files, etc. Developing and maintaining such > backend services requires skills not always available or expected of app > development teams. Beyond that, the proliferation of apps inside of > companies leads to the creation of many different, ad-hoc, unequally > maintained backend solutions created by employees and contractors alike and > hosted on a wide variety of environments. This is causing poor resource > usage, operational issues, as well as security, privacy & compliance > concerns. > > In response to this problem, companies have long tried to standardize their > server-side stack or unify them behind an ESB or API strategy. > Backends-as-a-Service follow a similar approach but their unique > characteristic is strongly tying 1) a persistence tier (typically a > database), 2) a server-side application tier delivering a set of common > services and 3) a set of client-side application interface mechanisms. For > example, a BaaS could package 1) MongoDB with 2) a node.js application that > offers access through 3) WebSockets. In the case of Usergrid, the trifecta > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > The Backend-as-a-Service approach has steadily gained popularity in the last > few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, > each operating tens of thousands of apps for tens of thousands of > developers. The trend has already reached large organizations as well, with > global companies such as Korea Telecom internally building a privately-run > BaaS platform. But so far, there have been limited options for developers > that want a non-proprietary, open option for hosting and providing these > services themselves, or for enterprise and government users who want to > provide these capabilities from their own data centers, especially on a very > large scale. > > > == Rationale == > > The issue this proposal deals with is implicit in the name. > Backend-as-a-Service platforms are usually offered solely as proprietary > cloud services. They are typically closed sourced, hosted on public clouds, > and require subscription payment. Usergrid opens the playing field, by > making a fully-featured BaaS platform freely available to all. This includes > developers that previously could not afford them, such as mobile > enthusiasts, small boutiques, and cost-sensitive startups. This also > includes large companies that benefit from a reference implementation they > can deploy in trust, or extend to their needs without losing time writing > less-vetted, less-performant boilerplate functionality. > > Usergrid has been open source since 2011 and has grown as an independent > project, garnering 11 primary committers, 35 total contributors, 260+ > participants on its mailing list, with 3,700+ commits, 200+ external > contributions, 350+ stars and 100+ forks on Github, not to mention several > large scale production deployments at major global companies in the media, > retail, telecommunication and government spaces. > > The Apache Software Foundation's "Way", by putting community before the > code, will help Usergrid establish a vibrant, more diverse community to >
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
On Tue, Sep 17, 2013 at 3:02 AM, John D. Ament wrote: > Hi, > > So one nitpick. In your proposal, you link to https://github/usergrid > but should probably be https://github.com/usergrid Doh! Thanks, good catch John. I just updated the wiki. > I happened to get a demo of apigee a few months back at PhillyJUG. I > was very impressed with the platform. I too was amazed, especially by how rapidly one could build web and mobile applications on it. I can't imagine having to have to start from scratch without it. Hence why it's such a good addition to the incubator IMO. > On Mon, Sep 16, 2013 at 9:39 AM, Jim Jagielski wrote: >> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service >> stack for web & mobile applications based on RESTful APIs, as an Apache >> Incubator podling. >> >> Here is a link to the proposal: >>https://wiki.apache.org/incubator/UsergridProposal >> >> It is also pasted below: >> >> = Usergrid Proposal = >> >> == Abstract == >> >> Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile >> applications, based on RESTful APIs. >> >> >> == Proposal == >> >> Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed >> of an integrated distributed NoSQL database, application layer and client >> tier with SDKs for developers looking to rapidly build web and/or mobile >> applications. It provides elementary services (user registration & >> management, data storage, file storage, queues) and retrieval features (full >> text search, geolocation search, joins) to power common app features. >> >> It is a multi-tenant system designed for deployment to public cloud >> environments (such as Amazon Web Services, Rackspace, etc.) or to run on >> traditional server infrastructures so that anyone can run their own private >> BaaS deployment. >> >> For architects and back-end teams, it aims to provide a distributed, easily >> extendable, operationally predictable and highly scalable solution. For >> front-end developers, it aims to simplify the development process by >> enabling them to rapidly build and operate mobile and web applications >> without requiring backend expertise. >> >> >> == Background == >> >> Developing web or mobile applications obviously necessitates writing and >> maintaining more than just front-end code. Even simple applications can >> implicitly rely on server code being run to store users, perform database >> queries, serve images and video files, etc. Developing and maintaining such >> backend services requires skills not always available or expected of app >> development teams. Beyond that, the proliferation of apps inside of >> companies leads to the creation of many different, ad-hoc, unequally >> maintained backend solutions created by employees and contractors alike and >> hosted on a wide variety of environments. This is causing poor resource >> usage, operational issues, as well as security, privacy & compliance >> concerns. >> >> In response to this problem, companies have long tried to standardize their >> server-side stack or unify them behind an ESB or API strategy. >> Backends-as-a-Service follow a similar approach but their unique >> characteristic is strongly tying 1) a persistence tier (typically a >> database), 2) a server-side application tier delivering a set of common >> services and 3) a set of client-side application interface mechanisms. For >> example, a BaaS could package 1) MongoDB with 2) a node.js application that >> offers access through 3) WebSockets. In the case of Usergrid, the trifecta >> is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. >> >> The Backend-as-a-Service approach has steadily gained popularity in the last >> few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, >> each operating tens of thousands of apps for tens of thousands of >> developers. The trend has already reached large organizations as well, with >> global companies such as Korea Telecom internally building a privately-run >> BaaS platform. But so far, there have been limited options for developers >> that want a non-proprietary, open option for hosting and providing these >> services themselves, or for enterprise and government users who want to >> provide these capabilities from their own data centers, especially on a very >> large scale. >> >> >> == Rationale == >> >> The issue this proposal deals with is implicit in the name. >> Backend-as-a-Service platforms are usually offered solely as proprietary >> cloud services. They are typically closed sourced, hosted on public clouds, >> and require subscription payment. Usergrid opens the playing field, by >> making a fully-featured BaaS platform freely available to all. This includes >> developers that previously could not afford them, such as mobile >> enthusiasts, small boutiques, and cost-sensitive startups. This also >> includes large companies that benefit from a reference implementation they >> can deploy in trust, or extend to their nee
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
Hi, So one nitpick. In your proposal, you link to https://github/usergrid but should probably be https://github.com/usergrid I happened to get a demo of apigee a few months back at PhillyJUG. I was very impressed with the platform. On Mon, Sep 16, 2013 at 9:39 AM, Jim Jagielski wrote: > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > stack for web & mobile applications based on RESTful APIs, as an Apache > Incubator podling. > > Here is a link to the proposal: >https://wiki.apache.org/incubator/UsergridProposal > > It is also pasted below: > > = Usergrid Proposal = > > == Abstract == > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > applications, based on RESTful APIs. > > > == Proposal == > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed > of an integrated distributed NoSQL database, application layer and client > tier with SDKs for developers looking to rapidly build web and/or mobile > applications. It provides elementary services (user registration & > management, data storage, file storage, queues) and retrieval features (full > text search, geolocation search, joins) to power common app features. > > It is a multi-tenant system designed for deployment to public cloud > environments (such as Amazon Web Services, Rackspace, etc.) or to run on > traditional server infrastructures so that anyone can run their own private > BaaS deployment. > > For architects and back-end teams, it aims to provide a distributed, easily > extendable, operationally predictable and highly scalable solution. For > front-end developers, it aims to simplify the development process by > enabling them to rapidly build and operate mobile and web applications > without requiring backend expertise. > > > == Background == > > Developing web or mobile applications obviously necessitates writing and > maintaining more than just front-end code. Even simple applications can > implicitly rely on server code being run to store users, perform database > queries, serve images and video files, etc. Developing and maintaining such > backend services requires skills not always available or expected of app > development teams. Beyond that, the proliferation of apps inside of > companies leads to the creation of many different, ad-hoc, unequally > maintained backend solutions created by employees and contractors alike and > hosted on a wide variety of environments. This is causing poor resource > usage, operational issues, as well as security, privacy & compliance > concerns. > > In response to this problem, companies have long tried to standardize their > server-side stack or unify them behind an ESB or API strategy. > Backends-as-a-Service follow a similar approach but their unique > characteristic is strongly tying 1) a persistence tier (typically a > database), 2) a server-side application tier delivering a set of common > services and 3) a set of client-side application interface mechanisms. For > example, a BaaS could package 1) MongoDB with 2) a node.js application that > offers access through 3) WebSockets. In the case of Usergrid, the trifecta > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > The Backend-as-a-Service approach has steadily gained popularity in the last > few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, > each operating tens of thousands of apps for tens of thousands of > developers. The trend has already reached large organizations as well, with > global companies such as Korea Telecom internally building a privately-run > BaaS platform. But so far, there have been limited options for developers > that want a non-proprietary, open option for hosting and providing these > services themselves, or for enterprise and government users who want to > provide these capabilities from their own data centers, especially on a very > large scale. > > > == Rationale == > > The issue this proposal deals with is implicit in the name. > Backend-as-a-Service platforms are usually offered solely as proprietary > cloud services. They are typically closed sourced, hosted on public clouds, > and require subscription payment. Usergrid opens the playing field, by > making a fully-featured BaaS platform freely available to all. This includes > developers that previously could not afford them, such as mobile > enthusiasts, small boutiques, and cost-sensitive startups. This also > includes large companies that benefit from a reference implementation they > can deploy in trust, or extend to their needs without losing time writing > less-vetted, less-performant boilerplate functionality. > > Usergrid has been open source since 2011 and has grown as an independent > project, garnering 11 primary committers, 35 total contributors, 260+ > participants on its mailing list, with 3,700+ commits, 200+ external > contributions, 350+ stars and 100+ forks on Github, not to mention several > large scale production deployments at ma
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
On Mon, Sep 16, 2013 at 8:05 PM, Luciano Resende wrote: > On Mon, Sep 16, 2013 at 6:39 AM, Jim Jagielski wrote: > >> I would like to propose Usergrid, a multi-tenant Backend-as-a-Service >> stack for web & mobile applications based on RESTful APIs, as an Apache >> Incubator podling. SNIP ... > I'm glad to see a multi-tenant Backend-as-a-Service coming to Apache. > Please feel free to add me as a mentor, and I'm most likely contribute to > this project if time permits as this is an area I have interest. Luciano, that sounds great! I've just added you to the list of mentors. Looking forward to working with you on this one. There's a lot of potential for Wink and OSGi related work on this project so it might be your cup of tea. -- Best Regards, -- Alex - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
I like the idea. Btw, I'm currently trying github gists as a database backend. 16.09.2013 21:06 пользователь "Luciano Resende" написал: > On Mon, Sep 16, 2013 at 6:39 AM, Jim Jagielski wrote: > > > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > > stack for web & mobile applications based on RESTful APIs, as an Apache > > Incubator podling. > > > > Here is a link to the proposal: > >https://wiki.apache.org/incubator/UsergridProposal > > > > It is also pasted below: > > > > = Usergrid Proposal = > > > > == Abstract == > > > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > > applications, based on RESTful APIs. > > > > > > == Proposal == > > > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) > > composed > > of an integrated distributed NoSQL database, application layer and client > > tier with SDKs for developers looking to rapidly build web and/or mobile > > applications. It provides elementary services (user registration & > > management, data storage, file storage, queues) and retrieval features > > (full > > text search, geolocation search, joins) to power common app features. > > > > It is a multi-tenant system designed for deployment to public cloud > > environments (such as Amazon Web Services, Rackspace, etc.) or to run on > > traditional server infrastructures so that anyone can run their own > private > > BaaS deployment. > > > > For architects and back-end teams, it aims to provide a distributed, > easily > > extendable, operationally predictable and highly scalable solution. For > > front-end developers, it aims to simplify the development process by > > enabling them to rapidly build and operate mobile and web applications > > without requiring backend expertise. > > > > > > == Background == > > > > Developing web or mobile applications obviously necessitates writing and > > maintaining more than just front-end code. Even simple applications can > > implicitly rely on server code being run to store users, perform database > > queries, serve images and video files, etc. Developing and maintaining > such > > backend services requires skills not always available or expected of app > > development teams. Beyond that, the proliferation of apps inside of > > companies leads to the creation of many different, ad-hoc, unequally > > maintained backend solutions created by employees and contractors alike > and > > hosted on a wide variety of environments. This is causing poor resource > > usage, operational issues, as well as security, privacy & compliance > > concerns. > > > > In response to this problem, companies have long tried to standardize > their > > server-side stack or unify them behind an ESB or API strategy. > > Backends-as-a-Service follow a similar approach but their unique > > characteristic is strongly tying 1) a persistence tier (typically a > > database), 2) a server-side application tier delivering a set of common > > services and 3) a set of client-side application interface mechanisms. > For > > example, a BaaS could package 1) MongoDB with 2) a node.js application > that > > offers access through 3) WebSockets. In the case of Usergrid, the > trifecta > > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > > > The Backend-as-a-Service approach has steadily gained popularity in the > > last > > few years with cloud providers such Parse.com, Stackmob.com and > Kinvey.com, > > each operating tens of thousands of apps for tens of thousands of > > developers. The trend has already reached large organizations as well, > with > > global companies such as Korea Telecom internally building a > privately-run > > BaaS platform. But so far, there have been limited options for developers > > that want a non-proprietary, open option for hosting and providing these > > services themselves, or for enterprise and government users who want to > > provide these capabilities from their own data centers, especially on a > > very > > large scale. > > > > > > == Rationale == > > > > The issue this proposal deals with is implicit in the name. > > Backend-as-a-Service platforms are usually offered solely as proprietary > > cloud services. They are typically closed sourced, hosted on public > clouds, > > and require subscription payment. Usergrid opens the playing field, by > > making a fully-featured BaaS platform freely available to all. This > > includes > > developers that previously could not afford them, such as mobile > > enthusiasts, small boutiques, and cost-sensitive startups. This also > > includes large companies that benefit from a reference implementation > they > > can deploy in trust, or extend to their needs without losing time writing > > less-vetted, less-performant boilerplate functionality. > > > > Usergrid has been open source since 2011 and has grown as an independent > > project, garnering 11 primary committers, 35 total contributors, 260+ > > participants on its mailing list, with 3,700+ commits, 20
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
This is good news! Looking forward for this project into ASF incubation =) - Henry On Mon, Sep 16, 2013 at 6:39 AM, Jim Jagielski wrote: > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > stack for web & mobile applications based on RESTful APIs, as an Apache > Incubator podling. > > Here is a link to the proposal: >https://wiki.apache.org/incubator/UsergridProposal > > It is also pasted below: > > = Usergrid Proposal = > > == Abstract == > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > applications, based on RESTful APIs. > > > == Proposal == > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) composed > of an integrated distributed NoSQL database, application layer and client > tier with SDKs for developers looking to rapidly build web and/or mobile > applications. It provides elementary services (user registration & > management, data storage, file storage, queues) and retrieval features (full > text search, geolocation search, joins) to power common app features. > > It is a multi-tenant system designed for deployment to public cloud > environments (such as Amazon Web Services, Rackspace, etc.) or to run on > traditional server infrastructures so that anyone can run their own private > BaaS deployment. > > For architects and back-end teams, it aims to provide a distributed, easily > extendable, operationally predictable and highly scalable solution. For > front-end developers, it aims to simplify the development process by > enabling them to rapidly build and operate mobile and web applications > without requiring backend expertise. > > > == Background == > > Developing web or mobile applications obviously necessitates writing and > maintaining more than just front-end code. Even simple applications can > implicitly rely on server code being run to store users, perform database > queries, serve images and video files, etc. Developing and maintaining such > backend services requires skills not always available or expected of app > development teams. Beyond that, the proliferation of apps inside of > companies leads to the creation of many different, ad-hoc, unequally > maintained backend solutions created by employees and contractors alike and > hosted on a wide variety of environments. This is causing poor resource > usage, operational issues, as well as security, privacy & compliance > concerns. > > In response to this problem, companies have long tried to standardize their > server-side stack or unify them behind an ESB or API strategy. > Backends-as-a-Service follow a similar approach but their unique > characteristic is strongly tying 1) a persistence tier (typically a > database), 2) a server-side application tier delivering a set of common > services and 3) a set of client-side application interface mechanisms. For > example, a BaaS could package 1) MongoDB with 2) a node.js application that > offers access through 3) WebSockets. In the case of Usergrid, the trifecta > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > The Backend-as-a-Service approach has steadily gained popularity in the last > few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, > each operating tens of thousands of apps for tens of thousands of > developers. The trend has already reached large organizations as well, with > global companies such as Korea Telecom internally building a privately-run > BaaS platform. But so far, there have been limited options for developers > that want a non-proprietary, open option for hosting and providing these > services themselves, or for enterprise and government users who want to > provide these capabilities from their own data centers, especially on a very > large scale. > > > == Rationale == > > The issue this proposal deals with is implicit in the name. > Backend-as-a-Service platforms are usually offered solely as proprietary > cloud services. They are typically closed sourced, hosted on public clouds, > and require subscription payment. Usergrid opens the playing field, by > making a fully-featured BaaS platform freely available to all. This includes > developers that previously could not afford them, such as mobile > enthusiasts, small boutiques, and cost-sensitive startups. This also > includes large companies that benefit from a reference implementation they > can deploy in trust, or extend to their needs without losing time writing > less-vetted, less-performant boilerplate functionality. > > Usergrid has been open source since 2011 and has grown as an independent > project, garnering 11 primary committers, 35 total contributors, 260+ > participants on its mailing list, with 3,700+ commits, 200+ external > contributions, 350+ stars and 100+ forks on Github, not to mention several > large scale production deployments at major global companies in the media, > retail, telecommunication and government spaces. > > The Apache Software Foundation's "Way", by putting community
Re: [PROPOSAL] Usergrid BaaS Stack for Apache Incubator
On Mon, Sep 16, 2013 at 6:39 AM, Jim Jagielski wrote: > I would like to propose Usergrid, a multi-tenant Backend-as-a-Service > stack for web & mobile applications based on RESTful APIs, as an Apache > Incubator podling. > > Here is a link to the proposal: >https://wiki.apache.org/incubator/UsergridProposal > > It is also pasted below: > > = Usergrid Proposal = > > == Abstract == > > Usergrid is a multi-tenant Backend-as-a-Service stack for web & mobile > applications, based on RESTful APIs. > > > == Proposal == > > Usergrid is an open-source Backend-as-a-Service (“BaaS” or “mBaaS”) > composed > of an integrated distributed NoSQL database, application layer and client > tier with SDKs for developers looking to rapidly build web and/or mobile > applications. It provides elementary services (user registration & > management, data storage, file storage, queues) and retrieval features > (full > text search, geolocation search, joins) to power common app features. > > It is a multi-tenant system designed for deployment to public cloud > environments (such as Amazon Web Services, Rackspace, etc.) or to run on > traditional server infrastructures so that anyone can run their own private > BaaS deployment. > > For architects and back-end teams, it aims to provide a distributed, easily > extendable, operationally predictable and highly scalable solution. For > front-end developers, it aims to simplify the development process by > enabling them to rapidly build and operate mobile and web applications > without requiring backend expertise. > > > == Background == > > Developing web or mobile applications obviously necessitates writing and > maintaining more than just front-end code. Even simple applications can > implicitly rely on server code being run to store users, perform database > queries, serve images and video files, etc. Developing and maintaining such > backend services requires skills not always available or expected of app > development teams. Beyond that, the proliferation of apps inside of > companies leads to the creation of many different, ad-hoc, unequally > maintained backend solutions created by employees and contractors alike and > hosted on a wide variety of environments. This is causing poor resource > usage, operational issues, as well as security, privacy & compliance > concerns. > > In response to this problem, companies have long tried to standardize their > server-side stack or unify them behind an ESB or API strategy. > Backends-as-a-Service follow a similar approach but their unique > characteristic is strongly tying 1) a persistence tier (typically a > database), 2) a server-side application tier delivering a set of common > services and 3) a set of client-side application interface mechanisms. For > example, a BaaS could package 1) MongoDB with 2) a node.js application that > offers access through 3) WebSockets. In the case of Usergrid, the trifecta > is 1) Cassandra, 2) Java + Jersey and 3) a RESTful API. > > The Backend-as-a-Service approach has steadily gained popularity in the > last > few years with cloud providers such Parse.com, Stackmob.com and Kinvey.com, > each operating tens of thousands of apps for tens of thousands of > developers. The trend has already reached large organizations as well, with > global companies such as Korea Telecom internally building a privately-run > BaaS platform. But so far, there have been limited options for developers > that want a non-proprietary, open option for hosting and providing these > services themselves, or for enterprise and government users who want to > provide these capabilities from their own data centers, especially on a > very > large scale. > > > == Rationale == > > The issue this proposal deals with is implicit in the name. > Backend-as-a-Service platforms are usually offered solely as proprietary > cloud services. They are typically closed sourced, hosted on public clouds, > and require subscription payment. Usergrid opens the playing field, by > making a fully-featured BaaS platform freely available to all. This > includes > developers that previously could not afford them, such as mobile > enthusiasts, small boutiques, and cost-sensitive startups. This also > includes large companies that benefit from a reference implementation they > can deploy in trust, or extend to their needs without losing time writing > less-vetted, less-performant boilerplate functionality. > > Usergrid has been open source since 2011 and has grown as an independent > project, garnering 11 primary committers, 35 total contributors, 260+ > participants on its mailing list, with 3,700+ commits, 200+ external > contributions, 350+ stars and 100+ forks on Github, not to mention several > large scale production deployments at major global companies in the media, > retail, telecommunication and government spaces. > > The Apache Software Foundation's "Way", by putting community before the > code, will help Usergrid establish a vibrant, more diverse com
