Vertex AI on Google Cloud is an MLOps solution, used to build, deploy, and scale machine learning (ML) models with fully managed ML tools for any use case.
$0
Starting at
Amazon Redshift
Score 8.9 out of 10
N/A
Amazon Redshift is a hosted data warehouse solution, from Amazon Web Services.
$0.24
per GB per month
Pricing
Vertex AI
Amazon Redshift
Editions & Modules
Imagen model for image generation
$0.0001
Starting at
Text, chat, and code generation
$0.0001
per 1,000 characters
Text data upload, training, deployment, prediction
$0.05
per hour
Video data training and prediction
$0.462
per node hour
Image data training, deployment, and prediction
$1.375
per node hour
Redshift Managed Storage
$0.24
per GB per month
Current Generation
$0.25 - $13.04
per hour
Previous Generation
$0.25 - $4.08
per hour
Redshift Spectrum
$5.00
per terabyte of data scanned
Offerings
Pricing Offerings
Vertex AI
Amazon Redshift
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
Pricing is based on the Vertex AI tools and services, storage, compute, and Google Cloud resources used.
—
More Pricing Information
Community Pulse
Vertex AI
Amazon Redshift
Features
Vertex AI
Amazon Redshift
AI Development
Comparison of AI Development features of Product A and Product B
we used Vertex AI on our automation process the model very useful and working as expected we have implemented in our monitoring phase this very helpful our analysis part. real time response is very effective and actively provide detailed overview about our products.this phase is well suited in our org. this model could not applicable for small level projects why because this model not needed for small level projects and without related resource of ML this model not useful. strictly on non cloud org not suitable means on pram not suitable
If the number of connections is expected to be low, but the amounts of data are large or projected to grow it is a good solutions especially if there is previous exposure to PostgreSQL. Speaking of Postgres, Redshift is based on several versions old releases of PostgreSQL so the developers would not be able to take advantage of some of the newer SQL language features. The queries need some fine-tuning still, indexing is not provided, but playing with sorting keys becomes necessary. Lastly, there is no notion of the Primary Key in Redshift so the business must be prepared to explain why duplication occurred (must be vigilant for)
Vertex AI comes with support for LOTs of LLMs out of the box
MLOps tools are available that help to standardize operational aspects
Document AI is an out of the box feature that works just perfectly for our use cases of automating lots to tedious data extraction tasks from images as well as papers
[Amazon] Redshift has Distribution Keys. If you correctly define them on your tables, it improves Query performance. For instance, we can define Mapping/Meta-data tables with Distribution-All Key, so that it gets replicated across all the nodes, for fast joins and fast query results.
[Amazon] Redshift has Sort Keys. If you correctly define them on your tables along with above Distribution Keys, it further improves your Query performance. It also has Composite Sort Keys and Interleaved Sort Keys, to support various use cases
[Amazon] Redshift is forked out of PostgreSQL DB, and then AWS added "MPP" (Massively Parallel Processing) and "Column Oriented" concepts to it, to make it a powerful data store.
[Amazon] Redshift has "Analyze" operation that could be performed on tables, which will update the stats of the table in leader node. This is sort of a ledger about which data is stored in which node and which partition with in a node. Up to date stats improves Query performance.
We've experienced some problems with hanging queries on Redshift Spectrum/external tables. We've had to roll back to and old version of Redshift while we wait for AWS to provide a patch.
Redshift's dialect is most similar to that of PostgreSQL 8. It lacks many modern features and data types.
Constraints are not enforced. We must rely on other means to verify the integrity of transformed tables.
Just very happy with the product, it fits our needs perfectly. Amazon pioneered the cloud and we have had a positive experience using RedShift. Really cool to be able to see your data housed and to be able to query and perform administrative tasks with ease.
Google is always top notch with their security and user interface performance. We use Google's entire suite in our business anyways, so using Vertex became second nature very quickly. I will say, though, that Google does need to come down on the price somewhat with their token allocation. Also, their UI is very robust, so it does require some time for training to really master it.
The support was great and helped us in a timely fashion. We did use a lot of online forums as well, but the official documentation was an ongoing one, and it did take more time for us to look through it. We would have probably chosen a competitor product had it not been for the great support
We tend to adapt and use the platform that suits the customers needs the best. We return to Vertex AI because it is the most in-depth option out there so we can configure it any which way they want. However, it is not quick to market and constantly changing or updating it's feature-set. This makes it suitable for bigger customers that have the capital and time to spend on a bigger project that is well researched and not quick to market like some of the other options that feel like a light-version of this.
Than Vertica: Redshift is cheaper and AWS integrated (which was a plus because the whole company was on AWS). Than BigQuery: Redshift has a standard SQL interface, though recently I heard good things about BigQuery and would try it out again. Than Hive: Hive is great if you are in the PB+ range, but latencies tend to be much slower than Redshift and it is not suited for ad-hoc applications.
Redshift is relatively cheaper tool but since the pricing is dynamic, there is always a risk of exceeding the cost. Since most of our team is using it as self serve and there is no continuous tracking by a dedicated team, it really needs time & effort on analyst's side to know how much it is going to cost.
Our company is moving to the AWS infrastructure, and in this context moving the warehouse environments to Redshift sounds logical regardless of the cost.
Development organizations have to operate in the Dev/Ops mode where they build and support their apps at the same time.
Hard to estimate the overall ROI of moving to Redshift from my position. However, running Redshift seems to be inexpensive compared to all the licensing and hardware costs we had on our RDBMS platform before Redshift.