[
https://issues.apache.org/jira/browse/USERGRID-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858708#comment-13858708
]
Sungju Jin edited comment on USERGRID-8 at 12/30/13 10:42 PM:
--------------------------------------------------------------
SGTM, I'd like to add features. And I welcome comments / questions.
Features / Goals
- ProxyService (3rd Party Server Integration Service)
- Collection/Entity Webhook
- Customizing Notification Mail
- Entity Ownership (Entity creator{Users, Groups} only has modify/delete
permission)
- Refactoring error codes ( for client developers )
- API Burst limit
- Support Providers (Google / Github)
- DBMS Persistence (Supporting legacy system)
was (Author: sungju):
SGTM, I'd like to add features. And I welcome comments / questions.
Features / Goals
- ProxyService (3rd Party Server Integration Service)
- Collection/Entity Hooks
- Customizing Notification Mail
- Entity Ownership (Entity creator{Users, Groups} only has modify/delete
permission)
- Refactoring error codes ( for client developers )
- API Burst limit
- Support Providers (Google / Github)
- DBMS Persistence (Supporting legacy system)
> [Epic] Usergrid 2.0 Roadmap
> ---------------------------
>
> Key: USERGRID-8
> URL: https://issues.apache.org/jira/browse/USERGRID-8
> Project: Usergrid
> Issue Type: New Feature
> Components: Stack
> Reporter: Rod Simpson
>
> This should be an epic, but no epic option is available.
> The following is a loose roadmap of what is in store for "2.0" of Usergrid.
> We welcome comments / questions.
> I. Overview
> - Refactoring and rebuilding the low-level persistence APIs
> II. Features / Goals
> - Optimistic Concurrency (No More Locking Nightmares)
> - Rock Solid Data Consistency
> - Establish (Cassandra Optimized) Persistence Usage Patterns
> - Ability to Support All Clients on Single Multi-tenant Mega Cluster
> - Cassandra Friendly Graph API
> - Asynchronous Staged Post-processing Pipeline
> - Optimizing Query Processing Engine
> - Circuit Breakers - Throttling & Load Management
> - Leverage Existing Netflix Infrastructure for Scalability (Elasticity)
> III. Phases
> i. Exploration
> - discussion
> - small scale tests
> - code analysis with tools
> ii. Develop new architecture
> Below is a link to an image of our proposed architecture plan.
> http://cl.ly/image/2j130R300f45
> iii.Build and Integrate
> 1. Collection Manager
> Build:
> Collection Manager (Entity) persistence
> Graph edges
> Graph indexing
> Integrate:
> Collection Services
> Graph Services (Services formerly known as Connections)
> Create migration for Graph and Collection
> Deploy:
> Performance testing
> Integration testing
> ** Map Persistence and Time Series Persistence may not be needed
> 2. Map Persistence
> Build:
> Map Persistence
> Integrate:
> Add shiro support for map persistence
> Create migration for security map persistence
> Deploy
> Performance testing
> Integration testing
> 3. Time Series Persistence
> Build:
> Time Series Persistence
> Integrate:
> Queue services
> Queue query services
> Deploy
> Performance testing
> Integration testing
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
