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
Can someone explain to me how the front-end and back-end developing are meeting, or let's say consisting in the web development world? Is C++ a sufficient language for the back-end or I would still need to learn about ruby or python or C# or will it depend?
Font end implies direct presentation to or interaction with the user, such as through a GUI.
Back end suggests the software that's furthest away from end users, which is sometimes some kind of database or transaction processing engine.
You generally expect actions on the front end to be feeding into the back end processing - perhaps causing transactions to happen there, or starting reports running etc.. Sometimes events in the backend will lead to events in the front end, such as offering to display a report, or popping up a notification of some kind.
C++ is well suited to custom backend services needing 3GL languages, but sometimes features well beyond the scope of the C++ language Standard are needed, and it may be easier to get a proprietary database system, or an off-the-shelf solution to queue and distribute jobs across myriad hosts or otherwise "manage" things. If could still be that some or all of the hands-on data processing is done in C++.
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'm about to create a web application first but even though I manage the development with rails, graph and react. should I use python thinking more in the future of the application, if it grows in time? Or if you know about a technology stay first with it for development and then migrate?
Couple of option you can choose for web application
Use GRAND Stack : GraphQl +Reactjs + Apollo server+ Node js + Neo4j(instead of this use any other database which you are comfortable)
If web app event based : Then user Nodejs as server-side technology (MERN)
If web app as Data-computation/ Algorithms solution : then Go we React(Front end) +Nodejs(orchestration/ Middle layer) + Python(application layer/or back-end )+ any DB
Yes, i say every framework is good enough, in the long run every thing comes down to one question, how efficient code did u write?
Django
You can use django if you are interested in python. It is a famous framework which has its own ORM and many security built in features another option is flask
I will share my experience.
Recently, coded a website in laravel 5.5, at first everything was fine but when the number of user(s) grew to >50k. The site became slow and my servers showed 100% cpu usage. Later i changed the code, tried to remove nested loops, optimized my queries and used cache technologies like memchached. The site is working fine now.
i hope that answers your question.
I hope the best for you,
Happy Coding
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I used node for 1 year, but only for writing server applications. I am now interested in making an application that's usually written in a language like C or C++, so I am not sure if it's possible, for example, to write a keylogger or simillar applications using JavaScript and Node.js?
Yes, you can use Node.js to write desktop applications which can act as a keylogger, communicate with device drivers and other system resources.
Most of the system interoperability has gone into providing cross-platform support for particular system event notifications and I/O. Be mindful that there are tall stacks for reading keyboard events that differ from platform to platform, so you will probably want to take a look around the Node.js ecosystem for packages like node-ffi, which may assist you at accessing system resources from your application's event loop.
Should you want to write your own system bindings that are exposed to V8 and accessible by your Node.js application, there is excellent support for going native, from packaging to creating asynchronous events for your Node.js application.
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 8 years ago.
Improve this question
These days I’m having a training in Microsoft Reporting Service. Although it’s a good tool but I can’t find any examples that using it will be useful. To me is always better implementing reports using c# code in combination of javascript controls. With C# and javascript maybe it will be necessary more work but in the other hand I will get better maintainability and better automatic tests. Is there any situation where using reporting services will be the best choice?
In my opinion Microsoft are not maintianing SSRS and will I believe be deprecating it. I have no citation for this, but have used it for 5 years and there has been little development on it in that period, and their launch of Azure reporting services was pulled immediately. Microsoft are heavily promoting the BI/Excel PowerView/Sharpeoint combination as the ad-hoc data enquiry tool of choice, but that doesn't cover the "printed banded report" use case that Reporting Services addressed.
The SQL emitted by the Reporting Model within SSRS is also very poorly performing.
In my opinion your initial misgivings are correct and I would not personally recommend its selection for a new system build. There aren't any directly comparable products which;
1) Have an HTML consumer AND designer user interface
2) Have a mediated data dictionary access to underlying data sources
3) Comply with custom permissions and authentication.
Consequently hand rolling reports in a MVH/HTML toolkit would also be my recommendation. User self-service reports seems to be an unaddressed areas of need. If you dont need user self-service, then just select your reporting toolkit of choice and go with that - if you do need user self-serivce then the choice of possible products is very thin indeed.
I'd be very interested if any other contributors have a different experience with SSRS and the target use-cased (user self-service, banded reporting, data dictionary driven, custom authentication and security).
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 8 years ago.
Improve this question
I want to create my own application for monitoring traffic of my website without using any third party tools like google analytics. In which I want to log screenshots, user details, page details and cookies. So what technology should I opt so as to achieve this goal and which will be best suited and what work flow should I follow.
I've never done this kind of work previously so I'm new to this. Any help would be greatly appreciated.
The technologies I know are : javascript, nodejs, django(python).
You will have to break down your application as it is a humongous task to create something like GA.
You will have to track many user activities(click,spend time etc).so you can do that in plain js or use a cross-platform lightweight library(angular.js) that can make your life a little easy.
Now since you will have to send large set of traced data to you database with minimum latency,use Node.js in this scenario.Simple Ajax call would also work but then it would be very slow.
Now comes your database.Prefer NoSql since it suits your requirement of unstructured data ,preferrablly MongoDb which can help you with its own mapReduce,large storage capacity
.Since there will be lot of calculation involved you can use your python knowledge which can help you process data a lot faster.you can use other languages as well(eg.Go)
Your processed data and results can then be stored in Redis(which acts as a caching layer).
you can use sophisticated graphic library like d3.js,Highcharts.js for displaying Graphical data on the client-side.
There are a lot of factors that can be involved.This is just a very basic outline of what you could do.
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 4 years ago.
Improve this question
I'm wondering what the technologies and best practices are behind real time collaboration in web interfaces.
An example of this is of course Google Wave. Another is PivotalTracker.com.
I'm particularly interested in any work (frameworks, plugins, etc) people are doing with Ruby on Rails here.
I imagine it would have to use Javascript underneath at some level, but you would need a way to abstract this out. Probably polling the server periodically to see if changes have been made, and also a way to resolve conflicts if in the middle of editing something the server comes back and says someone else has updated it.
Thank you!
Wave has operational transform that has a nice property of being easily combinable. You have two users, each of them does "something" in the user interface and two "somethings" can be combined into final document. That allows you to skip the problems with conflict resolution.
A nice way to enable real-time updates to state of the app is by using Comet, which is essentially a geeky codename for keeping an alive, long standing, unterminated get/post request to the server, that server finishes and responds to when something happens on the server. It allows sending to the client instantaneous updates without having the client periodically poll.
I can't really say how to abstract this away in javascript/r'n'r, many of the underlying technical details are hard enough and application specific that no framework supports them out of the box.