[1] Since acquiring Sun Microsystems well over a decade ago,
Oracle has owned MySQL. Under Oracle's watch,
MySQL has remained distinct. But unless you were MariaDB, until recently, few gave Oracle's stewardship much thought. And as each of the major cloud providers rolled out its own managed MySQL database services, Oracle provided relatively few reasons to draw customers to MySQL.
Well, that's no more. Fifteen months ago, Oracle introduced
MySQL HeatWave featuring its own optimized implementation of MySQL running in Oracle Cloud Infrastructure. Those optimizations should be transparent to the application. And now Oracle is making the 3.0 release of HeatWave, scaling up node size that will reduce costs for many workloads, and introducing in-database machine learning, which could benefit from higher density data nodes.
In making its move to become a serious competitor in the MySQL market, Oracle took the
database in a unique direction with HeatWave: It optimized for analytics in addition to transaction processing by taking advantage of MySQL's support for pluggable storage engines. In this case, it plugged in an in-memory columnar storage engine that operates side by side with the row store, incorporating optimizations tailored for processing analytic queries.
>> Read more. [2] Cognifiber, a company that builds stand-alone
photonic artificial intelligence accelerators for IoT analytics, has its sights set on a new goal — to replace traditional silicon with glass. By miniaturizing its in-fiber photonics, the startup claims it can bring server-grade capabilities to the edge.
The startup focuses on photonic computing, which goes a step further than most current commercial applications that use photonics just for communications across racks in the data center. Cognifiber has now announced a "
first of its kind" glass-based photonic chip specifically created for edge computing.
The company claims it has been able to miniaturize its previous designs to "a fraction" of the size. The "rack-size" system has been reduced to a 4U server with a height of 18cm, making it
feasible to deploy in offices, which also leads to a lower cost.
>> Read more. [3] The remote code execution (RCE) vulnerability in Spring Core, known as Spring4Shell, isn't an "everything's on fire kind of issue," according to Dallas Kaman, one of the security engineers who first posted confirmation of the vulnerability after it leaked this week. But patching will still be the wisest course of action for many organizations, said Kaman, principal security engineer at Praetorian — given that much remains unknown about the potential risks of the open source vulnerability.
In particular, there's a likelihood that attackers will find
new ways to exploit the vulnerability, says Praetorian CTO Richard Ford. This suggests that anyone who uses Spring, a popular framework in the development of Java applications, should consider deploying the patch — not just those who know they're vulnerable, according to Ford. Many security experts have pointed to the differences between Spring4Shell and Log4Shell — a far-more-critical but similarly named RCE flaw — indicating that this new RCE vulnerability is
not the "next Log4Shell" as some had initially feared.
At the same time, Spring4Shell is, in fact, being
actively targeted in attacks, according to reports from Kasada, GreyNoise Intelligence and Bad Packets. And researchers suspect that real-world applications are likely to be vulnerable — though reports still have yet to emerge confirming this.
>> Read more. 
No comments:
Post a Comment