Re: Big Table ?? vs Oracle and Yugabyte

Hi Kyle,

I don't know about Yugabyte, but BigTable has a lot of limitations compared to what we can do with Oracle or Postgres. Big Table is a wide-column database, so it isn't very compatible with Oracle SQL. I'm pretty sure you can insert a massive amount of data into it (as you can in Cassandra, which I'm more experienced with), but for every different query predicate you'll need a new table, or a materialized view, or a secondary index, which all have a cost on resources. BigTable it is not ACID compliant either. I think you won't find any other database technology as mature as Oracle is, mainly in regard to online operations that you wish. You probably know that you need Oracle Enterprise Edition to leverage parallelism and online operations and an extra cost feature for partitioning. So it will be expensive, but if that's what your business needs and it pays out compared to the management overhead and downtime of other solutions, I'm 100% sure that is the way to go. I know SQL Server implemented a lot of online operations lately as well, maybe it is an option for you as well; it's been a while I don't work with it directly.

I hope I could add 2 cents to your thoughts.

Kind regards,

[image: LORE DATA]
Franky Weber Faust

Consultor de Banco de Dados | LORE DATA
Oracle ACE ♠️
Fone: *47 99125 2714*
Email: franky_at_loredata.com.br
loredata.com.br

On Wed, May 31, 2023 at 1:34 PM kyle Hailey <kylelf_at_gmail.com> wrote:

>
> Any have experiences with Big Table? good or bad (bads always
> more interesting)
>
> I hope this message finds you well. We are at an important crossroads in
> our project, and your expertise could provide valuable insights to help
> make a pivotal decision.
>
> We are currently running a high-load application on Google Cloud's
> Postgres, which services between 10,000 to 15,000 queries per second and
> adds approximately 10 million new records per day. Our database currently
> stores about 4TB of data. However, we are facing some scaling issues,
> particularly related to online operations such as detaching a partition,
> which tend to lock and impact our service.
>
> Our intention is to increase our operation scale 10-fold by the end of
> this year, which will undeniably require a more robust and scalable
> database solution. We have three potential options: transitioning to Oracle
> on Oracle Cloud Infrastructure (OCI), Yugabute or moving to Google's
> Bigtable.
>
> Personally, I lean towards Oracle, given its proven capability for
> handling heavy loads and providing fine-grained control over queries. Also,
> Oracle offers comprehensive monitoring and debugging tools, which would be
> beneficial for managing the anticipated growth of our workload.
>
> However, we understand the importance of making an informed decision and
> are therefore eager to hear your thoughts.
>
> Could you please provide your professional opinions on the potential pros
> and cons of these three options, primarily Big Table, particularly in terms
> of their capacity to handle our projected growth, ease of migration,
> reliability, and cost-effectiveness?
>
> Your insights will be instrumental in determining the best path forward
> for our project.
>
> Thank you in advance for your time and insights.
>

--
http://www.freelists.org/webpage/oracle-l