Skip to content

Richard

My feedback

2 results found

  1. 155 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Richard commented  · 

    Ahmed, that's awesome! I've been toying with the idea of creating an open-source project for this very reason, but the time and effort required are beyond what I can commit right now. Is your emulation suite available publicly? Still, it honestly feels like this is something Atlas should be jumping on. It's not just a developer convenience—it's a feature that could drive more adoption and even serve as a selling point for converstion to their services.

    An error occurred while saving the comment
    Richard commented  · 

    Totally agree, an emulator for all aspects of App Services is crucial for every development aspect. It's not just about features; it's about business agility and cost-effectiveness. We already have local deployments for MongoDB; extending this capability to App Services would be a game-changer. Even if the emulator doesn't cover all features and uses mocks instead, this could drastically reduce development time, enhance reliability, and streamline our CI/CD pipelines. These advantages would not only lower operational costs but also serve as a strong incentive for teams who are considering adopting App Services and Atlas. This isn't just a nice-to-have; it's a strategic move that could make Atlas an even more attractive choice for development teams.

    Richard supported this idea  · 
  2. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Richard commented  · 

    I wholeheartedly agree with you and @Guillaume. The lack of access to the User object and Request details in Database Triggers isn't just a technical limitation—it's a business one. This feature is fundamental for implementing robust server-side logic which are essential for auditing, permissions, and complex workflows. But more than that, it's a monetization opportunity. Imagine the new use-cases and services companies could offer with this kind of flexibility. As someone deeply involved in backend and game development, I can attest that being able to fine-tune our logic without resorting to cloud functions and AWS deployments—especially when we're on GCP—could be a significant cost-saver and an incentive for wider adoption of Atlas services. Adding a parameter field when setting up a Trigger to pass this information would make Atlas not just a more powerful tool, but also a more financially attractive one.

    Richard supported this idea  · 

Feedback and Knowledge Base