I think that Ignite can be placed in a list of NewSQL databases even though that's not our strongest use case. Ignite is unique as the whole:
- Storage (memory + disk - 3rd party or native) - Key/value for simple querying + SQL for advanced calls - Collocated processing (compute grid, ML) - complex logic execution w/o data movement over network Based on those capabilities the most prominent use cases are: - In-memory data grid - acceleration of 3rd party DBs (primarily RDBMSs) and further evolution with collocated processing - In-memory database with native persistence - greenfield applications that need scalable memory-centric storage, fast restarts. See a lot of use cases coming from the Hadoop world - Ignite is used for real-time analytics, partially offloading Hadoop. - Denis On Thu, Mar 28, 2019 at 7:09 AM Ilya Kasnacheev <ilya.kasnach...@gmail.com> wrote: > Hello! > > It's weird that you classify Ignite as NewSQL. > > Anyway, there's a lot of places where you can help. It depends on your > skillset. There are a lot of open issues in Ignite JIRA, and there are > whole untouched realms of scope. > > For example, if you are comfortable with .Net development, there is a huge > feature gap between Java and .Net which you can help close. Just take a > look at any .Net API, compare it to Java and implement missing pieces by > talking to Ignite inside JVM. > > There are gaps in C++ feature parity too, if you are not afraid of that. Or > just try a fix a test or two. > > Please provide your Apache JIRA handle so you can be added to contributors > list. > > Regards, > -- > Ilya Kasnacheev > > > ср, 27 мар. 2019 г. в 23:56, Payam Mohammadi <payam....@gmail.com>: > > > Hi dudes, > > > > I'm Payam Mohammadi, a CS student from Iran. > > I don't know many things about database internals and I'm still learning > > the basics. I used many databases in some enterprise projects but I have > no > > deep understanding of their internals. > > I'm following Andy Pavlo's works (http://www.cs.cmu.edu/~pavlo/) and > > trying > > to figure out what is happening inside the NewSQL databases. > > So, do you have any advice for me? And I'm a hard-working developer, is > > there anything I can do without having a deep understanding of database > > internals? > > >
