371–380 of 456 posts
Earlier quoted context omitted.
RDS is not single node - its multi-AZ replicated. And that's what we are paying 300$ instead of 99$ for. Imagine.. RDS is literally the ONLY place where you can buy a 10 GB data multi-AZ replicated, snapshotted and managed postgresql. Its pretty much a monopoly, now that Google seems to have officially closed the book on ever supporting postgresql.
>Google seems to have officially closed the book on ever supporting postgresql. Er, that's a bet I'd strongly suggest you didn't make.
If anything, hosted Postgres from Google Cloud will be priced in a way that makes Spanner some what more attractive, as a way to get conversions to Spanner in the long-run.
Earlier quoted context omitted.
Its probably a class size of 2, with Amazon. Beyond those two though, no one else is close.
I honestly don't think Amazon is even close to Google. How much more infrastructure do they have besides AWS? How much does Google have besides GCP?
Earlier quoted context omitted.
The absolute level of computation available isn't changing at the consumer level. What's happening for the next decade is the destruction of businesses hosting their own IT infrastructure and moving it to a couple of core centers. So, the computational "Gini index" is increasing, but no one is being thrown into computational poverty.
>What's happening for the next decade is the destruction of businesses hosting their own IT infrastructure and moving it to a couple of core centers. Yes, and this will be disadvantageous over the long run for people that want to run things themselves. Ultimately companies like AMD/Intel go where the big money is at. As things centralize further and further, there will only be 3 customers they care about in the serve…
Earlier quoted context omitted.
Not fair. Amazon: IaaS Google: PaaS Amazon is philosophy is being 'close to the metal' to allow Enterprise customer to migrate 'regular apps' into a 'regular environment' in the cloud. Most of Google's offerings are (at least were) novel, but proprietary ways of doing specific things. Amazon is not a laggard: they have provided a number of interesting and useful 'helper' things to facilitate IaaS - as well as a numbe…
Google is IaaS, their PaaS offering (App Engine) never gained much traction AFAIK. I also find the comparison fair, Google is a software engineering company, Amazon is a sales/marketing company.
Earlier quoted context omitted.
Helpful feedback, we do have a development plan for $99, but it's not really intended for production workloads. If you only have 10 GB of data we'd heavily recommend going with something like RDS or Heroku Postgres. At that amount of data single node Postgres works great.
RDS is not single node - its multi-AZ replicated. And that's what we are paying 300$ instead of 99$ for. Imagine.. RDS is literally the ONLY place where you can buy a 10 GB data multi-AZ replicated, snapshotted and managed postgresql. Its pretty much a monopoly, now that Google seems to have officially closed the book on ever supporting postgresql.
Uh, how? I wouldn't be surprised to see a Cloud SQL-like managed Postgres service from Google.
While there's obviously some overlap in the potential market for any relational datastore service, Spanner doesn't really overlap with a cloud Postgres service as much as Cloud SQL does.
Really a CP system but with the Availability being five 9s or better (less than one failure in 10^6) How: 1)Hardware - Gobs and Gobs of Hardware and SRE experience "Spanner is not running over the public Internet — in fact, every Spanner packet flows only over Google-controlled routers and links (excluding any edge links to remote clients). Furthermore, each data center typically has at least three independent fibers…
MTBF of 2PC-strapped-to-quorum is no different from MTBF of a 2PC-strapped-to-spof replicas. MTTR is bounded by reelection latency, rather than replica recovery, although you still may eat a write amplification cost for rereplication. write amplification is 3-5x of non-quorum-backed 2PC system, depending on replication ensemble size. google further multiplies write amplification with geo-redundancy, so bump that WA b…
Forgive my ignorance, but could someone explain in layman's terms in which situation this would be helpful? E.g. if I have 1TB of data would I use this? If I have 1GB with a growth rate of 25GB/daily would I use this?
The rule of thumb I have always been told is that you can push MySql to ~200 GB total and between 99.9% and 99.99% availability (between 1 and 9 hours of downtime per year). Your milage might vary, but these are probably the right orders of magnitude. There is also an iops limit but that's harder to put a clear limit on because it's workload dependent. If you need more storage, availability, or iops, the current reco…
Earlier quoted context omitted.
> It will be interesting if Amazon and Microsoft choose to compete with Google on this service. If we get to the point where you have databases, compute, storage, and connectivity services from those three at equal scale, well that would be a lot of choice for the developers! There are also plenty of choices evolving for developers who aren't looking for hosted solutions (which can sometimes be a showstopper for ente…
As someone who works (in part) in the MS SQL field, is it irrational to be a bit worried about the effects some of these platform advances might have one one's career? For example, being a MSSQL performance tuning expert requires years of experience and probably pays very well, but just the other day I read an anecdotal story where someone switched a large BI database to use columnar indexes, allowing them to replace…
There's a reason why regulated (including self-regulated) professions have continuing education requirements; progress happens and you become obsolete if you don't keep up with it.
Just because tech isn't regulated doesn't mean it's any more sensible to expect to remain valuable without keeping up with progress in the field.
That being said, MSSQL experts will likely have good-paying opportunities for quite a while, for the same reason thats then case for any well-established enterprise technology: lots of systems are going to be around using it long after it has become distressingly uncool to spend time learning.
Earlier quoted context omitted.
What's the SQL and wire compatibility level? MySQL? EDIT: Found quite a bit of my answers in your linked article: > Cloud Spanner uses a SQL dialect which matches the ANSI SQL:2011 standard with some extensions for Spanner-specific features. This is a SQL standard simpler than that used in non-distributed databases such as vanilla MySQL, but still supports the relational model (e.g. JOINs). It includes data-definitio…
Just to be clear, the JOINS were removed for the vertical sharding prior to looking at Cloud Spanner. Cloud Spanner fully supports complex JOINS of many times (e.g. INNER, OUTER) Details - https://cloud.google.com/spanner/docs/query-syntax#join-type... Disclaimer: I work on Cloud Spanner