Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am looking at using Go for my web server:
https://golang.org/doc/articles/wiki/
I was actually going for:
https://spring.io/
since it comes with tons of modules for a web server, like security, data, etc.
Would it make sense to use Go as the Web Server for handling traffic/request and have Spring behind for the actual building of the back-end/MVC?
Or would you typically needs to make a decision between either Go or Spring?
Would it make sense to use Go as the Web Server for handling traffic/request and have Spring behind for the actual building of the back-end/MVC?
No, I don't think so. It's better to take nginx and have Tomcat server with Spring application behind it.
Or would you typically needs to make a decision between either Go or Spring?
Yes, choose what's better for your current task. You can use Spring for the entire web application, Go for some parts, etc.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I have just started out doing web development projects for clients and I have done two so far using NextJS, NuxtJS along with headless WordPress for the CMS. As I also have a full time job these projects take a fair amount of time and I end up working constantly.
I have recently come across Webflow and have messed around with it to see how it works. It seems like if I used Webflow and the CMS is provides I could get through projects much quicker than I would currently.
Do you think that for freelancing using a tool like Webflow is a better idea than what I am currently doing?
I currently use Webflow for client projects and I use Next.js at work. I would highly recommend using Webflow for the following reasons on most web dev client projects.
Speed of customization (You can create components in Webflow and copy and past them into new projects, which allows you to reuse standard parts in seconds)
CMS already integrated.
Ability to easily give clients access to edit their own content if they need
Easily edit SEO settings
Easily connect other tools like Zapier and Memberstack if you need
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I am bulding a learning portal for a client and the client has asked for a feature where the user can record and upload sound directly from the browser (or browser plugin) to a custom made forum on the portal. The client envision having a button like [start recording] on the site. I am probably ending up with recommending against this feature but I would like to hear if any of you have done something similar and what you used.
This specific application is built using dotnet core 2.0 and Angular 5 in the frontend.
Using WebRTC could be an option if you can run your site under an SSL cert.
You may want to take a look to this example here.
Here you have another example using the device camera.
You can store the response on a Blob and send it to your server.
It is an initial aproach but I think it could help you take a decision.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I Have a question regarding those 2 techniques, if I'm going to use both techniques in my project doesn't they clash?
for example, they both use the MVC model. So if I use the angular routing isn't the ASP.net MVC routing unnecesarry than?
Is it a smart move to only use ASP.net to create the WEB API and the other backend processing, and angularJS to implement MVC and talk to the API
any suggestions?
You shouldn't have to worry about them clashing if done correctly. Your bigger concern should be the additional and redundant work it may cause. For the large majority of situations, having Angular interact directly with WEB API is favorable because it eliminates a layer and makes your UI completely portable between technology stacks.
There are merits to the hybird approach though that are concisely expalined here: https://softwareengineering.stackexchange.com/questions/209735/mixing-angular-and-asp-net-mvc-web-api
The two can complement each other. MVC routing only kicks in when you make a server request. So long as no HTTP request to the server is made, then MVC routing doesn't kick in. I use the server for returning "dynamic content" that depends on some server resident information. You can fetch modals from the server as Partials. Using the Server for mostly API work is however advisable.
There is a project called TwitterBootStrapMVC (https://www.twitterbootstrapmvc.com/) That enables you to render pure bootstrap markup on the server and deliver it to angular after some "post processing". It is handy and works well with Angular.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I just got introduced to log4net and its abilities. For starters I'm currently working on a small project. We need to log errors,warnings etc to a file and also send an email to all developers involved about any Fatal errors. Is log4net an overkill for a small project thats got about 10 classes that require the logging functions? Are there any benefits of using log4net in the long run? We were initially going to just use FileIO manipulations and Mail functions to achieve the same.
The answer on this question is primarily opinion-based, some reasons to use a logging framework from the start:
Standard way of logging
Easy configuration
Small projects will grow, if you do it right from the start, there is no later rework needed
Using a logging framework will not cost you more time than writing your own. It will probably safe time. For example log4net will never crash your program when logging fails. Your own framework might interact with your business logic and gives you unexpected results.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Currently I am working on multiple projects as a third party (outsourced) where I have no control over the hosting. My application is modular enough to be changed on the fly, all that's required is slight edit in Html / CSS and it'll become a brand new site.
I do not want my proprietary codes to leak on the web without my consent.
Since I'm contracted to only work on a few particular domains, I wish to "lock" them down in the sense there won't be multiple instances of the same application running in the wild.
Domain locking comes to mind, but this will be rather restrictive as my client will no longer be able to change domain in the future.
Any other inexpensive ideas?
You could try having a registration server somewhere that requires various libraries in the system to register infrequently.