Microsoft Access is a database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and software-development tools.
$139.99
per PC
Redis Software
Score 9.1 out of 10
N/A
Redis is an open source in-memory data structure server and NoSQL database.
N/A
Pricing
Microsoft Access
Redis Software
Editions & Modules
Microsoft Access
$139.99
per PC
No answers on this topic
Offerings
Pricing Offerings
Microsoft Access
Redis Software
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Microsoft Access
Redis Software
Features
Microsoft Access
Redis Software
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Microsoft Access can be easily implemented with training. It doesn't require expert level skill for basic reporting functions - but can be scaled to a complex database with sophisticated users. Its appropriate to consider if excel needs to be used to create reports, or if there are data entry needs - with corresponding reports.
Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
Reliable. With a proper multi-node configuration, it can handle failover instantly.
Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
Fast. We process tens of thousands of RPS and it doesn't skip a beat.
Microsoft Access has not really changed at all for several years. It might be nice to see some upgrades and changes.
The help info is often not helpful. Need more tutorials for Microsoft Access to show how to do specific things.
Be careful naming objects such as tables, forms, etc. Names that are too long can get cut off in dialog boxes to choose a table, form, report, etc. So, I wish they would have resizable dialog boxes to allow you to see objects with long names.
I wish it could show me objects that are not in use in the database for current queries, tables, reports, forms, and macros. That way unused objects can be deleted without worrying about losing a report or query because you deleted the underlying object.
We had some difficulty scaling Redis without it becoming prohibitively expensive.
Redis has very simple search capabilities, which means its not suitable for all use cases.
Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.
I and the rest of my team will renew our Microsoft Access in the future because we use and maintain many different applications and databases created using Microsoft Access so we will need to maintain them in the future. Additionally, it is a standard at our place of work so it is at $0 cost to us to use. Another reason for renewing Microsoft Access is that we just don' t have the resources needed to extend into a network of users so we need to remain a single-desktop application at this time.
We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
Microsoft Access is easy to use. It is compatible with spreadsheets. It is a very good data management tool. There is scope to save a large amount of data in one place. For using this database, one does not need much training, can be shared among multiple users. This database has to sort and filtering features which seem to be very useful.
It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
While I have never contacted Microsoft directly for product support, for some reason there's a real prejudice against MS Access among most IT support professionals. They are usually discouraging when it comes to using MS Access. Most of this is due to their lack of understanding of MS Access and how it can improve one's productivity. If Microsoft invested more resources towards enhancing and promoting the use of MS Access then maybe things would be different.
The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
Crystal is easier for report writing, but isn't a database solution. Salesforce is lovely, but much more expensive than an old copy of Microsoft Office. For a small budget, [Microsoft] Access was really the only viable option. I only wish it was easier to write complex reports.
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.
