I saw the thumbnail and recognized Andi Gutmans so just stopped by to say you are one of my childhood heroes. I started coding in PHP after trying and quitting many other languages. The ease of PHP is the reason I could stick to programming and eventually become a Software Engineer. It opened door to more complex languages and technologies.
I'm new to GCP and was waiting for more than 20 min for Firestore to delete 1M record of test collection, was so upset with the limitations of Firestore (can't get a count of query so frustrating), then I saw this new product and really excited to try it with my new product :) amazing ...
It’s a very informative concept. Is there way to package the AlloyDB auth proxy as a service so that it can automatically startup without us having to manually start it up in case the VM reboots ??
Thank you for this video, it answered my question on whether or not we should use partitioning in AlloyDB. It would be great if these sort of questions were answered in an FAQ.
Does it matter? If a company isn't updating their tech stack every few years, it just shows their incompetence and companies that don't innovate should be kicked out of the race.
@@edenassos I agree with you in some ways but not in others. Systems I have written to run against SQL Server 7 (?) still run against current versions yet Google have dropped db.model and ndb.model for app engine. When you have hundreds of 'tables' this makes Google unviable for long-term, large, projects.
We have a great experience with App Engine and NDB (practically since its creation) and in general with all kinds of on-prem and cloud products... and I don't know of a single one that sooner or later (of any brand) will not evolve its versions and deprecate in a certain way. With Google in this case we have not had big problems. I can't say the same for IBM or Teradata.
Got same feeling… Too many options makes maintaining this a nightmare even for big corps... Anyways product looks good and I will test it to compare performance against big query.
I saw the thumbnail and recognized Andi Gutmans so just stopped by to say you are one of my childhood heroes.
I started coding in PHP after trying and quitting many other languages. The ease of PHP is the reason I could stick to programming and eventually become a Software Engineer. It opened door to more complex languages and technologies.
have u tried python yet?
@@nikitabbrv5947 yes I've used Python. Currently use Spring and Java. Thanks for asking!
Thank you Eric. Much appreciated!
I'm new to GCP and was waiting for more than 20 min for Firestore to delete 1M record of test collection, was so upset with the limitations of Firestore (can't get a count of query so frustrating), then I saw this new product and really excited to try it with my new product :) amazing ...
Nice overview for AllowDB! Thank you, Andi!
Response time looks amazing!!
It’s a very informative concept. Is there way to package the AlloyDB auth proxy as a service so that it can automatically startup without us having to manually start it up in case the VM reboots ??
Similar to aurora postgresql?
way faster
Yes, generally.
Why didn't you disaggregate compute and storage on Cloud Spanner?
Thank you for this video, it answered my question on whether or not we should use partitioning in AlloyDB. It would be great if these sort of questions were answered in an FAQ.
is it ready for production???
Thanks! For opening up a great door for relational database world.
In which programming language it was written?
Cool , It could be a good choosing for OLTP/OLAP on Cloud Database Solutions.
กรุณาอยู่ในตำแหน่ง และระบบควอนตัมไม่ได้ตัดสินหรือมองถึงข้อพิดพลาดที่ง่ายขนาดนั้น เราเชื่อว่าไม่มีใครอยากให้มันเกิดข้อผิดพลาด เซฟเวอร์สามารถใช้ไฟฟ้าปกติในการใช้พลังงานกับคอมบนโต๊ะ หรือที่ชาร์ตไฟฟ้ากับสายไฟได้ ขอให้ผู้พัฒนาทดลองปรับใช่และอย่าพึ่งเข้าใจในการตัดสินใจ เพราะแนวทางและวิธีการไม่ได้ตัดสินว่าใครผิด มันคือแนวทางและวิธีการ คุณอาจเป็น CEO ด้านพลังงานในอนาคตก็ได้ ใครจะรู้
Thanks Google, it was all crystal clear
Don't think it was an apple-apple comparison, as PostgreSQL(DISK) vs AlloyDB(Memory). This is same as oracle buffer cache vs oracle in-memory.
Great news!
I think it contributes to google's already extensive bbdd offering and clearly targets "toxic" players.
Great, sir.
Revalutinized Postgre SQL or RDBMS is the best name for ALLOY DB 😀
Awesome, yet another database offering from Google. Any idea how long before they drop support for this one and move on?
Does it matter? If a company isn't updating their tech stack every few years, it just shows their incompetence and companies that don't innovate should be kicked out of the race.
@@edenassos I agree with you in some ways but not in others. Systems I have written to run against SQL Server 7 (?) still run against current versions yet Google have dropped db.model and ndb.model for app engine. When you have hundreds of 'tables' this makes Google unviable for long-term, large, projects.
We have a great experience with App Engine and NDB (practically since its creation) and in general with all kinds of on-prem and cloud products... and I don't know of a single one that sooner or later (of any brand) will not evolve its versions and deprecate in a certain way. With Google in this case we have not had big problems. I can't say the same for IBM or Teradata.
Got same feeling… Too many options makes maintaining this a nightmare even for big corps... Anyways product looks good and I will test it to compare performance against big query.
Super sir from madurai CEO relative sundar pichai anna