Formerly from Magnitude Software and now from Insightsoftware, Angles is a solution to accelerate the distribution of actionable, operational reports and analytics.
N/A
SingleStore
Score 8.2 out of 10
N/A
SingleStore aims to enable organizations to scale from one to one million customers, handling SQL, JSON, full text and vector workloads in one unified platform.
I believe Noetix is much easier to use than either Crystal Reports or InfoMaker. When I worked with InfoMaker I used to say it took 5 minutes to get the data and 5 hours (and sometimes days) to make it look good. The same can be true for Crystal Reports. Noetix has a standard …
Effective solution around data even when it comes to real time info. Knowing you can access the data from any country is effective solution to extract the info needed.
I can only compare it with Exasol, which I have used a similar base, which manages the Hadoop scheme and is very similar to SingleStore. SingleStore has many advantages: being in the cloud, with just a couple of clicks I can increase the capacity, the configuration is super …
first of all SingleStoreis a cluster with high availability and easy to use. you need to design you tables / procedures such in a way that your SingleStore perform well and with handle heavy load
Reduces database sprawl, ETL costs, infrastructure expenses, etc. Supports horizontal scaling, unlike PostgreSQL & Aurora, and real-time analytics and fast transactions (HTAP), unlike Snowflake & ClickHouse.Handles high-volume workloads with thousands of concurrent queries. No …
SingleStore (memsql) out performs based on our analysis with sample data sets within org. We could see limitations with other products which SingleStore can overcall like scaling with data while performing with similar SLA. It also has the advantage of row store and column …
SingleStore outperforms Snowflake in real-time analytics and transactional workloads but lags in large-scale batch processing. Compared to MongoDB Atlas, SingleStore excels in complex SQL queries and joins, while MongoDB handles unstructured, document-based data better. Its …
Greenplum is good in handling very large amount of data. Concurrency in Greenplum was a major problem. Features available in SingleStore like Pipelines and in memory features are not available in Greenplum.
Gemfire was not scaling well like SingleStore. Support of both …
We previously used Bigquery for our application, and a single store gave us very good performance over Bigquery. But the comparison is not apples to apples, as Bigquery is more of a data warehousing solution.
SingleStore is just a bigger engine with more capability. Its ability to handle larger data sets with ease is its biggest advantage. These other database solutions are great for smaller scale projects that don't include large data sets but Singlestore greatly out performs in …
It has more APIs and other access methods. It has a multi-version concurrency control (MVCC) Distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in …
Its easier to query and faster. Ingestion is for the most part easier to understand and monitor and directly integrated with other storage solution products we use such as AWS S3. Singlestore overall is a better database to serve up an application large amounts of data very …
SingleStore is built for fast data ingestion and fast queries against large tables (> billions of rows). This is possible because of the column store engine that SingleStore uses. SingleStore also support a memory engine. Pipelines is also another big advantage. Being able to …
We knew early on that MySQL (Amazon Aurora) would not be suitable for this workload as it cannot query our time series data as fast as SingleStore. We also use MongoDB Atlas for another application but we could not achieve the raw speed we saw from SingleStore. Our technical …
We were initially using AWS Aurora which worked well at the time but as we grew it just felt like a lumbering beast - even with tier upgrades. We started looking at caching & search options to help make searches faster - we were already using redis. We looked at and even …
Timescale was the biggest alternative option we looked at for SingleStore, however the requirement to learn a new syntax (due to not being SQL compatible) was our biggest pain point.
Supporting a new language would require alterations to the Laravel framework, as this only …
SingleStore provides an abstraction layer in managing a sharded database solution reducing complexity for the FLOWD team. Coupled with the SingleStore Managed Service, we are partnering with SingleStore to provide FLOWD services to various utilities & councils.
SingleStore is eons faster than other database providers, and it absolutely crushes calculations & aggregations. While other providers may have a few quality of life enhancements over SingleStore, the speed benefits of SS far outweigh the cons. At the end of the day, speed …
If you desire to 'empower' employees to create or edit their own reports, Noetix is a great tool, though I am not particularly an 'empowerment' person. In my experience most people have enough work of their own, so to tell them they now have to create their own reports can cause problems. If someone is available, like I am, to create the reports based on user requirements, then the report can be shared with the user and they can make changes as needed. I have several users who use the same report over and over for slightly different applications, and they are happy to make the small alterations, but creating whole new reports can seem like a daunting task. I tell my users I don't want them to become frustrated. If they want to try on their own, fine, but don't waste more than half an hour, and if you start to get frustrated, stop and IM me. Ninety-nine times out of 100 I already have a report that will give them exactly what they need. I've done extensive training, and find it's quite easy for users to pick up
Well-Suited Scenarios: Real-Time Analytics: Financial trading platforms requiring instant insights. Operational Dashboards: Retail businesses monitoring live sales. IoT Data Processing: Smart device monitoring with high data ingestion. Fraud Detection: Banks detect suspicious transactions instantly. Less Appropriate Scenarios: Archival Storage: Cold data storage with infrequent access. Low-Volume Workloads: Small-scale apps with minimal data processing needs. Complex ETL Pipelines: Heavy data transformations without real-time demands.
Noetix makes reporting easy. Users can combine vtables (the Noetix term for its views), add or delete columns, add filters or parameters, sort, add totals to columns, all from an easy to use interface. It comes with a very large number of already written reports for all areas of Oracle reporting, but it also allows for custom vtables to be written, for Oracle or any database, to expand the number of available reports.
Noetix has an Excel add-in that is marvelous. It eliminates the need to run a report in the web application and export to Excel. The add-in can run very large reports, up to a million lines. Once a report is run in Excel, it can be saved, and then refreshed whenever needed. It's a really good tool.
Noetix is flexible. Joins can be added to existing Noetix vtables and also to custom vtables, to give users a large amount of data configurations to choose from. It also allows users to create calculated fields to any report.
Noetix is easy to administer. Users can be added or removed and grouped by the level of permission. Although, in our case, it validates against Oracle, the level of security is dictated by Noetix.
I like the fact that the output is standard, but I would like to be able to move columns around on the output screen, rather than having to go back to the editing screen, move the columns, then rerun the report.
Drag and drop of columns would be nice on the edit screen. Currently if you add a column to a report, it automatically goes to the bottom. Relocation of the column has to be done a line at a time. I would prefer to be able to grab the field I want from those available, and drop it into the report where I want it.
When adding a filter (or parameter), the available fields automatically come up in alphabetical order, but on the columns screen, they don't. They come up in the order they actually are in the query. That means, when creating custom vtables, to have the fields in alphabetical order, one must put them that way. It would be nice if Noetix put the fields in alphabetical order for the user.
It does not release a patch to have back porting; it just releases a new version and stops support; it's difficult to keep up to that pace.
Support engineers lack expertise, but they seem to be improving organically.
Lacks enterprise CDC capability: Change data capture (CDC) is a process that tracks and records changes made to data in a database and then delivers those changes to other systems in real time.
For enterprise-level backup & restore capability, we had to implement our model via Velero snapshot backup.
[Until it is] supported on AWS ECS containers, I will reserve a higher rating for SingleStore. Right now it works well on EC2 and serves our current purpose, [but] would look forward to seeing SingleStore respond to our urge of feature in a shorter time period with high quality and security.
Solutions are based around a business needs and even when implementing such solution, real time insights are also followed through showing the updates the business are implementing while informing the end users as what is new with technology.
When it comes to ingestion speed, SingleStore is probably at the top. Being able to create pipelines using SQL to ingest data from S3, Kafka, and other sources, is a great advantages. This means you can dynamically ingest data by customizing your SQL queries. SingleStore pipelines are pretty sophisticated, yet very simple. Few lines of codes and you are ingesting data, while still able to perform analytical queries on your billions of row tables.
The support deep dives into our most complexed queries and bizarre issues that sometimes only we get comparing to other clients. Our special workload (thousands of Kafka pipelines + high concurrency of queries). The response match to the priority of the request, P1 gets immediate return call. Missing features are treated, they become a client request and being added to the roadmap after internal consideration on all client needs and priority. Bugs are patched quite fast, depends on the impact and feasible temporary workarounds. There is no issue that we haven't got a proper answer, resolution or reasoning
We allowed 2-3 months for a thorough evaluation. We saw pretty quickly that we were likely to pick SingleStore, so we ported some of our stored procedures to SingleStore in order to take a deeper look. Two SingleStore people worked closely with us to ensure that we did not have any blocking problems. It all went remarkably smoothly.
I believe Noetix is much easier to use than either Crystal Reports or InfoMaker. When I worked with InfoMaker I used to say it took 5 minutes to get the data and 5 hours (and sometimes days) to make it look good. The same can be true for Crystal Reports. Noetix has a standard format, and most people export to Excel anyway. Who prints reports? So formatting is not all that important.
Reduces database sprawl, ETL costs, infrastructure expenses, etc. Supports horizontal scaling, unlike PostgreSQL & Aurora, and real-time analytics and fast transactions (HTAP), unlike Snowflake & ClickHouse.Handles high-volume workloads with thousands of concurrent queries. No need for ETL processes, unlike BigQuery & Snowflake. Works with JSON, relational, and key-value data, unlike ClickHouse.
Lower operational complexity - Installation and maintenance is pretty easy
Object scale when used can compete with Traditional Warehouse Systems like Teradata, Netezza, Greenplum
Adds lot of value to the business like couple of operations which never worked in traditional DBMS including HANA, Oracle In Memory, SQL Server In Memory just flew in SingleStore
