I want to know if web development can be done using Raku or Perl6?
Like Django for Python, do we have any framework available for Raku?
Id appreciate if you told us which are the libraries available or any tutorial.
Are there any webhosting providers to host Raku web application?
Many folks are using Cro for this. It's a set of libraries that you can pick as needed (and not just for web development), but offers things like:
Routing requests to handlers, and neat ways to express those handlers
WebSocket support integrated neatly into the router
Templating
Testing
There's a simple tutorial as well as a much longer one on making a SPA.
There is also a fresh CRUD server-side tutorial available.
Finally, there's integrated support in the Comma IDE, which includes a Cro project template where you can select the bits you need, indexing of and navigation to routes, and a timeline view that can be used to understand where time is spent during request processing.
There are base images available to support Docker deployment also, to anywhere that supports that.
I built a web framework for Raku called Humming-Bird it's brand new so there are still kinks to work out, but the core works really well! It is intended to be very similar to Sinatra and other frameworks of that style (express.js etc..)
Humming-Bird has most of the typical features of a web framework including but not limited to:
Routing
Middleware
Serving static files
This project is still in fairly early stages, but it offers more than enough to spin up simple web services, and web apps.
Related
My goal is to implement a generically extendible .NET core web API. The generic refers to modules that can be added at runtime and provide new endpoints as well as functionality. These modules will be developed based on a framework.
Currently I am still deciding if the modules will be included as a DLL or run as a separate process (.exe).
I have the basic understanding of Dependenci Injection regarding the addressing of controllers in a DLL. But now I wonder if and how to realize the whole thing via an own process.
The API should always be addressable via http://localhost/myapi/{endpoint}, i.e. a request to a module should be done via the same URL. For the user / developer of the frontend everything should be presented as one API.
Unfortunately I was not successful on my research and don't know exactly what I have to / should look for specifically. Therefore I hope that you can help me.
Examples are helpful, but I am also keywords or articles, which deal with such a topic, help me further.
kind regards
I am trying to implement speech to text on my .net core 3.1 web app without using any cloud services like Azure, AWS, or Google.
I have found options like deepspeech, kaldi,pocketpheonix. It looks like they can be implemented on a .net core app but being a beginner in .net core and backend development I don't know how to use them and their documentation is not very beginner-friendly.
So if you can provide a brief overview of how to implement these apis on .net core or link to some articles, that would be very helpful.
Just my personal view, some Kaldi or PocketSphinx experts might have a different view.
Kaldi + PocketSphinx
You will need to compile all sources yourself on Windows and Kaldi is a headache to build on Linux, so I guess it is not much better on Windows. That said, they use less resources and are usually quicker.
DeepSpeech
Just download the current English acoustic model (pbmm) and language model (scorer) and use the .NET example code. Should work without compilation.
I'm about to build out my API for my service and I'm wondering if there are any benefits to building it out using the NextJS API integration. It seems a little quirky for my own preferences and the resources aren't as exhaustive as they are for my ideal solution: expressJS. That said I'm aware there are some integrations that would allow me to use express inside the NextJS API but that seems excessive compared to standing up a separate repo for my express API.
So, I'm curious are there any under-the-hood benefits or perks to leveraging the NextJS API within the same repository as the rest of my code?
Thanks!
It depends on your application. Truth is probably a good portion of websites and projects just need a simple request server-side to retrieve data. Having Next.js API helps manages your serverless functions. You could easily do it with AWS's Lambdas and API gateway but the management of many serverless functions can get messy. You can also use CLI tools but Next.js with Now and Netlify can automatically do all this during build/CI/CD.
Under the hood is an AWS Lambda, so the usual can be an issue...cold starts, computing resources. But great for things like accessing private APIs, lower on-demand costs, and development as functions. If its heavy computational data, I would avoid using serverless and just spin up your own separate service. But the plumbing is all the same as an Express or KOA server, its just on-demand and a tool to manage. I just see it as a really easy and simple tool to do a little bit of backend work without maintaining infrastructure.
I am developing a application that is using backbone.js for most of the front end logic and was thinking of using sqlite for storage, but i have run into a few complications with it and need to switch to another NoSQL database.
I see on ravendb's site that it was created in C# and you need a .net compiler. Most of the docs are for ASP MVC type application. I can not go this root because we are developing this as a tablet application with no microsoft based technologies on the client side ( because we want it to work with android and apple )
The server however will be .NET and so i figured this might be do able. Just wondering if this is worth pursuing and if anyone has had any experience using ravendb? Or should i go for mongodb?
It is possible to expose RavenDB directly to a JavaScript application, sure. But it's usually not recommended. The main reason is security, but there are many other reasons to have a middle-layer.
For example, you often need a server-side location to perform application logic. Not everything can be done in the database itself, and if you do it all in the application then you will probably send a lot more data to the app than it really needs. Over the internet, that could mean a slow app.
The route many people take, is to use ASP.Net WebAPI, or ServiceStack, or another similar framework. This gives you a way to expose REST endpoints that your JavaScript app can call. You can connect to RavenDB from there.
Also, you seem to have the misconception that if you used ASP.Net MVC on the server that you couldn't target Apple or Android. That's just false. Whether you use a SPA approach or a traditional approach, you are delivering standards-based content, such as HTML, CSS, JSON and JavaScript.
Yes, You can use it. Actually RavenDB's server is a RESTful web service, which means you can work with it with any kinds of HTTP clients. These clients should be able to issue standard HTTP verbs like GET, PUT, DELETE etc.
ASP MVC is server side. I still at a loss as to why you would want to expose your db to a clientside piece. It is completely worth doing in a server side piece, but do not expose something like a db directly to your client.
Which API frameworks for node js best suits mobile applications (native or HTML5) or client-side HTML5?
While there are many frameworks (https://github.com/joyent/node/wiki/Modules#wiki-web-frameworks-full) , like restify, express, I think hapi was built for your needs. Its focus is on your business logic, and favours configuration for simple and fast deployment.
You can find the package in https://npmjs.org/package/hapi, and https://github.com/spumko/hapi
It looks very promising. There's a talk about the framework in https://www.youtube.com/watch?v=Recv7vR8ZlA where the main contributor talks about what makes an API framework tick.
It supports caching, validations, plug-ins and more (watch the video).