De viaje en Japón, el titular de Economía participa en un foro para conectar empresas en fase de crecimiento con inversores del país asiático
etiquetas: carlos cuerpo, idiomas, japones, ministro, economía
» noticia original (www.20minutos.es)
De viaje en Japón, el titular de Economía participa en un foro para conectar empresas en fase de crecimiento con inversores del país asiático
etiquetas: carlos cuerpo, idiomas, japones, ministro, economía
» noticia original (www.20minutos.es)
El intento de hacer desaparecer el nuevo grafiti ha dejado una silueta que muchos consideran un mensaje todavía más potente
etiquetas: chapuza, borrar, mural, banksy, londres, icono
» noticia original (www.lavozdegalicia.es)
Muchos señalaron que su acción va contra la economía manufacturera en un momento en el que se busca incentivar al sector imponiendo fuertes aranceles. "Imagínense apoyar los aranceles de Trump para recuperar empleos y luego celebrar la redada de ICE que destruyó la planta Hyundai de 4.300 millones de dólares, 40.000 empleos perdidos", "eso no es "Estados Unidos Primero", es un suicidio económico". Trump prometió reducir los aranceles a Corea del Sur a cambio de que este país invirtiera cientos de miles de millones de dólares en Estados Unidos.
etiquetas: estados unidos, ice, hyundai, maga, candidata, tori branum
» noticia original (www.alternet.org)
"No es por ponernos técnicos, ya saben que aquí hay una manía del dato, pero si cuando Mariló hacía la mañana aquí promediaba un 7,1% y Silvia Intxaurrondo está promediando un 20%. Debe de ser cosa de la mordaza". "Vamos a mostrarle a lo que es la paradoja de la mordaza. La paradoja de la censura. De quien dice 'no se puede hablar' y no se puede hablar en TVE pero habla y habla aquí en TVE. La de 'en otros tiempos vivíamos mejor'. Hoy no se puede decir nada, pero se dice, se dice todo y se dice aquí.
etiquetas: javier ruiz, mariló montero, audiencia, mordaza
» noticia original (www.huffingtonpost.es)
Necesita demostrarnos por activa y por pasiva que no ha sido contratado como bufón del rey en la TV del régimen. Video relacionado, también de UTBH: "MARILÓ MONTERO RESPONDE al ENCONTRONAZO con DAVID BRONCANO y la MANIPULACIÓN MEDIÁTICA "www.youtube.com/watch?v=s_D-DFxqmzk
etiquetas: tve, broncano, mariló montero, utbh, emilio mm, la revuelta
» noticia original (finofilipino.org)
España lo apoya. 'Lo hacemos por los niños' es la excusa elegida por los gobiernos de la UE. Podremos usar el cifrado de "extremo a extremo" siempre que nos sometamos a la comprobación previa de lo enviado.
etiquetas: privacidad, vigilancia, unión europea, chat control
» noticia original (www.genbeta.com)
Un 50% de adolescentes de ambos géneros justifica actitudes controladoras y un 30% de varones minimiza que se pegue o amenace a la novia en alguna ocasión, según un estudio de la oenegé Plan Internacional
etiquetas: acoso sexual, violencia de género, adolescencia, inteligencia artificial
» noticia original (www.elperiodico.com)

Written by: Boris Dali, Database Engineer @ Google (LinkedIn)
First off, the disclaimer: this blog series is neither a Google official documentation, nor it is an authoritative source. For the former, docs on AlloyDB Omni in particular, please see here and for the latter, please feel free to reach out to the AlloyDB product team. Google Cloud official blogs are posted here. Medium hosts Google Cloud Community here. This is neither. The opinions I express here in this blog post series are my own and may not represent or agree with Google’s official position on the subject.
So what is it then? Well, if you think of this blog series as the one engineer’s pseudo random ramblings on a particular topic (“running databases in containers on K8s” that is), you won’t be far off 🙂.
I do hope though that you may find these ramblings somewhat useful, perhaps even educational in some sense because it’s intended to show the thought process behind the work that I started as a 20% project and that at this point grew into its own legitimate line of business with a dedicated and very talented engineering team behind it. And while it may not be a Gmail (yet? 🙂), which BTW also started in a similar way from the very humble origins of one engineer’s idea and a small PoC, I still believe today, as I did when I started this project, that there are good reasons to invest into this technology and there’s a good market for it too.
But let’s not get ahead of ourselves. In this blog series I’ll try to be entertaining, but I don’t promise to be short, so a cup of coffee may be a good companion to reading my ramblings (and thank you for your patience!).
I also hope for this blog series to get more and more narrow and technical, but I start off and run the first few posts on “the big picture” stuff. You know, the big, bold, I’d almost call them foundational issues, “the why” questions. Personally, I find it important. In the past life, when I worked as a database consultant , I used to think of the customer engagements as falling into one of the two categories. First, obviously there were customers asking to solve specific problems like fixing a replication setup or addressing a database clustering problem or tuning a bunch of SQL statements or even a whole database. I looked at all those assignments as the narrow scope tactical problems. To be sure, these types of problems were very important to customers— and often time sensitive — and I obviously did my best to solve them to a customer’s satisfaction, but in the grand scheme of things, I personally looked at them as “tactical”. This is because they were usually self-contained where I didn’t really need to bother understanding the big picture stuff, just the set of technical artifacts sufficient for me to solve a problem at hand.
Then there were more open ended gigs, mostly design-type ones, typically longer ones too, where understanding of the context, the big picture, was essential (or at least I approached it that way) and so I treated these types of assignments as the much larger-scope problems, which I thought of as more like the strategic ones. I had to ask a lot more questions, connect a lot more dots, build this overall big picture in my head first before jumping into any design considerations and recommendations.
The first few posts here are going to be of this latter, strategic kind. If you are looking for a recipe for quick fix of a database hosted on K8s or a script to make your pesky SQL statement run faster on K8s or a nagging shell issue that you need to solve quickly, feel free to skip these few posts and wait until later when we are done sorting out the boring strategic questions and get them out of the way to arrive to the point where we can actually delve into solving specific technical problems (by means of running containerized databases on K8s). In the meantime, please consider the content produced by my esteemed colleague, Gleb Otochkin, who regularly publishes high quality articles here on Medium and elsewhere. But for now, the intent here is to present enough context to show how I reasoned about running a containerized database on K8s.
And yes, this series of blog posts is way overdue. By about six years overdue in fact. No kidding! Six years is an eternity in modern computer industry that seems to come up with new toys every month, but that’s when I first created a prototype of a database K8s Operator that we later launched and open sourced¹ and so I started drafting blogs about it to remember the motivation for doing it all. The good news is that the tech still stands, going strong, attracting new customers and keeping the existing customers happy, so I figured it may be a good time to bring the old blogs back to life. And perhaps write some new ones too as there are more than a few things I didn’t anticipate six years ago. Like AI 🙂.
Over the past six years I’ve also observed a bunch of really good quality technical articles for running containerized databases on K8s. For instance, I’m a big fan of Gabriele Bartolini’s work on CNPG and the open source community in general, but I don’t believe I came across the strategy guide to help me decide on why would I even entertain the idea of using K8 as a hosting platform for running databases to begin with? I’ve seen a few, like this one, but I’d still hesitate to call it definitive. Or maybe it’s clearly explained already somewhere and I just haven’t looked around hard enough to find out?
At any rate, let’s start from the beginning. Why bother running databases in containers? And even more so, why bother running database containers on K8s? Why introduce layers and layers of complexity when the good ol’ ways of using simple automation via a shell or Python or Perl scripts worked just fine for years for hosting databases on bare metal or VMs (perhaps with the help of config management tools like Puppet or Ansible if scale was a concern)? And isn’t there Terraform, Pulumi, Crossplane anyhow if you already got to a cloud and need an Infrastructure as Code (IaC) tool to provide the infra in a repeatable way? And even if there’s some fancy way to justify the investment into squeezing a database into a container for anything other than amusement and experiment, why spin that container on K8s? But more importantly, why on earth bother with all that stuff anyway if the world seems to be moving to Software as a Service (SaaS) or at least to the cloud providers’ Database as a Service (DBaaS) systems such as Google AlloyDB, Cloud SQL, Amazon RDS, Amazon Aurora, Azure PostgreSQL and such, which seem to be all the rage?
I’m glad you asked, because those were the questions on my mind too when I pondered about it six years ago. Let’s see if we can get to the bottom of it 🙂.
As the well-known Einstein quote goes: “everything should be made as simple as possible, but no simpler”. If so, wouldn’t throwing the layers of complexity at an already solved problem be considered as a classic case of over-engineering and overkill?
And yes, there are so many ways to visualize over-engineering and seemingly prove the point that additional complexity (and costs!) may not be warranted. My favorite is the story of the space pen and the urban legend that while NASA spent obscene amounts of public money on developing a pen that works at zero gravity, Russians just used pencils.
This is a cool story. It’s also a lie. Not just because private capital and not the government funding was spent on developing a space pen, but because NASA cared about safety and “because of the substantial dangers that broken pencil tips and graphite dust pose to electronics in zero gravity, etc”. So yes, maybe it wasn’t the most critical P0 task for the Apollo launch, but it was clearly more than just a clever engineering gimmick. It was the right investment. And yes, once Fisher developed the space pen, both NASA and Russians started purchasing it.
The point is that it’s easy to dismiss the new way of doing well known and familiar things — like running a database — particularly when it adds additional complexity, requires retooling, relearning, changing operational manuals and perhaps even a mindset and perhaps goes as far as proposing changes in company’s business flows. But it may make sense to at least review the benefits of this new proposed tech, understand the reasons behind using it before outright dismissing it.
So let’s try to unpack. I’ve been managing and helping manage databases on-prem for some 30 years and it clearly worked just fine with whatever toolset a customer was comfortable with. So why change? When I worked as a database consultant, especially on short term assignments, before leaving a customer, I’ve always tried to document not only how to operate what I created, but also explain why. To me this was an important part of every assignment and I always proposed customers to budget time for it, because circumstances change, project parameters get adjusted, people come and go, sometimes forgetting their initial directions, but I found that clearly stating the reasons, the parameters, the constraints for choosing this or that tech stack, a specific solution or a program or a protocol, is what overtime customers perhaps appreciate the most. It is what makes the chosen solutions endure, better withstand the test of time and incidentally, as a nice side effect, it also made customers often call me back and helped me find new assignments purely through word of mouth.
Just as I did on the consulting gigs, I take the same approach here as well — attempt to document, perhaps over communicate by breaking my thought process down before building it back, all the way up from the first principles (perhaps just as a favor to my future self for the next time when I’m asked why I had to over engineer the darn thing).
How?
Well, as Andy Jassy pointed out last year, 85% of IT spend still remains on-prem. And not only that, but some shops that made the jump to the cloud appear to regret it or at least question that decision and consider at least partial pull back to on-prem, either completely or towards some form of a hybrid computing. This article popped up in my feed recently to highlight this point or this one or this older one (and those are far from being the only stories of companies that pull back). All of this suggests that the on-prem may be a good starting point for reviewing a prospective database customer needs, first through the lens of what public clouds have to offer in terms of their DBaaS systems as well as self hosting options. If not fully satisfied, I’d consider alternatives, but as a savvy on-prem customer, my first step would be to analyze the cloud innovations from the data hosting perspective and define my own expectations. I’d like to see a clear advantage of hosting my data on a cloud, going beyond just the hype of swapping Capex for Opex (which may eventually backfire anyway).
All of us humans are different, but we also bear some similarities not just in being bipedal and how our bodies roughly consist of 60% water, but in how the technologically inclined of us approach these rather foundational questions and build our line of reasoning: we start with the first principles². So let’s take a step (or five) back and first start by reminding ourselves how does it make sense to throw my database to a cloud and give the keys to my proverbial castle to a cloud provider, introducing a critical dependency of my business on some servers and networks and all the infrastructure that I can’t even see and touch. And, yes, that infrastructure that is to run my critical apps and databases is also (often) shared with tons of other customers (perhaps bigger than me, with likely much stronger pull over the cloud provider for their interests), and can be taken offline at any moment as it’s solely owned by somebody else. But on the flip side, that cloud provider’s DBaaS automation can free me up from most of the mundane database management tasks, allows me to benefit from cloud elasticity providing compute and storage on-demand, relieving me from most support problems and upfront investments, so… isn’t it an acceptable trade-off?
So that’s the plan for the next few posts in this blog series. Before I can explain why I believe that running databases on K8s is a good investment, I’m taking a detour into the cloud evaluation methodology that I propose for determining the right place for hosting my database estate. How? By defining my cloud expectations and checking if it matches the real provider’s offerings.
And to make this somewhat more concrete, I’ll pretend to be a prospective customer with a successful on-prem business (say, retail, selling shirts and shoes) with my hosting co-lo lease expiring shortly. Should I continue and resign the lease for another 3 years or is there a better alternative out there for my database computing needs? I’m willing to explore my options and in particular the public cloud hosting DBaaS systems that seem to be everywhere, on the news and billboards.
I hope to see you there ! Link to part 2.
¹ The first K8s Operator was El Carro that we open sourced in May of 2021 (that is still very much in use by customers in production today) before adding AlloyDB Omni to our K8s Operator portfolio. I’m proud of this product, there were a bunch of innovations packed inside (like this one), including storage based snapshots for backup (in addition or instead of the database specific ones taken with RMAN in this case).
To be sure, storage snapshots are nothing new, of course, but figuring this out for K8s’ PVCs and making it a reliable mainstream option was a bit pioneering in 2020/2021 (especially for restoring to a different K8s cluster for DR purposes).
² Or, as Kevin Jernigan would say, ELI5 (“explain to me like I’m five”).
The Omni Database Engineering team at Google is the one that makes the magic presented in this blog series happen. I was the first, founding engineer, helped build the team, became a TL and later UberTL, so I believe I have a good perspective of why and how we approached the Operators and evolved them over time. Today, AlloyDB Omni K8s Operator is the production grade database management solution used by major banks, retailers and other customers and the eng team deserves all the credit.
I’d also like to thank Marc Fielding, Martin Nash, Aalok Muley, Hemanth Siddulugari, Sumaithri Mukkamalla, Gleb Otochkin, Justin Benton and Sridhar Ranganathan for reviewing these blog posts, correcting my broken English and my broken thoughts. All the remaining mistakes and inaccuracies are obviously still mine.
Databases on K8s — Really? (part 1) was originally published in Google Cloud - Community on Medium, where people are continuing the conversation by highlighting and responding to this story.
*insert vile and controversial direct quote from charlie*
Pearl clutching hypocrites:
How dare you speak ill of the dead… even though he constantly spit on the names of dead folks, how dare you show such disrespect.
me: it’s a direct quote from him… it’s his words…
PCH:
You’re celebrating his death! You’re a monster!
me: I quoted him… It’s his words!
………….
Acknowledging & discussing someone’s vile actions, words and behavior in their life, is not celebrating their death…
STOP BLATANTLY IGNORING THE HARM THIS MAN HAS CAUSED!
Here’s the truth: Kirk wasn’t about dialogue, he was about domination. He wasn’t protecting liberty, he was laying the rhetorical groundwork for fascism.
This guy wasn’t just “against gay marriage.” He opened his Bible, pointed to the verse about executing gay men, and called it “God’s perfect law.” He tweeted “Pride is a sin” like he was dunking on an entire community. He told a gay student that their life wasn’t valid. Then he went even further—demanding a nationwide ban on gender-affirming care and calling trans kids an abomination. That’s not policy debate, that’s state-sanctioned cruelty dressed up as a sermon.
And race? Same playbook. He called George Floyd a “scumbag,” smeared Martin Luther King Jr. as “awful,” and sneered at the Civil Rights Act as a “huge mistake.” That’s not contrarian courage, that’s spitting on the graves of people who bled to expand democracy. And the man didn’t just flirt with white nationalism—he blasted the Great Replacement theory on national radio, pointing to demographic charts and telling his audience the decline of white Christians was “intentional.” Do you hear the subtext? He wasn’t warning about immigration policy, he was laying out a war cry.
Immigrants, in his mind, weren’t people—they were invaders. He called for a total immigration shutdown, then promised mass round-ups. Not the usual “tighten security” talk—he said, “We will find you and your family, and we will return you. All 20, 25, 30 million.” That’s not a plan, that’s a threat. It’s the fantasy of a police state that tears apart homes in the middle of the night.
And let’s not forget his casual acceptance of violence. He said it outright: “Some gun deaths every single year? Worth it.” Worth it! As if dead kids in classrooms are a reasonable trade-off for his right to pose with an AR-15 on Instagram. He called for Trump to unleash the military on American streets under the Insurrection Act. He told dads they should’ve physically stopped trans athletes from competing. He framed blood in the streets as part of liberty’s price tag and told the audience to clap for it.
Now the obits will paint him as a victim of “political violence.” But the man himself glorified violence when it came from the right. He cheered Rittenhouse. He excused Jan. 6. He was fine with militarized crackdowns as long as they landed on protesters, not his base. He didn’t fear political violence—he marketed it. And here’s the uncomfortable truth: if someone makes it their life’s mission to be a hate-mongering fascist, they shouldn’t be shocked when political violence finds them. Actions, rhetoric, and consequences are not separate islands—they feed each other.
So no, he wasn’t a saint, he wasn’t some brave debater taken too soon. He was a professional hate-monger, a demagogue who wanted to roll this country back to the dark ages of church-run morality and white supremacy. And if the papers try to hand him a halo, it’s our job to rip it off and remind people who he really was.
- I don’t support Charlie Kirk.
- I don’t support what happened to Charlie Kirk.
Charlie Kirk was an openly racist person who built a career off of mocking and spreading harmful rhetoric and ideology that hurt many people, especially poc, trans people, and women.
My absence of empathy does NOT mean I am celebrating.
All the people publicly wailing the death of Charlie Kirk were silent when MN State Representative Melissa Hartman, was publicly shot and killed. They’ve remained silent EVERY day of this ongoing genocide of Palestinian people. The slaughtering and mutilation of tens of thousands of children.
This is Charlie Kirk’s legacy:
Who repeatedly stated that “there was more to the story” when it comes to slavery.
Who publicly tried to assisinate the character of MLK.
Who publicly stated numerous times that the civil rights act was “ a huge mistake.”
Who publicly made comments such as, “if I see a black pilot, I’m gonna think, ‘boy, is he qualified?”
Who rushed to blame black people for the air traffic controller crisis.
Who repeatedly attacked the extremely qualified and accomplished SCJ Kentaji Jackson Brown’s appointment, saying she’s a “DEI hire” who was only appointed because she’s a “Black Woman.”
Whose rhetoric historically hurt women, not only continously bringing in to question their rights, but also making claims that “men don’t want women in their 30s because they’re not in their prime.”
Who bragged about sending 80 buses to DC on January 6th “to help fight for Trump” when our capital was stormed in an attempt to overthrow the government.
Who staunchly denies the existance of an entire group of people- the Palestinian people- and simultaneously CELEBRATES their ongoing genocide (whose population is over 50% children. Meaning babies and children are the ones dying for all the pretend pro-lifers, reading this).
He founded an organization who spread dangerous and false claims and medical misinformation, saying the covid vaccine caused Jamie Fox to become blind and paralyzed. This same organization created watchlists to harass and intimidate academics, officials who support public health measures or the teaching of accurate history.
Who was a big proponent of leading the seven mountains mandate and called for full military occupation in American cities.
Whose response to the 2023 shooting at ‘The Covenant School’ where three 9 year old students (and three adults) were shot and killed in their school, was that these deaths were “unfortunately, the cost of liberty.”
I’d like to remind everyone that the first tenet of white supremacy is your belief that you have the right to comfort…
You being forced to face the evil that that man portrayed and enacted during his life, after his death, makes you uncomfortable… you want everyone to pretend that there’s this notion as if he’s some sort of saint or freedom fighter… while actively ignoring the harm he caused to children and their families and minorities and victims of gun violence…
I’m sorry, but not all of us are going to participate in your delusion to make you feel comfortable about his untimely death at his own words…
stop it…
Un panel de 5 miembros de la Corte Suprema de Brasil formó mayoría hoy para condenar al expresidente Bolsonaro por intento de golpe y formar parte de una organización criminal armada. La jueza Carmen Lucia votó a favor de condenar al líder de ultraderecha, poniéndose del lado de los jueces Alexandre de Moraes y Flavio Dino, en el juicio sobre un supuesto plan de golpe de Estado. El líder de ultraderecha de 70 años enfrenta hasta más de 40 años de cárcel por liderar una organización criminal armada tras perder las elecciones de 2022 contra Lula.
etiquetas: brasil, corte suprema, mayoría, condena, bolsonaro, lula, golpe de estado
» noticia original (www.lanacion.com.ar)
La cuenta oficial del primer ministro de Israel, Benjamin Netanyahu, en X ha escrito unos duros mensajes contra el Gobierno español y, en particular, contra el presidente Pedro Sánchez, al que le acusa de amenazar al estado judío por decir que no puede detener la lucha de Israel contra Hamás porque "España no tiene armas nucleares".
etiquetas: netanyahu, españa, sánchez, gaza
» noticia original (cadenaser.com)
Su verdadero lanzamiento llegó con su nombramiento como Jefe de Prensa del Ayuntamiento de Ferrol entre 2003 y 2007. Este cargo, aparentemente municipal, fue el trampolín crucial. No por el puesto en sí, sino por quién lo ostentaba: el alcalde Juan Manuel Juncal Rodríguez, una figura central en el entramado de poder que conectaba la política gallega con el negocio del narcotráfico a través de una red de testaferros y sociedades opacas.
etiquetas: narcos, galicia, miguel tellado, partido popular
» noticia original (xornalgalicia.com)
La familia política de extrema derecha Patriotas por Europa (PfE) y el grupo de extrema izquierda The Left registrarán antes de esta medianoche en el Parlamento Europeo sendas mociones de censura contra la presidenta de la Comisión Europea, Ursula von der Leyen. A falta del registro oficial, así lo han anunciado sus líderes tras conseguir las 72 firmas necesarias (un décimo de la Eurocámara) para su tramitación, aunque lo han hecho por motivos diferentes.
etiquetas: von der leyen, mociones de censura, izquierda, derecha, humillacion
» noticia original (www.infobae.com)
Los usuarios de redes sociales le han recordado casos en los que la ultraderecha ha asesinado a jóvenes antifascistas como el de Carlos Palomino o Guillem Agulló. También el de Lucrecia Pérez, la mujer dominicana asesinada por neonazis en 1992
etiquetas: tellado, charlie kirk, ultraderecha, pp
» noticia original (www.eldiario.es)
De viaje en Japón, el titular de Economía participa en un foro para conectar empresas en fase de crecimiento con inversores del país asiático
etiquetas: carlos cuerpo, inversiones, relaciones económicas, japón, españa
» noticia original (www.20minutos.es)
La Presidenta del Parlamento Europeo, Roberta Metsola, rechazó el jueves la propuesta de las facciones derechistas de guardar un minuto de silencio por el influyente conservador estadounidense asesinado Charlie Kirk. La iniciativa fue propuesta por primera vez por Charlie Weimers, eurodiputado del grupo derechista Conservadores y Reformistas Europeos (ECR), como una medida simbólica "para declarar que nuestro derecho a la libertad de expresión no puede ser extinguido", ...
etiquetas: parlamento europeo, ursula von der leyen, charlie kirk, crisis en gaza
» noticia original (www.politico.eu)