vscode-motoko VS cancan

As the new maintainer of the VS Code extension, I completely agree that we need to rewrite the LSP in a more portable language. I'm currently working on this (initially as a fallback for projects without dfx configuration), and this survey will directly inform what features we prioritize in this overhaul of the extension.

Thanks! Can I find this also somewhere in written form e.g. a Medium article or somewhere in the sdk.dfinity.org documentation?

Sorry it seems like I read over the title too quickly. You already have an app and you want to know If you can port it over. For your second question no that is not a problem at all. if you go to http://sdk.dfinity.org/ you'll find plenty of example where you host your frontend in an asset canister and that served out frontend can then make calls to the backend canister.

D. We test the platform via sample apps. BesidesCanCan, we also publicized one of thehackathons where we built apps. I was particularly proud of my hackathon team’s videoconferencing app using IC + WebRTC: https://github.com/Dfinity-Bjoern/Magnify

CanCan (demo app): https://github.com/dfinity/cancan

What I am going for is, I believe we are using SNS or SQS because we don't have a reliable computer that we can trust for scaling. If somehow dfinity solved the problem of scaling with the cannisters, and as far as I can see from the docs it seems like they solved it, then all those components we use whether its SNS or SQS or even S3 will become unnecessary because you can just store the data in memory(it won't be stored in memory yet the from the mokoto code it will look very similarly). Imagine if you have an infinitely scaleable Lambda function that never dies off. I think this is what dfinity is trying to achieve and it would be pretty cool if it works out. The Tiktok(cancan) example is pretty eye opening on how it can work in a real world application https://github.com/dfinity/cancan/blob/main/service/CanCan.mo