The angular-cosmosdb from johnpapa

angular-cosmosdb's Introduction

Hello 👋

🔭 I’m currently working on ... Azure Static Web Apps, projects for 30+ Web frameworks, VS Code extensions, and Azure
📝 I write stuff at johnpapa.net and dev.to/john_papa
📚 Learn Azure Static Web Apps
🎙 Host the Web Rush podcast
🌱 I’m currently learning ... AI and Copilots!
👯 I’m looking to collaborate on ... https://github.com/johnpapa/hello-worlds
🤔 I’m looking for help with ... https://github.com/johnpapa/vscode-peacock
💬 Ask me about ... https://github.com/azure/static-web-apps
📫 How to reach me: ... https://twitter.com/john_papa
😄 Pronouns: ... He/Him
⚡ Fun fact: ... All things Disney

angular-cosmosdb's People

Contributors

Stargazers

Watchers

angular-cosmosdb's Issues

Deprecation Warning: Mongoose Promise

I get the following warning when running the app locally

DeprecationWarning: Mongoose: mpromise (mongoose's default promise library) is deprecated, plug in your own promise library instead: http://mongoosejs.com/docs/promises.html

Question: Why the server component? Why not have the client get the data directly?

I get that we don't want a thousand web clients to direct connect to CosmosDB, but using the SDK, it does seem feasible to direct connect.

container.items.query('select * from heroes where id=1').fetchAll();

I've read your articles about how easy it is to implement CosmosDB, but why complicate it with another piece of middleware.

Security aside, if you where doing a simple PoT, couldn't you skip the server?

I'm asking, because, that's what I'm trying to do. Take your client component and simply add the SDK and direct connect. Just getting weird AbortSignal errors.

Recommend Projects