Claris' FileMaker is presented as a Workplace Innovation Platform, and is used to create a custom app. Manual processes can be automated with Claris FileMaker Pro, and apps can be created to manage contacts, track inventory, organize projects, etc.
$21
per month per user
Presto
Score 10.0 out of 10
N/A
Presto is an open source SQL query engine designed to run queries on data stored in Hadoop or in traditional databases.
Teradata supported development of Presto followed the acquisition of Hadapt and Revelytix.
N/A
Pricing
Claris FileMaker
Presto
Editions & Modules
Platform Subscription
$21
per month per user
Individual desktop license
$594
one-time fee
No answers on this topic
Offerings
Pricing Offerings
Claris FileMaker
Presto
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Claris FileMaker
Presto
Features
Claris FileMaker
Presto
Low-Code Development
Comparison of Low-Code Development features of Product A and Product B
If your company is really small, I can understand the need for a product like this. However, I would go for MS Access... FileMaker Pro can not be integrated with other systems (like MS Access can at least be handled by C# for instance, and can be integrated with MS Excel or even SQL server). I'm really not sure in what scenario one would choose for FileMaker Pro. If your application or company grows bigger, you're going to have a problem to move to another environment. Also, the fact that only one person can work with the backend at any given time is a problem in a somewhat larger company.
Presto is for interactive simple queries, where Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like Vertica
The relational database management system makes the program highly customizable to fit the needs of any product. You can add a ton of information to each record and update your inventory on a regular basis with an Excel import or manually inside of the record. It has the capability to incorporate barcoding, which can manage your available inventory with ease.
The scripting language allows FileMaker to automatically calculate complex algorithms automatically or generate report outs with the click of a button. This allows for greater UI, especially with active users who are not familiar with writing code. Almost all of our internal data is linked to the FileMaker database
The server license allows many users to update the database in real time, which is handy if your inventory is constantly changing. We have users with Macs, PCs, iPhones and handheld tablets linked to our FileMaker database and they are updating the information constantly throughout the day.
If you invest some time into formatting and scripting the database, there is a high ease of use for users without knowledge of any programming or FileMaker itself.
Linking, embedding links and adding images is easy enough.
Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope).
Organizing & design is fairly simple with click & drag parameters.
Developer features need to be beefed up - namely adding the ability to search code for a phrase or keyword and the ability to do the same in the "relationship graph" in the database.
Add ability for users to edit the same table record at the same time by version control.
Allow Filemaker Server to use more than 1 core; currently multi-processing is not supported and it can be tricky to find just the right server to support the application you've built to the fullest capacity.
Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem.
Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override.
UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc.
It it not really up to me but my opinion does have some weight in the decision and the reason I would renew my use FileMaker Pro 8.5 is because I am finally getting used to it! Now that I have been working with the program, tasks have become quicker and projects are getting done faster. File Maker Pro 8.5 really is a versatile tool and I think we are just scratching the surface with it's abilities.
It's almost what it should be after so may years and with Apple's longevity and strength behind it. For people who earn their living based on efficiency I think there are too many developer obstacles that waste time and therefore money.
The forums are great with lots of helpful experts and the staff monitor them to provide help where needed. There have been a couple of unique technical issues I've had to deal with that I haven't been able to get resolved so I chose to score this a 9 instead of a 10.
Suggest you use an iterative R.A.D. or AGILE development approach. (i.e. rather than writing a gigantic spec for a system, then building it). FileMaker facilitates quick prototypes. Developing an example, then allowing users to "try it out" is a snap.
FileMaker is still the quickest way to go from zero to having a minimum viable working solution. Simple solutions can be built in as little as a afternoon of development. It is the only tool I am aware of which allows tech savy end users with domain knowledge to build bespoke apps for their businesses without undertaking professional software development training.
Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.
We are a more agile company because of FileMaker. A few of us who are tech-savvy enough to manage the database (but are not professional developers) can make needed adjustments to our database without having to employ an in-house developer or contract with a 3rd party. As our business processes evolve and change, it's easy to update the database to accommodate those changes.