Microsoft Access vs. Percona Kubernetes Operators

Having worked at startups, I can say Microsoft Access is most suited for their needs. Some of the reasons for that can be the ease and ability to create tables, design an entity-relationship diagram, define the relationship between different tables, feeding data into the tables, and retrieving data. All of this can be curated very easily into a process for small to medium-size enterprises. But a serious limitation can be observed where Access does not provide better features for large-scale companies. Another limitation is for companies where Mac is used as work computers.

Incentivized

Production ready, robust DB solution built for Kubernetes envs, we was able, for the first time, to ship production db workloads inside k8s. Be sure to check differences with "traditional" MySQL and other clustering solutions. Also be sure to match it with proper k8s storage solutions.

• One good aspect of Microsoft Access is how the software can be customized for different applications. This is very useful because we are able to use this software for multiple applications, which makes it cost-friendly.
• Another strong point of Microsoft Access is the skill required to customize, the amount of programming required is less than most other database programs. This is good for a beginner looking to get into database management.
• Microsoft Access is one of the more cost-friendly database applications, and most of the time it comes with Microsoft Office. Other database programs can be expensive and not as easy to use.

Incentivized

• Easy and fast deployment.
• A reliable, fully automated, high-available db lifecycle management solution.
• Exaustive documentation.
• Production ready.

• Generally high learning curve for new users. Especially if they are not comfortable with technology.
• Desktop only program; not available in web-format like other O365 products
• Fewer experienced users, means it's a lot of self-teaching and troubleshooting when you run into an issue

Incentivized

• Some differences compared to "traditional" MySQL solution.
• Had some hard times trying to use it combined with pre-existing techs like WordPress, Magento, etc.
• The specific k8s environment features can have an impact on it, like the storage solutions offered by the cloud vendor.

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.

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.

Incentivized

Easy and fast deployment. A reliable, fully automated, high-available db lifecycle management solution. It requires a bit of learning time for people new to operators ecosystem.

I don't think the program has ever failed me. It is one of those programs where there is always a solution if you know where to look.

Incentivized

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.

Incentivized

Well documented, there was no need to contact support.

there is no key idea, since it is easy to implement Microsoft Access

Excel is a fantastic - robust application that can do so much so easily. Its easy to train and understand. However - excel does not provide a reporting function and that is typically where we will suggest a move to [Microsoft] Access. [Microsoft] Access requires a little more knowledge of data manipulation.

Incentivized

For a long time we struggled finding a viable solution to migrate our existing db workloads inside Kubernetes. Before "operators era" proper db workloads required manual management, of course that easily raised administrative overhead. Then the future started to be brighter with the introduction of operators and the "official" Oracle's MySQL Operator, then Presslab's one, finally Percona's operator. Compared to other operators, the last one allowed us to ship production db workloads inside k8s.

• Microsoft Access has had a mostly positive impact on our business objectives in that most of our work is funded by grants and those grants need reports with data about our projects. Microsoft Access makes getting and organizing that data very easy.
• Another positive is that since it is built on an Excel backbone, Excel files can be easily imported into Microsoft Access and also it is easy to export Microsoft Access reports, data sheets, etc. into Excel and some other programs as well. That might help more people who already use Excel learn how to work in a database.
• I can't really think of a negative impact other than not many people at my workplace have ever used or understand how to use a database. Most people tend to use Excel rather than a database, like Microsoft Access.

Incentivized

• It allowed us to use k8s on our entire infrastructure.
• Decreased administrative overhead around our db services.
• As it is an open source technology, it cut down our db pricings.