Month: July 2022

Article originally posted on InfoQ. Visit InfoQ

The long-term-support (LTS) version 3.1 of Microsoft .NET Core Framework is slated to go out of support on December 13th, 2022. Microsoft recommends upgrading .NET Core 3.1 applications to .NET 6.0 to stay supported for the future, while the developers have mixed feelings about the .NET support policy.

Microsoft .NET Core Framework version 3.1, released in 2019, is approaching the end of its support date. According to Dominique Whittaker, senior program manager at Microsoft, customers using the 3.1 version should move to .NET 6 or 7 to still receive official support and security patches.

Whittaker explains that the .NET Core 3.1 applications will still run after the end of support date, but that customers can be exposed to potential security flaws that will be patched only for supported versions.

Version 3.1 is what Microsoft calls a long-term-support (LTS) release, having a support lifecycle of three years since the release date. Non-LTS (or “current”) releases, such as .NET 7.0, have a shorter support lifecycle of 18 months, as Microsoft will support them for six months after the release of the next LTS version. Microsoft schedules .NET versions to launch one major version of .NET a year, alternating between LTS and current versions.

The latest LTS version of .NET is 6.0, which Microsoft plans to support until November 12, 2024. Microsoft expects to release .NET 7.0, a non-LTS version, in November 2022, meaning that the current .NET Core 3.1 customers can choose between upgrading to .NET 6 or 7 before the end of the .NET Core 3.1 support date.

Upgrading to .NET 6.0 involves a change of one line in the project file to change the target framework version. However, there might be runtime or source-code incompatibilities between .NET Core 3.1 and .NET 6.0.

Microsoft recommends that developers check the official compatibility guide for any issues when upgrading their applications and provides an open-source upgrade tool called upgrade-assistant. The tool analyzes the application code, updates the project files, checks for breaking changes, and does some automatic code fixes – but developers will still have to do some manual fixes.

The developer community’s reactions on social networks were mixed. Some developers argue that a three-year support cycle is too short for corporate projects, while others recognize that the growing complexity of code dependencies makes frequent version upgrades a necessity and a new way of work. Rockford Lhotka, the creator of the widely used CSLA.NET application framework, explains that most of the pain in .NET code upgrades comes from moving the old .NET Framework into the modern .NET framework, while upgrades between .NET Core versions are substantially less work-intensive.

Microsoft regularly publishes summarised telemetry information derived from the usage of  .NET SDK. According to the data for June 2022, the most used version of .NET Framework for applications is precisely the .NET Core 3.1, accounting for 31% of the telemetry data.

Posted on nosqlgooglealerts. Visit nosqlgooglealerts

By

A cloud database is an organized and managed collection of data in an IT system that resides on a public, private or hybrid cloud computing platform. From an overall design and functionality perspective, a cloud database is no different than an on-premises one that runs on an organization’s own data center systems. The biggest difference between them lies in how the database is deployed and managed.

For example, the same database appears identical to end users and applications, whether it’s on premises or in the cloud. Depending on the particular database software that’s used, cloud databases can store structured, unstructured or semistructured data, just as their on-premises counterparts do.

But using a cloud database changes the responsibilities of IT and data management teams. Cloud vendors install and manage the underlying system infrastructure and, in managed services environments, the database platform. That reduces the routine management work traditionally done by IT operations workers and database administrators (DBAs). A DBA can then take on other tasks, such as optimizing databases for applications and tracking the usage and cost of cloud database systems.

Like other IT systems, database deployments are clearly shifting toward the cloud. In a report on cloud databases published in December 2021, Gartner forecasted that they would account for 50% of total database management system (DBMS) revenues worldwide in 2022, a year earlier than it previously predicted. Also, in a survey of 753 cloud users conducted in late 2021 by IT management tools vendor Flexera, 55% said their organizations were using data warehouses in the cloud, while 49% had adopted cloud-based relational database services and 38% were using NoSQL database services.

This comprehensive guide to cloud databases further explains what they are, how they work and their potential IT and business benefits for organizations, as compared with on-premises databases. You’ll also find information on cloud database technologies, vendors and security issues, plus more details on database administration responsibilities in the cloud. Throughout the guide, hyperlinks point to related articles that cover those topics and others in more depth.

How cloud databases work

In businesses, databases are used to collect, organize and deliver data to executives and workers for operational and analytics applications. In general, cloud databases provide the same data processing, management and access capabilities as on-premises ones. Existing on-premises databases usually can be migrated to the cloud, along with the applications they support.

Instead of traditional software licenses, pricing is based on the use of system resources, which can be provisioned on demand as needed to meet processing workloads. Alternatively, users can reserve database instances — typically for at least a year — to get discounted pricing on regular workloads with consistent capacity requirements.

Organizations that are implementing databases in the public cloud choose between the following two deployment models:

1. Self-managed database. This is an infrastructure as a service (IaaS) environment, in which the database runs in a virtual machine on a system operated by a cloud provider. The provider manages and supports the cloud infrastructure, including servers, operating systems and storage devices. But the user organization is responsible for database deployment, administration and maintenance. As a result, it’s akin to an on-premises deployment for the DBA, who retains full management control of the database.
2. Managed database service. Database as a service (DBaaS) environments are fully managed by the vendor, which could be a cloud platform provider or another database vendor that runs its cloud DBMS on a platform provider’s infrastructure. Under the DBaaS model, both the system infrastructure and the database platform are managed for the customer. The DBaaS vendor handles provisioning, backups, scaling, patching, upgrades and other basic database administration functions, while the DBA monitors the database and coordinates with the vendor on some administrative tasks. Similar data warehouse as a service (DWaaS) offerings are also available for deployments of cloud data warehouses.

In addition, some cloud providers — Amazon Web Services (AWS) and Oracle, for example — offer versions of their DBaaS technologies for installation in on-premises data centers as part of a private cloud or a hybrid cloud infrastructure that combines public and private clouds. As with a regular DBaaS environment, the provider deploys the databases on its own systems and manages them for customers, except that it instead delivers the systems to a customer’s data center to run there and then manages the databases remotely.

Cloud database benefits

Compared with running databases on premises, cloud databases offer the following potential IT and business advantages to an organization:

• Increased scalability and flexibility. Cloud database systems can be easily scaled up by adding more processing and storage capacity when workloads increase. Some vendors offer autoscaling features that do so dynamically, without users even needing to submit a request. In addition, an organization can quickly deploy new databases and shut down ones that it no longer needs, matching its database strategy to the speed of business.

• Elimination of IT infrastructure. Because the cloud provider is responsible for the system infrastructure in a cloud database environment, an organization may be able to reduce its own IT footprint by decommissioning systems, especially if it’s moving on-premises databases to the cloud. At the very least, it can avoid the need to add more systems when it deploys new databases.
• Faster access to new features. With on-premises databases, users typically need to wait for and then install a software upgrade to get new features and functionality. DBaaS vendors can update their cloud databases on an ongoing basis, enabling organizations to take advantage of new features as soon as they’re available.
• More reliable systems with guaranteed uptime. Cloud vendors provide high availability, automated backup and disaster recovery capabilities that may be more advanced than what an organization implements itself. They also guarantee uptime percentages as part of their cloud service-level agreement (cloud SLA), giving them an incentive to keep cloud database platforms running smoothly.
• Cost savings. Reduced capital expenditures, data center operating costs and space needs in IT facilities, as well as possible IT staff cuts, can result in lower spending overall. But that isn’t a sure thing: Pay-as-you-go cloud services can cost more than planned if resource utilization exceeds expectations or, conversely, if excess capacity goes unnoticed. A cloud database environment needs to be monitored closely to keep cloud costs under control.

On the other hand, on-premises databases may still be best for some organizations, particularly if they want or need to retain full control of the database environment. Get advice on how to decide between cloud and on-premises databases in an article by Chris Foot, a senior strategist and consultant at IT services provider RadixBay.

Cloud database architecture considerations

The most straightforward approach for deploying cloud databases is to use a single public cloud platform. That ensures consistency on the underlying cloud infrastructure and a single cloud provider to work with, even if multiple DBaaS vendors are involved. But it may not always be feasible or meet an organization’s IT and business needs. As a result, other architectural strategies may need to be explored.

One option is deploying databases across a hybrid cloud, putting some of them in a public cloud and others in a private cloud set up on premises.

In an article by technology writer George Lawton on creating a hybrid cloud database environment, Alexander Wurm, a research analyst at advisory services firm Nucleus Research, said using one enables organizations to “reap the benefits of the modern cloud, such as regular updates and elastic scalability, without interfering with the security and reliability of existing on-premises infrastructure in support of mission-critical workloads.”

Lawton listed eight items to consider when planning a hybrid cloud database strategy, including data security, data egress charges, potential data latency issues and how to group applications and databases together into logical units to make the deployment process more manageable.

A multi-cloud database architecture is an even more expansive approach that involves the use of multiple public cloud platforms. It can avoid cloud provider lock-in and enable organizations to deploy databases and applications in the cloud platform that’s best suited to them. In another article, IT professional Jeff McCormick detailed a set of 10 multi-cloud database management best practices, including the following steps:

1. Start with a comprehensive plan and a governance framework.
2. Run the right database in the right cloud.
3. Use data services that support multi-cloud environments.
4. Exploit managed database services, or DBaaS.
5. Consider database portability across multiple clouds.
6. Reduce the number of different databases.
7. Reduce the number of the same databases.
8. Optimize data access for applications and end users.
9. Keep data local in one cloud platform when possible.
10. Connect cloud networks to reduce data latency.

Posted on mongodb google news. Visit mongodb google news

At the time of writing, there are 714,548 open cybersecurity jobs across the United States, with a supply-to-demand ratio of 66 qualified candidates to every 100 open positions.

But database-as-a-service provider MongoDB Inc. has no issue finding trained applicants when there’s an opening on its security team.

“We have the Champions Program,” said Lena Smart (pictured), chief information security officer of MongoDB Inc. “So, the minute one of my jobs goes on the board, they get first dibs at it … [and] there are ripple effects out from over a hundred people internally. I think just having that, that’s been a game changer.”

Smart spoke with theCUBE industry analyst Dave Vellante at AWS re:Inforce, during an exclusive broadcast on theCUBE, SiliconANGLE Media’s livestreaming studio. They discussed MongoDB’s Security Champions Program, Smart’s fiscally responsible attitude toward security, and how keeping ahead in security requires a “meerkat attitude” to watch what could be on the horizon. (* Disclosure below.)

MongoDB builds an in-house, interdepartmental team of security volunteers

MongoDB’s Security Champions Program was created out of Smart’s desire to help underrepresented groups advance in their tech careers, but it’s turned into a win-win-win situation for the security department, the company and employees.

There’s no bar to entry for the program, which is open to anyone in any position across the company. Currently, over a hundred MongoDB employees are taking part, and they represent every department and every geographical area where MongoDB has a presence. If an employee wishes to learn cyber skills, they simply volunteer to join the Security Champions team (with their supervisor’s approval). Then in addition to their regular responsibilities, they work alongside MongoDB’s security experts, assisting with tasks such as preventing phishing campaigns, testing things like Queryable Encryption, and learning Amazon Web Services toolsets.

The program flips the security paradigm by turning employees from a security liability into an asset, generating a culture of security awareness within MongoDB, according to Smart. It also builds an in-house pool of security skilled employees that jump at the chance to join Smart’s department whenever there’s an opening. And it gives the security team an awareness of operations across the company and breaks barriers between departments.

“We have people who have such an in-depth knowledge in other areas of the business that I could never learn, no matter how much time I had,” Smart stated. “To have that scope and depth of people with long tenure in the company, technically brilliant, [that] really want to understand how they can apply the cultural values that we live with each day to make our security programs stronger … that’s been a game changer for us.”

Strong partnerships and fiscal responsibility mark Smart’s security strategy

MongoDB’s executive board is supportive of Smart and her team, and she meets with them regularly to discuss the company’s security needs.

“I actually get their attention for at least an hour once a quarter, which is almost unheard of,” she said.

Her close relationship with the company’s directors, and the fact that many of them serve on other boards, has helped her build a network with other CISOs and share knowledge. She specifically mentioned Dev Ittycheria, MongoDB’s president and chief executive officer.

“Dev is a huge, huge fan of security and [governance, risk and compliance],” Smart said.

Unlike some CISOs who, according to Smart, “have every tool that’s out there ‘cuz it’s shiny and it’s new’ and they know the board is never gonna say no,” MongoDB’s naturally frugal CISO takes a fiscally responsible approach to spending the company’s security budget.

“I always tell my team, treat this money as if it’s your own,” Smart said.

When she evaluates a new tool, she makes a point of speaking to that company’s CISO to ensure MongoDB is getting the best deal. She also proposes partnerships that could mutually benefit both companies. MongoDB’s partnership with Amazon Web Services Inc. falls into this camp.

“[AWS] is very proactive when it comes to where we are from the security standpoint,” Smart said. “When we sit down with them … it is not a conversation that’s a surprise. When I tell them this is what we need, they’re like, ‘Yep. We’re on that already.’”

Here’s the complete video interview, part of SiliconANGLE’s and theCUBE’s coverage of the AWS re:Inforce event:

(* Disclosure: This is an unsponsored editorial segment. However, theCUBE is a paid media partner for AWS re:Inforce. Amazon Web Services Inc. and other sponsors of theCUBE’s event coverage have no editorial control over content on theCUBE or SiliconANGLE.)

Photo: SiliconANGLE

Article originally posted on mongodb google news. Visit mongodb google news

Article originally posted on InfoQ. Visit InfoQ

After over four years in development, Google open source quantum programming framework Cirq has reached stability and established itself as the lingua franca that Google engineers use to write quantum programs for Google’s own quantum processors.

The significance of the 1.0 release is that Cirq has support for the vast majority of workflows for these systems and is considered to be a stable API that we will only update with breaking changes at major version numbers.

This means that future point releases, e.g., 1.1, will be compatible with its base major version, e.g, 1.0. New major releases, e.g., 2.0, is where breaking changes could occur.

Cirq is aimed at today’s noisy intermediate-scale quantum computers, sporting a few hundred qubits and few thousands of quantum gates at most. According to Google, current quantum computers require dealing with the details of their hardware configuration to achieve state-of-the-art results, which accounts for the kind of abstractions the framework provides.

This means, for example, that Cirq enables specifying the mapping between the algorithm and the hardware, providing fine-grained control down to the gate level, as well as dealing with specific processor constraints, which could result in faulty computations when not addressed correctly. A Cirq program, also known as a circuit, is a collection of moments. Each moment is a collection of simultaneous operations, where each operation is the result of applying a gate to a disjoint subset of the available qubits.

Since its introduction in 2018, Cirq has been extended through a number of libraries exploring quantum computing research areas, including TensorFlow Quantum, OpenFermion, Pytket, and others. In particular, TensorFlow Quantum has been used to train a machine learning model on 30 qubits at a rate of 1.1 petaflops per second. OpenFermion instead is a library for compiling and analyzing quantum algorithms to simulate fermionic systems, including quantum chemistry.

As a last remark, Cirq has gained support with several quantum computing cloud services, including AQT, IonQ, Pascal, Rigetti, and Azure Quantum, which enable running Cirq programs on their hardware, says Google.

If you do not have a quantum processor available, you could experiment with Cirq using Google Quantum Virtual Machine, a Colab notebook that emulates a Google quantum processor. Currently, the tool can emulate two of Google’s processors: Weber and Rainbow. The Google Quantum Virtual Machine can also be supercharged to run in Google Cloud in case additional emulation power is required.

Article originally posted on InfoQ. Visit InfoQ

With the recent release of GitLab version 15.2, open-core company GitLab Inc. has announced a series of improvements, including an enhanced Wiki editor, adding SAML integration for enterprises, improving dashboards, and adding internal notes. From a security perspective, basic container scanning is improved, and developers have new abilities to ensure upstream dependencies have not been tampered with.

GitLab 15.0 was released in May and was incrementally improved in June with version 15.1.  July’s release of 15.2 brings further improvements and fixes:

• Many improvements have been made to the editor for the Wiki, such as adding links, media, and code blocks with syntax highlighting for over 100 languages. Editing diagrams is much easier with a live preview available. Thanks to a new popover menu, links and media are now easier to work with. Wikis can now also be set up for groups, allowing documentation to span multiple projects.
• For organizations using a self-managed GitLab installation rather than the SaaS offering at GitLab.com, group memberships can now be mapped to a group in their identity provider using SAML (Security Assertion Markup Language). This removes the need to duplicate group memberships between the identity provider and GitLab for self-managed installations.
• The Value Stream Analytics dashboard now includes the four key DORA metrics, and a trend chart for the Time to Restore Service and Change Failure Rate metrics, allowing users to see team performance and the value flow of the organization.
• GitLab can now generate SLSA (Supply-chain Levels for Software Artifacts) attestations to store in a registry, helping developers verify that artifacts have not been tampered with.
• Issue planning for agile teams using regular iteration cadences becomes easier, as GitLab now allows admins to set up iterations on regular cadences (for example, bi-weekly), and it’s now possible to have unfinished issues roll over automatically from one cadence to the next.
• Internal notes are new in GitLab 15. These allow organisations with publically-facing issues and epics to use notes internally within the team which is not seen by the public. This can help protect confidential or personal data relevant to the issue that might otherwise be exposed.
• Basic container scanning is now available in all tiers, allowing all developers to find basic vulnerabilities
• Scan execution policies can also now be implemented at group and subgroup levels, allowing security teams to apply policy consistently.
• The Advanced Search functionality is now compatible with OpenSearch – removing the need for admins using AWS-managed service to use older versions of Elasticsearch.
• Nested CI/CD variables can now be used with environments – enabling organisations to remove duplication and hierarchically organise variables.
• This nesting can cause complex CI/CD configurations with nested includes to be hard to debug and manage, so GitLab now incorporates easy links to all included configuration files and templates.
• Users can now manage customer contacts and organizations within GitLab as part of a nascent customer relations management (CRM) feature.
• Incident timelines can now be created, allowing organizations to log and report on problems that occur without leaving the GitLab interface.

Those eager to upgrade should also consider that there are several breaking changes in version 15, which are detailed here. The full release announcements for 15.0, 15.1, and 15.2 are also available.

Posted on mongodb google news. Visit mongodb google news

Park Avenue Securities LLC acquired a new stake in MongoDB, Inc. (NASDAQ:MDB – Get Rating) during the 1st quarter, according to its most recent disclosure with the Securities and Exchange Commission. The fund acquired 522 shares of the company’s stock, valued at approximately $232,000.

Several other hedge funds and other institutional investors have also modified their holdings of the company. Norges Bank acquired a new position in MongoDB during the 4th quarter worth approximately $277,934,000. TD Asset Management Inc. lifted its position in MongoDB by 153.9% during the 4th quarter. TD Asset Management Inc. now owns 525,000 shares of the company’s stock worth $277,909,000 after acquiring an additional 318,259 shares in the last quarter. Ardevora Asset Management LLP acquired a new position in MongoDB during the 4th quarter worth approximately $74,638,000. Geode Capital Management LLC lifted its position in MongoDB by 7.1% during the 4th quarter. Geode Capital Management LLC now owns 864,250 shares of the company’s stock worth $456,904,000 after acquiring an additional 56,940 shares in the last quarter. Finally, Schonfeld Strategic Advisors LLC lifted its position in MongoDB by 1,488.2% during the 4th quarter. Schonfeld Strategic Advisors LLC now owns 47,646 shares of the company’s stock worth $25,221,000 after acquiring an additional 44,646 shares in the last quarter. 88.70% of the stock is owned by institutional investors and hedge funds.

Get MongoDB alerts:

Insider Activity at MongoDB

In related news, insider Thomas Bull sold 489 shares of the firm’s stock in a transaction on Tuesday, July 5th. The stock was sold at an average price of $264.45, for a total transaction of $129,316.05. Following the completion of the sale, the insider now directly owns 17,104 shares of the company’s stock, valued at approximately $4,523,152.80. The transaction was disclosed in a legal filing with the Securities & Exchange Commission, which is available at the SEC website. In other news, Director Dwight A. Merriman sold 14,000 shares of MongoDB stock in a transaction on Monday, May 2nd. The stock was sold at an average price of $349.22, for a total value of $4,889,080.00. Following the completion of the sale, the director now directly owns 1,323,384 shares of the company’s stock, valued at approximately $462,152,160.48. The transaction was disclosed in a legal filing with the Securities & Exchange Commission, which can be accessed through this link. Also, insider Thomas Bull sold 489 shares of MongoDB stock in a transaction on Tuesday, July 5th. The shares were sold at an average price of $264.45, for a total value of $129,316.05. Following the completion of the sale, the insider now directly owns 17,104 shares of the company’s stock, valued at $4,523,152.80. The disclosure for this sale can be found here. Insiders sold 77,185 shares of company stock valued at $23,594,636 in the last three months. Corporate insiders own 5.70% of the company’s stock.

MongoDB Trading Up 8.7 %

Shares of MongoDB stock opened at $289.92 on Thursday. The company has a quick ratio of 4.16, a current ratio of 4.16 and a debt-to-equity ratio of 1.69. The firm has a market cap of $19.75 billion, a price-to-earnings ratio of -59.90 and a beta of 0.91. The business has a fifty day simple moving average of $273.47 and a 200-day simple moving average of $340.65. MongoDB, Inc. has a fifty-two week low of $213.39 and a fifty-two week high of $590.00.

MongoDB (NASDAQ:MDB – Get Rating) last issued its earnings results on Wednesday, June 1st. The company reported ($1.15) earnings per share (EPS) for the quarter, topping analysts’ consensus estimates of ($1.34) by $0.19. MongoDB had a negative return on equity of 45.56% and a negative net margin of 32.75%. The business had revenue of $285.45 million during the quarter, compared to analysts’ expectations of $267.10 million. During the same period in the prior year, the firm posted ($0.98) EPS. MongoDB’s quarterly revenue was up 57.1% compared to the same quarter last year. On average, equities analysts forecast that MongoDB, Inc. will post -5.08 EPS for the current fiscal year.

Wall Street Analysts Forecast Growth

Several research firms have issued reports on MDB. UBS Group lifted their price objective on MongoDB from $315.00 to $345.00 and gave the stock a “buy” rating in a report on Wednesday, June 8th. Canaccord Genuity Group dropped their price objective on MongoDB from $400.00 to $300.00 in a report on Thursday, June 2nd. Robert W. Baird began coverage on MongoDB in a report on Tuesday, July 12th. They set an “outperform” rating and a $360.00 price objective on the stock. Mizuho dropped their price objective on MongoDB from $325.00 to $270.00 and set a “neutral” rating on the stock in a report on Wednesday, May 18th. Finally, Royal Bank of Canada lifted their price objective on MongoDB from $325.00 to $375.00 in a report on Thursday, June 9th. One analyst has rated the stock with a sell rating, one has given a hold rating and sixteen have given a buy rating to the stock. Based on data from MarketBeat.com, the company currently has a consensus rating of “Moderate Buy” and a consensus target price of $401.17.

MongoDB Profile

(Get Rating)

MongoDB, Inc provides general purpose database platform worldwide. The company offers MongoDB Enterprise Advanced, a commercial database server for enterprise customers to run in the cloud, on-premise, or in a hybrid environment; MongoDB Atlas, a hosted multi-cloud database-as-a-service solution; and Community Server, a free-to-download version of its database, which includes the functionality that developers need to get started with MongoDB.

Further Reading

• Get a free copy of the StockNews.com research report on MongoDB (MDB)
• The MarketBeat Podcast: Portfolio Management in Market Downturns
• Can These Two Airline Stocks Overcome Gravity And Fly Higher?
• Shopify Stock Rallies Despite Quarterly Loss
• Two Automation Stocks The Institutions Are Buying 
• Can Owens-Corning Insulate Your Portfolio?  

Want to see what other hedge funds are holding MDB? Visit HoldingsChannel.com to get the latest 13F filings and insider trades for MongoDB, Inc. (NASDAQ:MDB – Get Rating).

Want More Great Investing Ideas?

• Bear Market Game Plan!
  
• The 10 Best Stocks to Own in 2022
• 7 Stocks to Buy and Hold Forever
• 3 Stocks to DOUBLE This Year

Receive News & Ratings for MongoDB Daily – Enter your email address below to receive a concise daily summary of the latest news and analysts’ ratings for MongoDB and related companies with MarketBeat.com’s FREE daily email newsletter.

Article originally posted on mongodb google news. Visit mongodb google news

Posted on mongodb google news. Visit mongodb google news

Park Avenue Securities LLC bought a new stake in MongoDB, Inc. (NASDAQ:MDB – Get Rating) during the first quarter, according to the company in its most recent disclosure with the Securities and Exchange Commission (SEC). The fund bought 522 shares of the company’s stock, valued at approximately $232,000.

A number of other hedge funds and other institutional investors have also modified their holdings of MDB. Russell Investments Group Ltd. increased its position in MongoDB by 27.1% during the fourth quarter. Russell Investments Group Ltd. now owns 8,236 shares of the company’s stock worth $4,359,000 after buying an additional 1,755 shares during the last quarter. Avantax Advisory Services Inc. bought a new stake in shares of MongoDB during the fourth quarter worth approximately $266,000. Strs Ohio boosted its holdings in shares of MongoDB by 390.0% during the fourth quarter. Strs Ohio now owns 2,656 shares of the company’s stock worth $1,405,000 after acquiring an additional 2,114 shares during the period. National Bank of Canada FI bought a new stake in shares of MongoDB during the fourth quarter worth approximately $184,000. Finally, Janney Montgomery Scott LLC boosted its holdings in shares of MongoDB by 8.6% during the fourth quarter. Janney Montgomery Scott LLC now owns 670 shares of the company’s stock worth $355,000 after acquiring an additional 53 shares during the period. Institutional investors and hedge funds own 88.70% of the company’s stock.

MongoDB Stock Performance

Shares of MDB opened at $289.92 on Thursday. The company has a current ratio of 4.16, a quick ratio of 4.16 and a debt-to-equity ratio of 1.69. The stock has a market capitalization of $19.75 billion, a P/E ratio of -59.90 and a beta of 0.91. The firm’s fifty day simple moving average is $273.47 and its two-hundred day simple moving average is $340.65. MongoDB, Inc. has a 12 month low of $213.39 and a 12 month high of $590.00.

MongoDB (NASDAQ:MDB – Get Rating) last released its quarterly earnings data on Wednesday, June 1st. The company reported ($1.15) earnings per share (EPS) for the quarter, topping analysts’ consensus estimates of ($1.34) by $0.19. The company had revenue of $285.45 million for the quarter, compared to analysts’ expectations of $267.10 million. MongoDB had a negative net margin of 32.75% and a negative return on equity of 45.56%. The business’s revenue was up 57.1% on a year-over-year basis. During the same quarter in the prior year, the firm earned ($0.98) EPS. As a group, analysts predict that MongoDB, Inc. will post -5.08 EPS for the current year.

Insider Activity at MongoDB

In related news, Director Dwight A. Merriman sold 14,000 shares of the firm’s stock in a transaction dated Monday, May 2nd. The shares were sold at an average price of $349.22, for a total value of $4,889,080.00. Following the transaction, the director now owns 1,323,384 shares of the company’s stock, valued at approximately $462,152,160.48. The sale was disclosed in a legal filing with the SEC, which is available through this hyperlink. In other MongoDB news, Director Dwight A. Merriman sold 14,000 shares of the stock in a transaction dated Monday, May 2nd. The shares were sold at an average price of $349.22, for a total value of $4,889,080.00. Following the completion of the sale, the director now owns 1,323,384 shares in the company, valued at approximately $462,152,160.48. The transaction was disclosed in a document filed with the SEC, which is available at this link. Also, CEO Dev Ittycheria sold 35,000 shares of the stock in a transaction dated Thursday, May 5th. The shares were sold at an average price of $321.10, for a total transaction of $11,238,500.00. Following the completion of the sale, the chief executive officer now owns 204,744 shares of the company’s stock, valued at approximately $65,743,298.40. The disclosure for this sale can be found here. In the last quarter, insiders have sold 77,185 shares of company stock valued at $23,594,636. 5.70% of the stock is owned by corporate insiders.

Analyst Ratings Changes

MDB has been the subject of a number of research analyst reports. Piper Sandler reduced their price objective on MongoDB from $430.00 to $375.00 and set an “overweight” rating for the company in a report on Monday, July 18th. Credit Suisse Group cut their price target on MongoDB from $650.00 to $500.00 and set an “outperform” rating for the company in a research note on Thursday, June 2nd. Canaccord Genuity Group cut their price target on MongoDB from $400.00 to $300.00 in a research note on Thursday, June 2nd. Mizuho cut their price target on MongoDB from $325.00 to $270.00 and set a “neutral” rating for the company in a research note on Wednesday, May 18th. Finally, William Blair reiterated an “outperform” rating on shares of MongoDB in a research note on Tuesday, May 24th. One research analyst has rated the stock with a sell rating, one has assigned a hold rating and sixteen have assigned a buy rating to the company’s stock. Based on data from MarketBeat.com, MongoDB currently has an average rating of “Moderate Buy” and a consensus target price of $401.17.

MongoDB Profile

(Get Rating)

MongoDB, Inc provides general purpose database platform worldwide. The company offers MongoDB Enterprise Advanced, a commercial database server for enterprise customers to run in the cloud, on-premise, or in a hybrid environment; MongoDB Atlas, a hosted multi-cloud database-as-a-service solution; and Community Server, a free-to-download version of its database, which includes the functionality that developers need to get started with MongoDB.

Further Reading

Want to see what other hedge funds are holding MDB? Visit HoldingsChannel.com to get the latest 13F filings and insider trades for MongoDB, Inc. (NASDAQ:MDB – Get Rating).

Receive News & Ratings for MongoDB Daily – Enter your email address below to receive a concise daily summary of the latest news and analysts’ ratings for MongoDB and related companies with MarketBeat.com’s FREE daily email newsletter.

Article originally posted on mongodb google news. Visit mongodb google news

Article originally posted on InfoQ. Visit InfoQ

Google recently announced the general availability of Rocky Linux optimized for Google Cloud. The new images are customized variants of Rocky Linux, the open-source enterprise distribution compatible with Red Hat Enterprise.

Developed in collaboration with CIQ, the support and services partner of Rocky Linux, the new images are a direct replacement for CentOS workloads. Started by Gregory Kurtzer, the founder of the CentOS project and CEO of CIQ, Rocky Linux is a downstream, binary-compatible release built using the Red Hat Enterprise Linux (RHEL) source code. The distribution was born after Red Hat decided not to provide full updates and maintenance updates for CentOS 8 as initially announced.

Google Cloud builds and supports the Rocky Linux images for Compute Engine, with both a fully open source version and one optimized for Google Cloud: this version has the suffix “-optimized-gcp” and uses the latest version of the Google virtual network interface (gVNIC). Clark Kibler, senior product manager at Google, explains:

These new images contain customized variants of the Rocky Linux kernel and modules that optimize networking performance on Compute Engine infrastructure, while retaining bug-for-bug compatibility with Community Rocky Linux and Red Hat Enterprise Linux. The high bandwidth networking enabled by these customizations will be beneficial to virtually any workload, and are especially valuable for clustered workloads such as HPC (see this page for more details on configuring a VM with high bandwidth).

A few months ago, Venkat Gattamneni, senior product manager at Google, announced the partnership with CIQ and promised more integrations with the new distribution:

In addition to CIQ-backed support for Rocky Linux, Google is also working with CIQ to provide a streamlined product experience – with plans to include performance-tuned Rocky Linux images, out-of-the-box support for specialized Google infrastructure, tools to help support easy migration, and more.

Google Cloud is not the only provider supporting Rocky Linux. AWS and Azure are other sponsors of the Rocky Linux project and offer AMI in the AWS and Azure marketplaces. Kibler adds:

Going forward, we’ll collaborate with CIQ to publish both the community and Optimized for Google Cloud editions of Rocky Linux for every major release, and both sets of images will receive the latest kernel and security updates provided by CIQ and the Rocky Linux community.

The Rocky Linux 8 AMI optimized for Google Cloud is available for all x86-based Compute Engine VM families. Versions for the new Arm-based Tau T2A and Rocky Linux 9, the latest Rocky generally available release, are expected soon. Google does not charge a license fee for using Rocky Linux with Compute Engine.

Article originally posted on InfoQ. Visit InfoQ

Recently, Microsoft and Oracle announced the general availability (GA) of Oracle Database Service for Microsoft Azure, a new service that allows Microsoft Azure customers to provision, access, and monitor enterprise-grade Oracle Database services in Oracle Cloud Infrastructure (OCI).

Microsoft and Oracle have partnered since 2019 and first delivered the Oracle Interconnect for Microsoft Azure,, allowing hundreds of organizations to use secure and private interconnections in 11 global regions. Now both companies have extended their partnership with the GA release of Oracle Database Service for Microsoft Azure, which builds upon the core capabilities of the Oracle Interconnect for Azure and enables any customer to integrate workloads more easily on Microsoft Azure with Oracle Database services on OCI.

Through the Azure Portal, customers can deploy Oracle Database running on OCI with the Oracle Database Service. The service automatically configures everything required to link the two cloud environments and federates Azure Active Directory identities, making it easy for Azure customers to use the service. Furthermore, OCI database logs and metrics are integrated with Azure Services such as Azure Application Insights and Azure Log Analytics for simpler management and monitoring Azure Application Insights and Azure Log Analytics.

Source: https://www.oracle.com/cloud/azure/

Jane Zhu, senior vice president, and chief information officer, Corporate Operations, Veritas, said in a Microsoft press release:

Oracle Database Service for Microsoft Azure has simplified the use of a multi-cloud environment for data analytics. We were able to easily ingest large volumes of data hosted by Oracle Exadata Database Service on OCI to Azure Data Factory where we are using Azure Synapse for analysis. 

In addition, Holger Mueller, principal analyst and vice president at Constellation Research Inc., told InfoQ:

It is remarkable as customers brought competitors together – and now Oracle is even better integrated into the Azure… practically making Oracle a first-grade citizen in Azure – operating the Oracle DB from an Azure console. This is how multi-cloud should be implemented – so customers win. And they must win……

Furthermore, he said: 

Tacitly it is also the admission by Microsoft that the Oracle DB is better than MS SQL Server and by Oracle that Microsoft PowerBI is better than Oracle Analytics – at least for some customers… and Larry J Ellison is right – it is all about giving customers choices.

Lastly, there are no charges for using the Oracle Database Service for Microsoft Azure, the Oracle Interconnect for Microsoft Azure, or data egress or ingress when moving data between OCI and Azure. Customers will pay only for the other Azure or Oracle services they consume, such as Azure Synapse or Oracle Autonomous Database.

Article originally posted on InfoQ. Visit InfoQ

Empathy is the first step in practicing sustainable, genuine inclusion. If persons or groups of people feel unwelcome because of the language being used in a community, its products, or documentation, then the words can be changed. Identifying divisive language can help to make changes to the words that we use.

Eliane Pereira and Josip Vilicic, both technical writers, spoke about promoting inclusion in documentation at OOP 2022.

Empathy is a conscious practice where we listen to each other and try to feel what they are feeling, Vilicic said. This allows a person to relate to someone else’s experience, even if it’s unfamiliar.

Pereira mentioned that empathy is the key to understanding how others feel in certain situations, even if the situation does not impact you. A word can be just a word for you, but the same word can impact your coworkers and make the work environment unsafe for them.

It takes empathy and willingness to make changes so that everyone feels included, as Pereira explained:

For example, in the engineering field, master/slave is a model of asymmetric communication or control where one device or process, “master”, controls one or more other devices or processes, the “slaves”. For a descendant of slaves who decides to contribute to a project, the perceived racial connotations associated with the terms, invoking slavery, is terrible.

Vilicic mentioned that the most important thing is having support from the top decision-makers in an organization in improving the language. Once there is ideological support, the difficulty of the journey is less important, because we know we have a good goal in mind: improving the language so it doesn’t harm our community, he said.

By using inclusive language, we give everyone the opportunity to be themselves, Pereira argued. We can ensure that we are not using expressions that can be punitive, or make people feel rejected or embarrassed for what they are, she said.

InfoQ interviewed Eliane Pereira and Josip Vilicic about promoting empathy and inclusion in documentation.

InfoQ: What role does empathy play when it comes to inclusion?

Josip Vilicic: If someone says that they are being illegitimately excluded from a community, and the community says this is unintentional, there is a conflict.

Conflict is not inherently bad… but we can respond to conflict in a destructive (defensive or aggressive) manner, or in a constructive (empathetic) manner. If the community actively listens, does not deny the experience that the excluded group shares, and does not want to perpetuate harm, then the only choice left is for the community to fix the inequality through inclusion.

InfoQ: What can be done to encourage and support people in changing the language?

Eliane Pereira: Speak up to show that changes are needed. Listen if you think that some changes are not needed. People are used to the harmful language being present in their daily lives to the point that, when they are asked to change, they will say, “This has been here forever, we don’t need to change it, it is just a word”.

That is why we need to explain why we need those words to be replaced, so people can be aware that those are not just words, but a way to communicate something and sometimes, this something can be derogatory to someone.

InfoQ: How can the use of inclusive language increase psychological safety?

Vilicic: Using inclusive language signals to the audience that we are moving forward in a way that is sensitive, intentional, and kind. This can make teammates feel like they are in a supportive environment, where they can speak freely and they won’t be rejected.

No matter what our professional efforts are, we’re a group of imperfect people working towards a shared goal. When we base our interactions around respecting each other’s humanity, we allow each other to collaborate towards amazing things.

Pereira: Some words have a connotation for us, but for others, can be a pain point in their lives. For example, saying you have ADHD to express you are having difficulties concentrating in your work can make a colleague who actually has attention deficit hyperactivity disorder (ADHD) to feel embarrassed or afraid that they are labelled as a worker with inability to perform their job. That is why we think that it is important to avoid metaphors in expressing yourself. Saying you are unable to concentrate on work on that day is clear enough.