I understand Strapi is a headless CMS. But I wonder if it can be used as a general backend framework (like Django) to build a social app.
By looking at its CRUD API capabilities, I feel it is possible; but on the other hand, the way Strapi boasts its user management and RBAC makes me feel it is very much tailored for internally managed users
Can someone share your understanding and experience toward Strapi?
Related
I am far for being an expert in web development or any app development in general but i have the basics. I want to develop a simple microsoft Teams app for my organisation in order to do HR management. I want to use MongoDB to store the data. However I've spent quite a lot of time on trying to figure out how does the toolkit works. How can I create an teams application in teams using a mongoDB database. Which language should I use, React JS?
If you have any useful links i'll take them.
Thanks for your time guys :)
Does jBASE support web sockets or any other similar technology to offer real-time interaction capabilities? For example, if I am creating a web based dashboard, can I show real time updates on the charts with a jBASE backend?
Please note, this answer applies to the Zumasys iteration of jBASE not the Temenos T24 flavor.
As of jBASE 5.7.10, jBASE supports building web based dashboards like this by utilizing the jAgent module to create RESTful APIs that you can use to serve traffic from your jBASE system. You can read more about jAgent at our Introduction to jAgent guide and you can see more about the the PICK libraries we provide for REST API development at our APIs page.
You may also be interested in our full-stack-with-pick tutorial on GitHub, which includes lessons on:
How to set up demo data in jBASE
How to set up REST API get endpoints
How to set up a simple Vue.js environment
How to display a database record with Vue.js
This would give you a recipe on building APIs to access the information you're looking to convey in a dashboard, as well as an idea of how to begin working on the dashboard (as it so happens there are many great, free Vue.js based dashboards available on the internet).
For what it is worth we are evaluating expanding the protocols and technology available within the next iteration of jAgent, including but not limited to a look at implementing web sockets.
Me and a team built a small "meet people" app last semester that used Spring linked to a MySQL database as the backend. I am working on my own app now and I'm worried about security because all of our user information was sent over HTTPS GET requests to the server. It seems weird to me that we were able to hop on google chrome, type in xxx.xxxxx.xx:xxx/user/2 and get back a JSON with all of a specific users information. If anyone knew our url/port, they would be able to access this information themselves.
I'm sure this is a basic question, but what steps do I need to take to create a Spring backend that isn't as easy to access? I'm basically a total beginner in this, but I did write the service in Spring last semester so I know the basics.
You can use Spring Security which is a very good project and easy to integrate.
There are many types of security features it provides :
Basic Spring Security
Role Based Spring Security
baeldung.com and howtodoinjava has a very good series on it.
You can also use jwt-authentication-on-spring-boot which is also a good way to secure the APIs.
I'm contemplating to use Parse as a platform for my app, as I'm trying to avoid creating and managing the cloud infrastructure myself.
For the sake of simplicity let's say that my app will hook into an Exchange Server and will need to leverage some hosted Machine Learning service to categorize my e-mail and report on insights found.
I'm assuming that Parse would store my core data, while the hosted ML will store the "Big Data" associated with processing for insights.
I'm also expecting my app to receive push notifications generated by the hosted ML service.
Does this sound like a plausible way to go about it and leverage Parse, or am I better off developing the backend myself?
I think parse.com is the right place for you requirements, because they have everything you need like storage of core data, push notifications, cloud module which can be integrated with heroku, social integration, user management functionalities.
They also have large set of client libraries for desktop and mobile apps (node,java,.net etc...) also they have libraries of embedded devices.
The biggest advantage is that everything is setup, and you are focused on software development not on infrastructure things. This is my opinion.
I've been experimenting with the above stack and so far was really impressed. Seems like a viable path forward. The Cloud Code capability of Parse is very solid, and easy to work with. If you want to run services outside of Parse code this us also possible : just issue REST calls.
Good morning,
I am going to write a web service and I am not sure which framework would suit the situation best. I understand what Node and .Net are good at.
The client will call the services at the following stages:
App loads up - user logins in via Facebook API.
User can create an "entity". This entity will be stored in a database (SQL for .Net/ Azure table for Node) and also posted to a Facebook application (timeline stuff). User can make changes to this at any time.
User can browse Facebook Friends (Facebook API again).
Changes to the entity will be pushed to all users who have "joined" the same entity (SignalR .net/Socket.io Node).
That is the skeleton of the web services, there may be more Facebook calls or CRUD operations. Which Framework will handle this best?
Many thanks.
Aside from the mentioned WebAPI, also consider the excellent ServiceStack for building a webservice.
Any well-written code regardless of the framework will be able to handle it.
If you are a .NET developer I personally think type safety of C# is important so I would not go down the Azure node.js way since it will also force me to use Azure.
I would personally use ASP.NET Web API.
As long as you build your application on a solid framework, you'll be on the bright side (assuming you know how to set-up such an application in a secure and proper manner). For .NET i'd use the Web API and for node.js i'd stick with something like express/connect.
Just keep in mind that node.js and the frameworks based on it are still subject to heavy changes, whereas ASP.NET is production-safe since years.
As a bottom line, i don't think you're able to say "X is better than Y because of Z" in this scenario. It's a matter of personal preferences, infrastructure and your technical skills.