If you’ve been waiting for the global memory shortage to ease anytime this year and hardware prices to drop, Intel CEO Lip-Bu Tan has some bad news. Speaking at a recent Cisco Systems conference, Tan said the crunch will likely last at least two more years.

According to Bloomberg, Tan cited information from two key players in the memory space who reportedly told him, “There’s no relief until 2028.” The timeline aligns with recent comments from Micron’s Christopher Moore, VP of Marketing for its Mobile and Client Business Unit, who said tight supply conditions are likely to linger for the foreseeable future.

The prolonged shortage is being driven largely by the explosive growth of AI infrastructure, which is soaking up memory at an unprecedented scale. With memory manufacturers increasingly focused on serving data centers and AI workloads, supply for consumer devices is being squeezed. For buyers, that could mean paying more for laptops, phones, PC components, and even TVs.

AI demand could keep your next hardware upgrade expensive

Nvidia’s next wave of AI hardware could make the situation even worse. According to Tan, the company’s latest Rubin platform will drive demand even higher. AI is going to “suck up a lot of memory,” Tan said, which could further tighten supply for consumer electronics.

For consumers, this means the pressure on hardware pricing is unlikely to ease anytime soon. Devices may continue to ship with higher price tags or more modest memory configurations unless memory supply expands significantly or demand from AI infrastructure slows. Until then, buyers may need to plan upgrades carefully or hold onto existing hardware longer than usual.

Five years ago, Databricks coined the term ‘data lakehouse’ to describe a new type of data architecture that combines a data lake with a data warehouse. That term and data architecture are now commonplace across the data industry for analytics workloads.

Now, Databricks is once again looking to create a new category with its Lakebase service, now generally available today. While the data lakehouse construct deals with OLAP (online analytical processing) databases, Lakebase is all about OLTP (online transaction processing) and operational databases. The Lakebase service has been in development since June 2025 and is based on technology Databricks gained via its acquisition of PostgreSQL database provider Neon. It was further enhanced in October of 2025 with the acquisition of Mooncake, which brought capabilities to help bridge PostgreSQL with lakehouse data formats.

Lakebase is a serverless operational database that represents a fundamental rethinking of how databases work in the age of autonomous AI agents. Early adopters, including easyJet, Hafnia and Warner Music Group, are cutting application delivery times by 75 to 95%, but the deeper architectural innovation positions databases as ephemeral, self-service infrastructure that AI agents can provision and manage without human intervention.

This isn’t just another managed Postgres service. Lakebase treats operational databases as lightweight, disposable compute running on data lake storage rather than monolithic systems requiring careful capacity planning and database administrator (DBA) oversight.

 “Really, for the vibe coding trend to take off, you need developers to believe they can actually create new apps very quickly, but you also need the central IT team, or DBAs, to be comfortable with the tsunami of apps and databases,” Databricks co-founder Reynold Xin told VentureBeat. “Classic databases simply won’t scale to that because they can’t afford to put a DBA per database and per app.”

92% faster delivery: From two months to five days

The production numbers demonstrate immediate impact beyond the agent provisioning vision. Hafnia reduced delivery time for production-ready applications from two months to five days — or 92% — using Lakebase as the transactional engine for their internal operations portal. The shipping company moved beyond static BI reports to real-time business applications for fleet, commercial and finance workflows.

EasyJet consolidated more than 100 Git repositories into just two and cut development cycles from nine months to four months — a 56% reduction — while building a web-based revenue management hub on Lakebase to replace a decade-old desktop app and one of Europe’s largest legacy SQL Server environments.

Warner Music Group is moving insights directly into production systems using the unified foundation, while Quantum Capital Group uses it to maintain consistent, governed data for identifying and evaluating oil and gas investments — eliminating the data duplication that previously forced teams to maintain multiple copies in different formats.

The acceleration stems from the elimination of two major bottlenecks: database cloning for test environments and ETL pipeline maintenance for syncing operational and analytical data.

Technical architecture: Why this isn’t just managed Postgres

Traditional databases couple storage and compute — organizations provision a database instance with attached storage and scale by adding more instances or storage. AWS Aurora innovated by separating these layers using proprietary storage, but the storage remained locked inside AWS’s ecosystem and wasn’t independently accessible for analytics.

Lakebase takes the separation of storage and compute to its logical conclusion by putting storage directly in the data lakehouse. The compute layer runs essentially vanilla PostgreSQL— maintaining full compatibility with the Postgres ecosystem — but every write goes to lakehouse storage in formats that Spark, Databricks SQL and other analytics engines can immediately query without ETL.

“The unique technical insight was that data lakes decouple storage from compute, which was great, but we need to introduce data management capabilities like governance and transaction management into the data lake,” Xin explained. “We’re actually not that different from the lakehouse concept, but we’re building lightweight, ephemeral compute for OLTP databases on top.”

Databricks built Lakebase with the technology it gained from the acquisition of Neon. But Xin emphasized that Databricks significantly expanded Neon’s original capabilities to create something fundamentally different.

“They didn’t have the enterprise experience, and they didn’t have the cloud scale,” Xin said. “We brought the Neon team’s novel architectural idea together with the robustness of the Databricks infrastructure and combined them. So now we’ve created a super scalable platform.”

From hundreds of databases to millions built for agentic AI

Xin outlined a vision directly tied to the economics of AI coding tools that explains why the Lakebase construct matters beyond current use cases. As development costs plummet, enterprises will shift from buying hundreds of SaaS applications to building millions of bespoke internal applications.

“As the cost of software development goes down, which we’re seeing today because of AI coding tools, it will shift from the proliferation of SaaS in the last 10 to 15 years to the proliferation of in-house application development,” Xin said. “Instead of building maybe hundreds of applications, they’ll be building millions of bespoke apps over time.”

This creates an impossible fleet management problem with traditional approaches. You cannot hire enough DBAs to manually provision, monitor and troubleshoot thousands of databases. Xin’s solution: Treat database management itself as a data problem rather than an operations problem.

Lakebase stores all telemetry and metadata — query performance, resource utilization, connection patterns, error rates — directly in the lakehouse, where it can be analyzed using standard data engineering and data science tools. Instead of configuring dashboards in database-specific monitoring tools, data teams query telemetry data with SQL or analyze it with machine learning models to identify outliers and predict issues.

“Instead of creating a dashboard for every 50 or 100 databases, you can actually look at the chart to understand if something has misbehaved,” Xin explained. “Database management will look very similar to an analytics problem. You look at outliers, you look at trends, you try to understand why things happen. This is how you manage at scale when agents are creating and destroying databases programmatically.”

The implications extend to autonomous agents themselves. An AI agent experiencing performance issues could query the telemetry data to diagnose problems — treating database operations as just another analytics task rather than requiring specialized DBA knowledge. Database management becomes something agents can do for themselves using the same data analysis capabilities they already have.

What this means for enterprise data teams

The Lakebase construct signals a fundamental shift in how enterprises should think about operational databases — not as precious, carefully managed infrastructure requiring specialized DBAs, but as ephemeral, self-service resources that scale programmatically like cloud compute. 

This matters whether or not autonomous agents materialize as quickly as Databricks envisions, because the underlying architectural principle — treating database management as an analytics problem rather than an operations problem — changes the skill sets and team structures enterprises need.

Data leaders should pay attention to the convergence of operational and analytical data happening across the industry. When writes to an operational database are immediately queryable by analytics engines without ETL, the traditional boundaries between transactional systems and data warehouses blur. This unified architecture reduces the operational overhead of maintaining separate systems, but it also requires rethinking data team structures built around those boundaries.

When lakehouse launched, competitors rejected the concept before eventually adopting it themselves. Xin expects the same trajectory for Lakebase. 

“It just makes sense to separate storage and compute and put all the storage in the lake — it enables so many capabilities and possibilities,” he said.

OnePlus is tipped to deliver a major camera upgrade with its upcoming flagship, the OnePlus 16, expected later in 2026.

According to a new leak, the device will feature a 200MP telephoto sensor measuring 1/1.56 inches, a significant jump from the 50MP 1/2.76-inch telephoto lens found on the OnePlus 15. This change could dramatically improve zoom performance and image detail, while also introducing telephoto macro capabilities for close-up shots.

The leak, shared by @OnePlusClub on X, suggests OnePlus is finally addressing criticism of the OnePlus 15’s scaled-down camera system. That model shipped with smaller sensors and lacked Hasselblad colour tuning, leaving photography enthusiasts underwhelmed despite strong performance elsewhere.

The OnePlus 16’s rumoured telephoto upgrade would put it in line with rivals such as Oppo’s Find X9 series, which already offers telephoto macro functionality. 

Strong leadership is essential for IEEE to advance technology for humanity. The organization depends on the dedicated service of its volunteers to advance its mission.

Each year, the Nominations and Appointments (N&A) Committee is responsible for recommending candidates to the Board of Directors and the IEEE Assembly for volunteer leadership positions, including president-elect, corporate officers, committee chairs, and committee members. See below for the complete list.

By nominating qualified, experienced, committed volunteers, you help ensure continuity, good governance, and thoughtful decision-making at the highest levels of the organization. We encourage nominators to take a deliberate approach and align nominations with each candidate’s demonstrated experience and the specific qualifications of the role.

To nominate a person for a position, complete this form.

The N&A Committee is currently seeking nominees for the following positions:

2028 IEEE President-Elect (who will be elected in 2027 and will serve as President in 2029 )

2027 IEEE Corporate Officers

• Secretary
• Treasurer
• Vice President, Educational Activities
• Vice President, Publication Services and Products

2027 IEEE Committees Chairs and Members

• Audit
• Awards Board
• Collaboration and Engagement
• Conduct Review
• Election Oversight
• Employee Benefits and Compensation
• Ethics and Member Conduct
• European Public Policy
• Fellow
• Fellow Nominations and Appointments
• Governance
• History
• Humanitarian Technologies Board
• Industry Engagement
• Innovations (formerly New Initiatives)
• Nominations and Appointments
• Public Visibility
• Tellers

Deadlines for nominations

15 March

• Vice President, Educational Activities
• Vice President, Publication Services and Products
• Committee Chairs

15 June

• President-Elect
• Secretary
• Treasurer
• Committee Members

Deadlines for self-nominations

30 March

• Vice President, Educational Activities
• Vice President, Publication Services and Products
• Committee Chairs

30 June

• President-Elect
• Secretary
• Treasurer
• Committee Members

Who can nominate

Anyone may submit a nomination. Self-nominations are encouraged. Nominators need not be IEEE members, but nominees must meet specific qualifications. An IEEE organizational unit may submit recommendations endorsed by its governing body or the body’s designee.

A person may be nominated for more than one position, however nominators are encouraged to focus on positions that align closely with the candidate’s qualifications and experience. Nominators need not contact their nominees before submitting the form. The IEEE N&A committee will contact eligible nominees for the required documentation and for their interest and willingness to be considered for the position.

How to nominate

For information about the positions, including qualifications, estimates of the time required by each position during the term of office, and the nomination process check the IEEE Nominations and Appointments Committee website. To nominate a person for a position, complete this form.

Nominating tips

Make sure to check eligibility requirements on the N&A committee website before submitting a nomination as those that do not meet the stated requirements will not be advanced.

Volunteers with relevant prior experience in lower-level IEEE committees and units are recommended by the committee more often than volunteers without such experience.

Individuals recommended for president-elect and corporate officer positions are more likely to be recommended if they possess a strong track record of leadership, governance experience, and relevant accomplishments within and outside IEEE. Recommended president-elect candidates must have served on the IEEE Board of Directors for at least one year.

Contact nominations@ieee.org with any questions.