Month: April 2025

Article originally posted on InfoQ. Visit InfoQ

PayPal has released its Agent Toolkit, designed to help developers integrate PayPal’s API suite with AI frameworks through the Model Context Protocol (MCP). The toolkit provides access to APIs for payments, invoices, disputes, shipment tracking, catalog management, subscriptions, and analytics capabilities.

The company is adopting MCP, a standard proposed by Anthropic that aims to standardize how agents access third-party services and data sources. PayPal’s official MCP server is now available for developers, offering remote MCP servers with authentication integration in the cloud environment. The technology will support users working across multiple devices with simplified login procedures.

The PayPal Agent Toolkit provides developers with a streamlined way to incorporate PayPal’s commerce capabilities into AI agent workflows. This library serves as an intermediary between PayPal’s API ecosystem and modern AI frameworks, enabling AI agents to handle tasks like order management, invoice generation, and subscription control without requiring developers to implement complex API integrations manually.

The toolkit offers several important capabilities, including “Easy integration with PayPal services, including functions that correspond to common actions within the payments, invoices, disputes, shipment tracking, catalog, subscriptions, reporting and insights APIs, eliminating the need to delve deep into each API endpoint.” Currently supporting TypeScript with Python support planned for future release, the toolkit works with leading AI frameworks such as Model Context Protocol servers and Vercel’s AI SDK.

The PayPal Agent Toolkit opens new avenues for businesses to integrate AI-powered workflows with financial operations. By connecting AI frameworks directly to PayPal services, developers can create specialized agents that handle various commerce-related tasks.

For Order Management and Shipment tracking, businesses can implement AI agents that create orders from conversational interactions, process payments with proper authentication, and provide shipment updates. A customer service agent could use the toolkit to complete transactions when customers confirm purchases through chat interfaces.

The toolkit also supports Intelligent Invoice Handling, allowing AI assistants to generate and manage invoices based on service completions. These agents can use natural language instructions to define invoice parameters, send them to clients via email, and monitor payment status.

With Streamlined Subscription Management capabilities, businesses can develop agents that handle the entire subscription lifecycle. This includes creating products, setting up subscription plans, and processing recurring payments through PayPal’s payment system. As described in the documentation, “a membership agent could use the toolkit to set up a recurring PayPal payment when a new user signs up for a service and approves the payment.”

The PayPal Agent Toolkit implementation requires minimal setup, as demonstrated in the code examples. Developers first initialize the PayPal workflows by importing the necessary components and configuring client credentials:

import { PayPalWorkflows, ALL_TOOLS_ENABLED } from '@paypal/agent-toolkit/ai-sdk';

const paypalWorkflows = new PayPalWorkflows({

clientId: process.env.PAYPAL_CLIENT_ID,

clientSecret: process.env.PAYPAL_CLIENT_SECRET,

configuration: {

actions: ALL_TOOLS_ENABLED,

},

});

Once configured, the toolkit can be used with any compatible language model through a simple API call structure. The code shows how developers can integrate PayPal’s functionality with an AI model:

const llm: LanguageModelV1 = getModel(); // The model to be used with ai-sdk

const { text: response } = await generateText({

model: llm,

tools: paypalToolkit.getTools(),

maxSteps: 10,

prompt: `Create an order for $50 for custom handcrafted item and get the payment link.`,

});

This integration allows AI models to execute PayPal operations through natural language instructions, such as creating orders and generating payment links, without requiring developers to write extensive custom code for API integrations.

David Paluy, CTO at Suppli, raised important questions about identity and authentication in agentic commerce:

Financial systems rely on identifying who is making a transaction. An AI agent has no legal identity of its own – it operates under a user’s or organization’s identity.

Paluy suggested that the industry may need to extend the concept of Know-Your-Customer to “Know-Your-Agent” – verifying an agent’s identity and authorization as an intermediary acting for a user.

Abdul Abdirahman, a principal at F-Prime, highlighted existing challenges in API infrastructure:

Today’s APIs are designed for human developers to engage with and thus not optimized for the agentic world. Many modifications are needed to enable agents to execute complex tasks efficiently.

The announcement also triggered reactions on social media. Kenneth Auchenberg, Partner at AlleyCorp, expressed surprise at PayPal’s position in the market, stating:

Wait, Paypal shipped a remote MCP server, before Stripe?

Developers interested in exploring the PayPal Agent Toolkit can access the official repository at https://github.com/paypal/agent-toolkit/ for documentation, examples, and implementation guides. The repository contains detailed information on getting started with the toolkit, supported features, and best practices for integrating PayPal’s payment capabilities into AI agent workflows.

Article originally posted on InfoQ. Visit InfoQ

With the release of the last Android 16 beta, developers should ensure their apps or libraries are free of any compatibility issues. Google warns of changes—including JobScheduler quotas, stronger intent security, 16KB page size—that might affect apps even if they do not specifically target Android 16.

The JobScheduler in Android 16 will enforce runtime quotas based on several factors, including the app’s standby bucket—suche as active, working, frequent, rare, and restricted— whether a background job was started while the app was active, or whether a job executes concurrently with a foreground service. When a job runs out of its quota, it will be blocked.

An important, and potentially breaking, change is the update to the Android Runtime (ART), which affects apps that use reflections or JNI to access Android internals. Google warns that relying on internal ART structures, such as non-SDK interfaces, is risky, as ART updates are delivered via Google Play and are decoupled from the device’s platform version.

If an app uses intents, it must account for Android 16’s new protections against redirection attacks, which occur when an attacker hijack an intent to trigger a different component. These attacks can exploit serialized intents passed via the extra field or when intents are marshaled into strings. For instance, a malicious app might pass a null value to getCallingActivity() hoping that a vulnerable app will not validate it. Likewise, ignoring the return code from checkCallingPermission() is a common mistake leading to potential risks.

Android 16 introduces a by-default security hardening solution to Intent redirection exploits. In most cases, apps that use intents normally won’t experience any compatibility issues.

The removeLaunchSecurityProtection method allows apps to opt out of the new protections, Google says. However, developers should thoroughly test their intent handling and opt out only when absolutely necessary.

Android 15 introduced 16 KB page size as a performance optimization, improving app launch times on systems under memory pressure, reducing power consumption during app launch, and shortening system boot time. In Android 16, while 4 KB-aligned apps will work in compatibility mode, the user will be displayed a potentially-annoying warning dialog. To suppress this dialog, developers can set the android:pageSizeCompat property in the AndroidManifest.xml.

Additional Android 16 changes potentially affecting existing apps include the removal of the option to opt out of edge-to-edge mode, a new predictive-back behavior, and optimizations to fixed-rate scheduling. On large-screen devices, Android 16 also fully enforces orientation, resizability, and aspect ratio settings.

This is just a glimpse of what developers should take into account in the upcoming release of Android. Refer to the official documentation for the full picture.

Posted on mongodb google news. Visit mongodb google news

At the recent Google Cloud Next 2025, Google Cloud announced the preview of Firestore with MongoDB compatibility, introducing support for the MongoDB API and query language. This capability allows users to store and query semi-structured JSON data within Google Cloud’s real-time document database.

Firestore with MongoDB compatibility is backed by a serverless infrastructure offering single-digit-millisecond read performance, automatic scaling, and high availability. Minh Nguyen, senior product manager at Google Cloud, and Patrick Costello, engineering manager at Google Cloud, stated:

“Firestore developers can now take advantage of MongoDB’s API portability along with Firestore’s differentiated serverless service, to enjoy multi-region replication with strong consistency, virtually unlimited scalability, industry-leading high availability of up to 99.999% SLA, and single-digit milliseconds read performance.”

The backend of Firestore automatically replicates data across availability zones and regions, ensuring no downtime or data loss. Future developments will include data interoperability between Firestore’s MongoDB compatible interface and Firestore’s real-time and offline SDKs.

.ai-rotate {position: relative;}
.ai-rotate-hidden {visibility: hidden;}
.ai-rotate-hidden-2 {position: absolute; top: 0; left: 0; width: 100%; height: 100%;}
.ai-list-data, .ai-ip-data, .ai-filter-check, .ai-fallback, .ai-list-block, .ai-list-block-ip, .ai-list-block-filter {visibility: hidden; position: absolute; width: 50%; height: 1px; top: -1000px; z-index: -9999; margin: 0px!important;}
.ai-list-data, .ai-ip-data, .ai-filter-check, .ai-fallback {min-width: 1px;}

Details about supported query and projection operators and features by MongoDB API version are available, along with limitations and behavior differences. Text search operators are currently unsupported.

For more information, explore the following links:

---

MongoDB announced several updates at Google Cloud Next ’25, emphasizing their collaboration with Google Cloud.

MongoDB Atlas has expanded availability to Google Cloud regions in Mexico and South Africa. The company was recognized as the 2025 Google Cloud Partner of the Year for Data & Analytics – Marketplace, marking MongoDB’s sixth consecutive year as a partner of the year.

MongoDB is enhancing developer productivity through integrations with Google Cloud’s Gemini Code Assist. This tool allows developers to access MongoDB documentation and code snippets directly within their Integrated Development Environments (IDEs).

Additionally, MongoDB is now integrated with Project IDX, which helps developers set up MongoDB environments quickly. Developers can also easily integrate MongoDB Atlas with Firebase, using a new Firebase extension for MongoDB Atlas for real-time synchronization.

For more details, visit:

---

Google Cloud introduced numerous database enhancements at its Next 2025 conference, including new AI features in AlloyDB and a MongoDB-compliant API for Firestore. AlloyDB has incorporated the open-source pgvector extension, allowing storage and querying of vector embeddings.

In April 2024, Google Cloud added the Scalable Nearest Neighbor (ScaNN) algorithm to AlloyDB, significantly enhancing performance metrics. This was highlighted by Andi Gutmans, VP & GM for databases at Google:

“We’re seeing thousands and thousands of customers doing vector processing. Target went into production with AlloyDB for their online retail search and they have a 20% better hit rate on recommendations. That’s real revenue.”

For more on this, check:

---

Google Cloud Migration Center simplifies the transition from on-premises servers to Google Cloud, which significantly enhances performance and reduces operational costs. The integration of MongoDB cluster assessment into the Migration Center allows for deeper insights into MongoDB deployments.

Using Migration Center provides significant advantages, including:

• Automated discovery and inventory of MongoDB clusters.
• Enhanced understanding of configuration and resource utilization.
• A unified platform for asset discovery and migration tools.

For further insights, see:


---

MongoDB Atlas now supports native JSON for BigQuery, simplifying data transformations and reducing operational costs. This integration allows businesses to analyze data with better flexibility and efficiency.

MongoDB also introduced support for Data Federation and Online Archive, enabling users to manage and archive cold data seamlessly.

Discover more at:

---

For a secure and smooth login experience, explore passwordless authentication solutions at mojoauth. Quickly integrate passwordless authentication for web and mobile applications to enhance user experience and security. Contact us today to learn more about our services!

*** This is a Security Bloggers Network syndicated blog from MojoAuth – Go Passwordless authored by Dev Kumar. Read the original post at: https://mojoauth.com/blog/google-cloud-enhances-databases-with-firestore-and-mongodb-features/

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

Article originally posted on InfoQ. Visit InfoQ

There was a flurry of activity in the Spring ecosystem during the week of April 21st, 2025, highlighting first release candidates of Spring Boot, Spring Data 2025.0.0, Spring Security, Spring Authorization Server, Spring Session, Spring Integration, Spring Modulith and Spring Web Services. There were also second milestone releases of Spring Data 2025.1.0 and Spring for Apache Kafka and a first milestone release of Spring Vault.

Spring Boot

The first release candidate of Spring Boot 3.5.0 delivers bug fixes, improvements in documentation, dependency upgrades and new features such as: new annotations, @ServletRegistration and @FilterRegistration, as an annotation-based alternative to registering servlet and filter beans using the ServletRegistrationBean and FilterRegistrationBean classes; and new classes that support Docker credential stores and helpers. More details on this release may be found in the release notes.

The release of Spring Boot 3.4.5 and 3.3.11 (announced here and here, respectively) provide bug fixes, improvements in documentation and dependency upgrades. More importantly, the Spring Boot team has disclosed that these two releases, along with versions 3.2.14, 3.1.16 and 2.7.25, address CVE-2025-22235, a vulnerability in which the overloaded to() method, defined in the EndpointRequest class creates an incorrect null/** matcher, under certain conditions, if the actuator endpoint is not exposed. Further details on these releases may be found in the release notes for version 3.4.5 and version 3.3.11.

Spring Data

The first release candidate of Spring Data 2025.0.0 features: refinements to the Hibernate Query Language (HQL), Elastic Query Language (EQL) and Jakarta Persistence Query Language (JPQL) to resolve various query issues; and new deprecation warnings for intended breaking changes, such as the removal of support for JMX, planned for Spring Data 4.0. This version aligns with Spring Boot 3.5.0-RC1 and the Spring Data team plans a GA release in May 2025.

The second milestone release of Spring Data 2025.1.0 ships with support for JSpecify on sub-projects: Spring Data Commons, Spring Data JPA, Spring Data MongoDB, Spring Data LDAP, Spring Data Cassandra, Spring Data KeyValue, and Spring Data Elasticsearch. There was also a breaking change with a significant rewrite of the QueryEnhancer interface such that configuration via the the spring.data.jpa.query.native.parser property is no longer available. Configuration is now possible via the @EnableJpaRepositories annotation. More details on this release may be found in the release notes.

Spring Security

The first release candidate of Spring Security 6.5.0 delivers bug fixes, dependency upgrades and new features such as: refinements to the implementation of the OAuth 2.0 Demonstrating Proof of Possession (DPoP) specification that include a new AuthenticationEntryPoint interface that returns the WWW-Authenticate header upon failure of a DPoP authentication; and refinements to the PathPatternRequestMatcher class to use a servlet in the path pattern instead of implementing the RequestMatcher interface for the servlet. Further details on this release may be found in the release notes and what’s new guide.

The release of Spring Security 6.4.5 and 6.3.9 (announced here and here, respectively) provide bug fixes, improvements in documentation and dependency upgrades. More importantly, the Spring Security team has disclosed that these two releases, along with versions 6.2.11, 6.1.15, 6.0.17, 5.8.19 and 5.7.17, address CVE-2025-22234, a follow up to CVE-2025-22228, whee the the timing attack mitigation, implemented in DaoAuthenticationProvider class, had been inadvertently broken. More details on these releases may be found in the release notes for version 6.4.5 and version 6.3.9.

Spring Authorization Server

The first release candidate of Spring Authorization Server 1.5.0 provides dependency upgrades and new features such as: the addition of authorization server metadata for the OAuth 2.0 DPoP and Pushed Authorization Requests (PAR) specifications; and a new REQUEST_URI constant, defined in the Spring Security OAuth2ParameterNames class, to facilitate flow in PAR. Further details on this release may be found in the release notes.

Spring Session

The first release candidate of Spring Session 3.5.0 ships with bug fixes, dependency upgrades and new features: a new CompositeHttpSessionIdResolver class, an implementation of the HttpSessionIdResolver interface, that iterates over a given collection of delegate instances of the HttpSessionIdResolver; and an optimization of the JdbcIndexedSessionRepository class to only start JDBC transactions only when there are session updates with a JDBC-based repository. More details on this release may be found in the release notes.

Spring Integration

The first release candidate of Spring Integration 6.5.0 provides bug fixes, improvements in documentation, dependency upgrades and new features such as: discontinued use of the logger.error() method in the TcpSendingMessageHandler class that was deemed unnecessary; and a new LockRequestHandlerAdvice class, based on the LockRegistry interface, that maintains mutual access to underlying services. Further details on this release may be found in the release notes.

Spring Modulith

The first release candidate of Spring Modulith 1.4.0 delivers bug fixes, dependency upgrades and improvements such as: performance improvements in use of the DefaultEventPublicationRegistry class and the publishEvent() method defined in the Spring Framework AbstractApplicationContext class; and state change detection for instances of the Scenario class should only accept non-empty collections by default. More details on this release may be found in the release notes.

Spring for Apache Kafka

The second milestone release of Spring for Apache Kafka 4.0.0 provides bug fixes, improvements in documentation, dependency upgrades and new features such as: client dependency upgrades to Apache Kafka 4.0.0; and an optimization in the MessagingMessageListenerAdapter class that now returns null from the invoke() method, defined in the DelegatingInvocableHandler class, that avoids an unnecessary instance return of the InvocationResult class. Further details on this release may be found in the release notes.

Spring Web Services

The first release candidate of Spring Web Services 4.1.0 ships with bug fixes, improvements in documentation, dependency upgrades and new features such as: support for configuring arbitrary options for Apache Web Services Security for Java (WSS4J) via the Wss4jSecurityInterceptor class; and the ability to create custom implementations of the MethodArgumentResolver and MethodReturnValueHandler interfaces. More details on this release may be found in the release notes.

Spring Vault

The first milestone release of Spring Vault 3.2.0 available delivers bug fixes, improvements in documentation, dependency upgrades and new features such as: support for Instance Metadata Service Version 2 (IMDSv2) on AWS EC2; and the ability to use the Github token authentication mechanism. Further details on this release may be found in the release notes.

Posted on mongodb google news. Visit mongodb google news

Voya Investment Management LLC reduced its position in shares of MongoDB, Inc. (NASDAQ:MDB – Free Report) by 96.4% in the fourth quarter, according to the company in its most recent disclosure with the Securities and Exchange Commission. The firm owned 474,019 shares of the company’s stock after selling 12,794,369 shares during the period. Voya Investment Management LLC owned 0.64% of MongoDB worth $110,356,000 as of its most recent SEC filing.

Several other large investors also recently modified their holdings of MDB. B.O.S.S. Retirement Advisors LLC bought a new position in MongoDB in the fourth quarter worth about $606,000. Union Bancaire Privee UBP SA bought a new position in shares of MongoDB in the 4th quarter worth approximately $3,515,000. HighTower Advisors LLC raised its position in shares of MongoDB by 2.0% in the 4th quarter. HighTower Advisors LLC now owns 18,773 shares of the company’s stock worth $4,371,000 after acquiring an additional 372 shares in the last quarter. Nisa Investment Advisors LLC lifted its stake in shares of MongoDB by 428.0% in the 4th quarter. Nisa Investment Advisors LLC now owns 5,755 shares of the company’s stock valued at $1,340,000 after purchasing an additional 4,665 shares during the period. Finally, Covea Finance bought a new stake in shares of MongoDB during the fourth quarter valued at approximately $3,841,000. 89.29% of the stock is owned by institutional investors.

Insider Activity at MongoDB

In other MongoDB news, CEO Dev Ittycheria sold 8,335 shares of the business’s stock in a transaction on Tuesday, January 28th. The shares were sold at an average price of $279.99, for a total value of $2,333,716.65. Following the sale, the chief executive officer now owns 217,294 shares in the company, valued at $60,840,147.06. The trade was a 3.69 % decrease in their position. The sale was disclosed in a document filed with the Securities & Exchange Commission, which is available through the SEC website. Also, Director Dwight A. Merriman sold 3,000 shares of MongoDB stock in a transaction dated Monday, February 3rd. The stock was sold at an average price of $266.00, for a total value of $798,000.00. Following the completion of the sale, the director now directly owns 1,113,006 shares in the company, valued at $296,059,596. This trade represents a 0.27 % decrease in their ownership of the stock. The disclosure for this sale can be found here. In the last 90 days, insiders have sold 47,680 shares of company stock valued at $10,819,027. 3.60% of the stock is owned by company insiders.

Wall Street Analyst Weigh In

Several equities analysts have commented on the company. Robert W. Baird lowered their price objective on MongoDB from $390.00 to $300.00 and set an “outperform” rating for the company in a research report on Thursday, March 6th. The Goldman Sachs Group cut their price objective on shares of MongoDB from $390.00 to $335.00 and set a “buy” rating on the stock in a report on Thursday, March 6th. Piper Sandler lowered their target price on shares of MongoDB from $280.00 to $200.00 and set an “overweight” rating for the company in a report on Wednesday. Needham & Company LLC reduced their price objective on MongoDB from $415.00 to $270.00 and set a “buy” rating for the company in a research report on Thursday, March 6th. Finally, China Renaissance initiated coverage on MongoDB in a report on Tuesday, January 21st. They issued a “buy” rating and a $351.00 target price on the stock. Eight analysts have rated the stock with a hold rating, twenty-four have assigned a buy rating and one has assigned a strong buy rating to the stock. Based on data from MarketBeat.com, MongoDB presently has a consensus rating of “Moderate Buy” and an average target price of $294.78.

Check Out Our Latest Stock Analysis on MDB

MongoDB Stock Performance

Shares of MDB traded up $0.29 during mid-day trading on Friday, reaching $173.50. The stock had a trading volume of 2,105,392 shares, compared to its average volume of 1,841,392. The firm has a market cap of $14.09 billion, a price-to-earnings ratio of -63.32 and a beta of 1.49. MongoDB, Inc. has a 12 month low of $140.78 and a 12 month high of $387.19. The business has a fifty day moving average of $195.15 and a 200 day moving average of $248.95.

MongoDB (NASDAQ:MDB – Get Free Report) last issued its quarterly earnings results on Wednesday, March 5th. The company reported $0.19 earnings per share (EPS) for the quarter, missing analysts’ consensus estimates of $0.64 by ($0.45). The business had revenue of $548.40 million during the quarter, compared to analysts’ expectations of $519.65 million. MongoDB had a negative return on equity of 12.22% and a negative net margin of 10.46%. During the same quarter in the previous year, the company posted $0.86 EPS. On average, research analysts forecast that MongoDB, Inc. will post -1.78 EPS for the current fiscal year.

About MongoDB

(Free Report)

MongoDB, Inc, together with its subsidiaries, provides general purpose database platform worldwide. The company provides MongoDB Atlas, a hosted multi-cloud database-as-a-service solution; MongoDB Enterprise Advanced, a commercial database server for enterprise customers to run in the cloud, on-premises, or in a hybrid environment; 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

Before you consider MongoDB, you’ll want to hear this.

MarketBeat keeps track of Wall Street’s top-rated and best performing research analysts and the stocks they recommend to their clients on a daily basis. MarketBeat has identified the five stocks that top analysts are quietly whispering to their clients to buy now before the broader market catches on… and MongoDB wasn’t on the list.

While MongoDB currently has a Moderate Buy rating among analysts, top-rated analysts believe these five stocks are better buys.

View The Five Stocks Here

Discover the top 7 AI stocks to invest in right now. This exclusive report highlights the companies leading the AI revolution and shaping the future of technology in 2025.

Get This Free Report

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

Posted on mongodb google news. Visit mongodb google news

Stifel Financial Corp grew its position in shares of MongoDB, Inc. (NASDAQ:MDB – Free Report) by 6.4% in the 4th quarter, according to the company in its most recent filing with the Securities and Exchange Commission (SEC). The institutional investor owned 114,216 shares of the company’s stock after purchasing an additional 6,894 shares during the quarter. Stifel Financial Corp owned approximately 0.15% of MongoDB worth $26,590,000 as of its most recent SEC filing.

A number of other large investors also recently bought and sold shares of the business. TD Waterhouse Canada Inc. raised its position in shares of MongoDB by 7.2% during the 4th quarter. TD Waterhouse Canada Inc. now owns 1,557 shares of the company’s stock valued at $362,000 after buying an additional 105 shares during the period. Tower Research Capital LLC TRC boosted its stake in shares of MongoDB by 554.0% in the 4th quarter. Tower Research Capital LLC TRC now owns 8,077 shares of the company’s stock valued at $1,880,000 after buying an additional 6,842 shares during the period. Teachers Retirement System of The State of Kentucky grew its holdings in MongoDB by 138.1% during the 4th quarter. Teachers Retirement System of The State of Kentucky now owns 51,432 shares of the company’s stock worth $11,974,000 after acquiring an additional 29,832 shares in the last quarter. Transatlantique Private Wealth LLC increased its holdings in MongoDB by 15.5% in the fourth quarter. Transatlantique Private Wealth LLC now owns 3,273 shares of the company’s stock valued at $762,000 after buying an additional 440 shares during the last quarter. Finally, Thematics Asset Management boosted its holdings in MongoDB by 49.9% in the fourth quarter. Thematics Asset Management now owns 132,313 shares of the company’s stock valued at $30,804,000 after purchasing an additional 44,061 shares in the last quarter. Institutional investors and hedge funds own 89.29% of the company’s stock.

Wall Street Analysts Forecast Growth

MDB has been the topic of several recent research reports. Daiwa America upgraded MongoDB to a “strong-buy” rating in a research report on Tuesday, April 1st. Barclays cut their price objective on shares of MongoDB from $330.00 to $280.00 and set an “overweight” rating for the company in a research report on Thursday, March 6th. Daiwa Capital Markets began coverage on shares of MongoDB in a report on Tuesday, April 1st. They issued an “outperform” rating and a $202.00 target price on the stock. Stifel Nicolaus dropped their price target on shares of MongoDB from $340.00 to $275.00 and set a “buy” rating on the stock in a research note on Friday, April 11th. Finally, Scotiabank restated a “sector perform” rating and issued a $160.00 price objective (down previously from $240.00) on shares of MongoDB in a research report on Friday. Eight investment analysts have rated the stock with a hold rating, twenty-four have given a buy rating and one has assigned a strong buy rating to the company’s stock. According to data from MarketBeat, the stock currently has an average rating of “Moderate Buy” and an average price target of $294.78.

Read Our Latest Research Report on MongoDB

MongoDB Stock Performance

MongoDB stock traded up $0.29 during midday trading on Friday, reaching $173.50. 2,105,392 shares of the company were exchanged, compared to its average volume of 1,841,392. The company has a market capitalization of $14.09 billion, a price-to-earnings ratio of -63.32 and a beta of 1.49. The firm’s 50-day simple moving average is $195.15 and its 200-day simple moving average is $248.95. MongoDB, Inc. has a 1 year low of $140.78 and a 1 year high of $387.19.

MongoDB (NASDAQ:MDB – Get Free Report) last announced its quarterly earnings data on Wednesday, March 5th. The company reported $0.19 earnings per share (EPS) for the quarter, missing the consensus estimate of $0.64 by ($0.45). The firm had revenue of $548.40 million for the quarter, compared to analysts’ expectations of $519.65 million. MongoDB had a negative net margin of 10.46% and a negative return on equity of 12.22%. During the same period in the previous year, the company posted $0.86 EPS. On average, analysts forecast that MongoDB, Inc. will post -1.78 EPS for the current fiscal year.

Insider Activity

In other MongoDB news, CAO Thomas Bull sold 301 shares of MongoDB stock in a transaction on Wednesday, April 2nd. The shares were sold at an average price of $173.25, for a total value of $52,148.25. Following the transaction, the chief accounting officer now owns 14,598 shares in the company, valued at $2,529,103.50. This trade represents a 2.02 % decrease in their position. The sale was disclosed in a document filed with the Securities & Exchange Commission, which is available through this link. Also, CFO Srdjan Tanjga sold 525 shares of the business’s stock in a transaction on Wednesday, April 2nd. The shares were sold at an average price of $173.26, for a total transaction of $90,961.50. Following the sale, the chief financial officer now directly owns 6,406 shares of the company’s stock, valued at $1,109,903.56. This represents a 7.57 % decrease in their ownership of the stock. The disclosure for this sale can be found here. Insiders sold a total of 47,680 shares of company stock valued at $10,819,027 over the last quarter. Company insiders own 3.60% of the company’s stock.

MongoDB Company Profile

(Free Report)

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

Read More

Before you consider MongoDB, you’ll want to hear this.

MarketBeat keeps track of Wall Street’s top-rated and best performing research analysts and the stocks they recommend to their clients on a daily basis. MarketBeat has identified the five stocks that top analysts are quietly whispering to their clients to buy now before the broader market catches on… and MongoDB wasn’t on the list.

While MongoDB currently has a Moderate Buy rating among analysts, top-rated analysts believe these five stocks are better buys.

View The Five Stocks Here

Discover the top 7 AI stocks to invest in right now. This exclusive report highlights the companies leading the AI revolution and shaping the future of technology in 2025.

Get This Free Report

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

Posted on mongodb google news. Visit mongodb google news

Scotiabank has adjusted its outlook for MongoDB (MDB, Financial), decreasing the price target from $240 to $160. Despite recognizing several strengths within MongoDB’s business model, analyst Patrick Colville maintains a Sector Perform rating for the company. This cautious stance suggests that the firm advises a prudent approach and does not recommend investors to quickly increase their positions in MongoDB at this time.

Wall Street Analysts Forecast

Based on the one-year price targets offered by 34 analysts, the average target price for MongoDB Inc (MDB, Financial) is $278.18 with a high estimate of $520.00 and a low estimate of $160.00. The average target implies an
upside of 64.47%
from the current price of $169.14. More detailed estimate data can be found on the MongoDB Inc (MDB) Forecast page.

Based on the consensus recommendation from 38 brokerage firms, MongoDB Inc’s (MDB, Financial) average brokerage recommendation is currently 2.0, indicating “Outperform” status. The rating scale ranges from 1 to 5, where 1 signifies Strong Buy, and 5 denotes Sell.

Based on GuruFocus estimates, the estimated GF Value for MongoDB Inc (MDB, Financial) in one year is $432.68, suggesting a
upside
of 155.81% from the current price of $169.14. GF Value is GuruFocus’ estimate of the fair value that the stock should be traded at. It is calculated based on the historical multiples the stock has traded at previously, as well as past business growth and the future estimates of the business’ performance. More detailed data can be found on the MongoDB Inc (MDB) Summary page.

MDB Key Business Developments

Release Date: March 05, 2025

• Total Revenue: $548.4 million, a 20% year-over-year increase.
• Atlas Revenue: Grew 24% year-over-year, representing 71% of total revenue.
• Non-GAAP Operating Income: $112.5 million, with a 21% operating margin.
• Net Income: $108.4 million or $1.28 per share.
• Customer Count: Over 54,500 customers, with over 7,500 direct sales customers.
• Gross Margin: 75%, down from 77% in the previous year.
• Free Cash Flow: $22.9 million for the quarter.
• Cash and Cash Equivalents: $2.3 billion, with a debt-free balance sheet.
• Fiscal Year 2026 Revenue Guidance: $2.24 billion to $2.28 billion.
• Fiscal Year 2026 Non-GAAP Operating Income Guidance: $210 million to $230 million.
• Fiscal Year 2026 Non-GAAP Net Income Per Share Guidance: $2.44 to $2.62.

For the complete transcript of the earnings call, please refer to the full earnings call transcript.

Positive Points

• MongoDB Inc (MDB, Financial) reported a 20% year-over-year revenue increase, surpassing the high end of their guidance.
• Atlas revenue grew 24% year over year, now representing 71% of total revenue.
• The company achieved a non-GAAP operating income of $112.5 million, resulting in a 21% non-GAAP operating margin.
• MongoDB Inc (MDB) ended the quarter with over 54,500 customers, indicating strong customer growth.
• The company is optimistic about the long-term opportunity in AI, particularly with the acquisition of Voyage AI to enhance AI application trustworthiness.

Negative Points

• Non-Atlas business is expected to be a headwind in fiscal ’26 due to fewer multi-year deals and a shift of workloads to Atlas.
• Operating margin guidance for fiscal ’26 is lower at 10%, down from 15% in fiscal ’25, due to reduced multi-year license revenue and increased R&D investments.
• The company anticipates a high-single-digit decline in non-Atlas subscription revenue for the year.
• MongoDB Inc (MDB) expects only modest incremental revenue growth from AI in fiscal ’26 as enterprises are still developing AI skills.
• The company faces challenges in modernizing legacy applications, which is a complex and resource-intensive process.

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

Article originally posted on InfoQ. Visit InfoQ

Activision has cut build times for Call of Duty: Modern Warfare II (COD) in half by profiling and optimizing their C++ build system with MSVC Build Insights to uncover bottlenecks in their compilation pipeline.

The effort unblocked developers, accelerated delivery, and reduced idle time. Their success reflects a broader trend across the industry, with teams at Netflix, Canva, and Honeycomb investing in CI performance engineering as a way to improve both productivity and developer experience.

Activision observed that persistent build delays were eroding developer flow and limiting delivery velocity. In response, the Activision team collaborated with Microsoft’s Xbox Advanced Technology Group to instrument and streamline their compilation pipeline. By using MSVC (Microsoft Visual C++) Build Insights, a profiling tool for C++ builds, engineers identified a number of key inefficiencies in their build process. While these specific issues are rooted in C++, they reflect familiar challenges faced when working with large codebases and compute heavy builds.

Among the core inefficiencies, excessive inlining was inflating compile units, link-time optimizations were dragging due to complex initializations, and inefficient symbol resolution was creating CPU stalls during the final linking stage. Each issue contributed to delay in a different part of the process, and together they highlighted how localized inefficiencies – when multiplied across a large codebase – significantly extended build time.

These targeted optimizations led to a substantial reduction in build times – from approximately 28 minutes to 14 minutes. This improvement had significant implications for Activision’s development workflow. Faster builds meant more pull requests merged, more builds, less idle time and ultimately more frequent feature delivery.

But reducing build time isn’t just a technical improvement – it has measurable effects on the developer experience. Michael Vance, SVP and software engineer at Activision, noted that “slow builds create bottlenecks in our continuous integration pipelines, delaying the verification of every piece of code and content that goes into our games.” The team’s build time improvements were not just a performance win, but a way to unblock developers and maintain velocity in a tightly integrated workflow.

This aligns with broader industry findings that highlight developer experience as a key contributor to engineering throughput. Research from GitHub and Microsoft suggests that satisfaction with internal tooling, including CI/CD pipelines, correlates strongly with productivity metrics such as PR cycle time, deployment frequency, and time to resolve issues.

Activision’s experience is indicative of a broader shift in how organizations approach CI performance. As build and test pipelines grow in complexity, teams are applying similar discipline to their profiling and instrumentation as they are with the build artifacts. Netflix reported faster iteration cycles and improved efficiency for Android developers after tuning their Gradle builds. Canva reduced CI durations from over 80 minutes to under 30, improving release velocity and reducing developer frustration. Honeycomb set internal objectives to keep build times under 15 minutes, framing CI speed as a first-class developer productivity metric. In each case, pipeline performance improvements were directly tied to happier, more effective engineering teams.

Article originally posted on InfoQ. Visit InfoQ

Microsoft has announced experimental support for .slnx files in the .NET CLI v9.0.200, unifying the developer experience among the .NET tooling. This new feature aims to remove clutter in the solution file and to reduce friction when working with large solutions.

Traditionally, .sln files have been the standard for Visual Studio solutions, but they come with limitations such as manual maintenance of project references and path dependencies, difficult merging of source code changes, and overall verbosity, as can be seen in this example:

Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio Version 17
VisualStudioVersion = 17.9.34511.98
MinimumVisualStudioVersion = 10.0.40219.1
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "DotNetMonitorWebApp", "DotNetMonitorWebAppDotNetMonitorWebApp.csproj", "{1385B389-B20C-4D19-8FE0-85629BC41343}"
EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Debug|Any CPU = Debug|Any CPU
Release|Any CPU = Release|Any CPU
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
{1385B389-B20C-4D19-8FE0-85629BC41343}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{1385B389-B20C-4D19-8FE0-85629BC41343}.Debug|Any CPU.Build.0 = Debug|Any CPU
{1385B389-B20C-4D19-8FE0-85629BC41343}.Release|Any CPU.ActiveCfg = Release|Any CPU
{1385B389-B20C-4D19-8FE0-85629BC41343}.Release|Any CPU.Build.0 = Release|Any CPU
EndGlobalSection
GlobalSection(SolutionProperties) = preSolution
HideSolutionNode = FALSE
EndGlobalSection
GlobalSection(ExtensibilityGlobals) = postSolution
SolutionGuid = {C12E911E-FAA3-4ACE-B6BF-C3605E866483}
EndGlobalSection
EndGlobal

The new .slnx format, based on XML and introduced in 2024, provides a more robust and flexible alternative, similar to project files in Visual Studio. It has a minimal footprint, removing the duplication of information already present in the project files. It uses a human-readable format that reduces the chances of accidental errors when manually editing the solution file.

MSBuild already fully supports the .slnx format since version 17.13. The experimental support for .NET CLI in version 9.0.200 allows developers to use .slnx files directly with dotnet commands (e.g., dotnet build, dotnet test). Visual Studio support for the new format might require developers enabling the ‘Use Solution File Persistence Model‘ option listed under Environment / Preview Features.

A new dotnet command called migrate helps developers convert their .sln files into .slnx files. Alternatively, from Visual Studio developers can right-click the solution node in the Solution Explorer and save the solution in the new format (if enabled in the preview options). The official recommendation is to keep either .sln or .slnx file, but not both of them in the solution folder.

The .slnx file format is still officially in preview, with Microsoft encouraging developers to try the new format in their workflows and sharing their feedback with the appropriate tooling team owners. The stated goal is to make the new format the default in both Visual Studio and the .NET CLI tool. According to Microsoft, the new format will also work with legacy .NET Framework solutions.

Microsoft has also released a library called Microsoft.VisualStuidio.SolutionPersistence that allows programmatic access to both .sln and .slnx file operations. This allows third-party tools to leverage the new solution format without having to create a parser for it.

The comments by the developer community are mixed. Some praise the new format for simplicity and straightforward migration. Other developers think that new features such as globbing (dynamic project discovery inside a folder tree) should be added to the new format.

Article originally posted on InfoQ. Visit InfoQ

Microsoft has announced the Public Preview of the open-source Azure MCP Server, a new tool designed to enhance the capabilities of AI agents by providing access to Azure resources. The Azure MCP Server allows AI agents to interact with Azure services such as file storage, databases, and logs, and execute CLI commands.

Model Context Protocol (MCP) is an open protocol that standardizes the interaction between AI agents and external resources. The Azure MCP Server implements this protocol, exposing Azure services to AI systems. According to Microsoft, this enables developers to build context-aware agents for their Azure resources. For instance, agents can now query Azure Cosmos DB using natural language, access Azure Storage files, and analyze Azure Log Analytics logs.

The Public Preview of the Azure MCP Server includes support for the following Azure services and tools:

• Azure Cosmos DB (NoSQL): List accounts, databases, containers, and items; execute SQL queries.
• Azure Storage: List accounts and blob containers/blobs; manage blob containers and blobs; list and query tables; get container properties and metadata.
• Azure Monitor (Log Analytics): List workspaces and tables; query logs using Kusto Query Language (KQL); configure monitoring.
• Azure App Configuration: List stores; manage key-value pairs and labeled configurations; lock/unlock settings.
• Azure Resource Groups: List and manage resource groups.
• Azure CLI: Execute commands directly, with full functionality and JSON output.
• Azure Developer CLI (azd): Execute commands directly, supporting template discovery, initialization, provisioning, and deployment.

(Source: Medium blog post)

Brian Veldman concluded in a Medium blog post on the Azure MCP Server:

From now on, I can use the Azure MCP Server to interact with the Azure services within my subscription. This is especially helpful in troubleshooting scenarios, such as analyzing logs.

Microsoft states that this functionality allows agents to operate on Azure services, manage cloud resources, and deploy applications. Yet, more open-source projects, such as the Azure CLI MCP Server, are available on GitHub, leveraging the MCP Server for Azure resources. Julion Dubois, a principal manager, Java Developer Relations, tweets on the mentions the Azure CLI MCP Server:

It’s an MCP server that wraps the Azure CLI, so your LLM can directly send commands to Azure.

In addition, Madni Aghadi states on  via tweet on X:

“MCP is just hype” That’s what I thought until I saw 1000+ MCP servers built since its launch.

Any agent that supports the MCP client pattern, including GitHub Copilot Agent Mode and custom MCP clients, can use the Azure MCP Server.

• GitHub Copilot Agent Mode: The Azure MCP Server can be installed with GitHub Copilot in VS Code. Microsoft recommends combining the Azure MCP Server with the GitHub Copilot for Azure extension for an enhanced development experience.
• Custom MCP Clients/Agents: Agents must adopt the MCP client pattern to interact with the Azure MCP Server. Frameworks like Semantic Kernel can be used to build such agents. Microsoft provides a command (npx -y @azure/mcp@latest server start) to install and execute the server, and notes that the Azure MCP Server should work with any MCP client.

The Azure MCP Server follows similar moves by other cloud providers to enhance AI agent capabilities within their ecosystems:

Lastly, Microsoft plans to enhance the Azure MCP Server with more agent samples, documentation, Microsoft products, Azure service integrations, and additional features.