IBM Z is the company's mainframe enterprise server solution product line.
N/A
SingleStore
Score 7.5 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.
These are not that effective when there is a lot of data, and the outage is more in other products as compared to the IBM Z. The processing Capabilities of the Z OS are much better than these products since, in my organization, the processing data is huge, and the IBM Z is best …
From an IBM Z Mainframe standpoint, there is no other platform that can even touch with the mainframe can do. This is why it is the best of breed and has been for over 60 years. There are a large number of third party products available for use on the mainframe. From job …
There is no competitor when you really run a banking infrastructure with a CICS Transaction System, Cobol- or PL1- Programs and DB2 Databases running under the operating system z/OS. Also when you migrate your programs to JAVA z/OS is still the platform where you want to stay …
My answer is yes. This made moving to the cloud much easier. The main benefits of this are latency and data extraction. The speed, security and reliability is the game changer and where it stacks up when compared to other IBM products. Additionally, increasing the workload is …
No one can deliver a Hardware Security Module with FIPS 140-2 Level 4 certification than IBM. And the value and ease of use in the IBM cloud with the Hyper Protect Crypto Service are just not compatible to the other vendors. And with Unified Key Orchestrator I can also manage …
IBM Z is the best storage solution as it provides the best in class data protection with the cryptographic hardware keys, no loss in data while migration, and a user-friendly interface that makes it easy for develops to understand and has less of a learning curve. This makes it …
IBM/IMS Tools compare favorably in use and performance against other vendors such as BMC. We support both within all our mainframe/zOS products so our users have the flexibility to choose the tools that work best for them and their users and budgets.
IBM Z is the winner when dealing with enormous transactions In terms of security as well IBM Z is a better option compared to other alternatives Excellent is dealing with large batch processing in multiple environments.
When it comes to deploying enterprise applications requiring serious resources that cannot be constrained, IBM Z and IBM Power 9 do a great job. However, they are in different classes of service. For high powered applications, we rarely utilize Intel architectures because the …
We currently have both X Linux and Windows platforms. The Windows applications support some of the smaller business units within Highmark very well and Z is probably not a solution for those environments. X Linux won out over Z Linux due to the processor requirements of the …
Specifically, Storage products attached to IBM Z Mainframe Technology. Hitachi Direct Access Storage Devices seems not to have as many hardware failures as some other IBM DASD. EMC DLM8100 Technology is used to support our FEP Disaster Recovery plan as we support DRE for the …
We believe in the right workload on the right platform. Z/OS is able to run more workloads than ever before and still with the lowest headcount required.
These items are not really compatible at all, so the comparison is not really valid. A mainframe may access the network by using an ISR router, but an ISR router would not replace anything that the mainframe does. I am new to the technology field, so I have not worked with many …
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 …
SingleStore provides performance for real-time data analytics application where as Snowflake is more for data engineers and not fast enough for real-time data analytics apps.
As I said before, we felt that running queries on BigQuery for every query is really slow, especially from an user point of view. After seeing the drastically improved latency of SingleStore we decided to use to solve this issue. We currently use it to run low volume queries …
We found its Data processing marvelous, and its benefit to accomplish chores in time gives us high authenticity and availability to the data deposit with accelerated admittance. One thing I will say that try to make it more user-friendly as it is difficult to learn. We liked it overall; Working is very good.
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.
IBM needs to add more focus on simplifying mainframe usage and management.
Most modern programmers interface with the Z using an IDE. However, performing many tasks, such as cataloging a data set or checking on a job status, can require switching to the ISPF interface. Users want to interface with a GUI, not a function-key, menu and character-based interface like ISPF. Anything that can simplify and modernize interfacing with the mainframe should be a high priority for IBM.
The IBM Z platform is one of the most instrumented computing platforms in the world, so there are a lot of metrics that could be automatically analyzed and used to improve the performance and management of the mainframe environment.
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.
The IBM Z mainframe capabilities are unmatched for cloud readiness and optimization the learning capabilities are matched perfectly with Watson and the expandability of the cloud makes it a perfect choice.
[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.
Performance is a major part when you configure your system. IBM has many tools to study your system and suggest the appropriate configuration. With the right contract, you can add processing power dynamically and remove it when no longer needed
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.
Support is usually superb, only occasionally dropping to very good. We participate in some of the CD (Continuous Delivery) aspects of z/OS, IMS, MQ, and DB2.
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.
My answer is yes. This made moving to the cloud much easier. The main benefits of this are latency and data extraction. The speed, security and reliability is the game changer and where it stacks up when compared to other IBM products. Additionally, increasing the workload is also very helpful. Use a single platform to avoid unnecessary activities and actions, help maintain safety, and even recover quickly. Activities that users are unable to continue and complete tasks help avoid mistakes when there are errors related to And because it's perfect for your users, it has less impact on your business. Always ready for backup. I didn't even care about the migrations that were performed.
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.
If you need more processing power, just add more CPU's or memory. The largest system can have close to 200 CPU's and 40 TB of memory. If that is not enough, you can add more physical computers, and connect them using a sysplex
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