Hi I'm an undergraduate student who's doing a project on vessel tracking system using blockchain. Im really new to this an I would really appreciate any help you guys can give me. My project is that Ill get location and other important data about the vessel and send them via a satellite directly to my database. That database must be blockchain like one so it will increase the trust among the entities by providing them transparency in tracking details of the vessel. Then it all will be displayed in a web application to users to interact with there private key according to there vessel.
I did a small research on Blockchain, but didn’t find something that’s directly relevant to my project. They are all about creating Blockchain and doing transactions and creating bank like apps. I found out about bigchainDB and Blockchain mongoDB but I have no idea about If it is suitable for my project. I need from you guys is that to find a path to create a blockchain like database to store and retrieve my data real-time to the web application. I Dont know is this even possible to do. I am sorry if my English is bad. I hope you guys can understand me and I would really appreciate if anyone can give any insight on this, you guys will be saving my life <3. thank you
Related
I collected lots of data (images, pdf's,...) over some years. For my start-up, I like to be able to access this data through a web application as well as a website. All of the data has a relation with each other reaching from example images, contact cards, and bills,... so I would like to query the data by inserting tag filters. I am a very beginner in this stuff but would love to get a good basis and self-education, so I can maintain and manage my database. A connection with normal SQL data is also necessary. I assume the setup of a central database to connect later on web applications/website/mobile apps is the first thing to create....? If somebody can help me at least with some advice on how to start, I would be very happy.
I searched a lot, but as a newbie I get overwelmed by all kinds of software.
I would love to get some help on how to start in the right way.
I am trying to figure out a reliable data architecture for a small business that wants to utilize Shopify for their online store.
My current idea is to have a central database (doesn't matter which, we'll say Postgres). The business users can create products, services, customers, etc in Shopify. Customers could go to their site and order things.
Then I would have a background process to sync all these things from Shopify to this central database.
Some orders would have to be put in a LIMS system so I would have another background process to sync these orders in the central database with the LIMS system.
Some orders come directly from the LIMS system so another background process to sync these orders to the central database.
All the orders in the db need to be synced to Quickbooks so another background process to sync this.
Concerning Shopify, does this seem like a doable strategy? I'm an experienced programmer, but no experience with Shopify or its APIs.
Also, I'm not really a fan of syncing data sources but...is there a better way?
Obviously I could write an admin ui to let them create things in the central db first and then sync them to Shopify.
But isn't the whole point of Shopify to make this part easy by providing them a way to create all these things right out of the box?
One of the other things that they want is to run reports against this central database. In theory Shopify could act as the central database, but not sure what reporting would even look with Shopify API.
My advice to you is to use Shopify till you understand it, and once you do, you may find things that Shopify cannot do for your business. Only then would you marshal any resources to try and fix those problems with custom code. As it stands, your question is one of "how would I..." for problems that do not exist for you. Why bother thinking about problems you do not have? Wait till you actually have a problem, then ask a question about how to solve it.
TL;DR: Does strapi require me to model my database schema inside its admin panel?
Or is there a way I can use a database that I created its tables (but didn't populate it yet), populate it then and generate APIs for use in my front-end?
I understand this may be a general misunderstanding on my part as far as and I may have gotten on this framework for the wrong reasons - but I'd like to understand why so I can avoid making such decisions later on and have some better fundamentals for choosing my tooling.
My goal - I'm creating an eCommerce website for an extremely small artisan's shop that cannot afford anything but stuff like free AWS tiers at the moment. The end goal is a website for a few products with credit card payment, a database, and reasonably safe authentication, and I want it to be simple enough so that I can eventually scale it if it grows. I want to understand this project very intimately and really get to know my tooling.
What I tried vs my needs - my stack currently consists of react+next on the front-end, and strapi with postgresql for the back-end. I then took to the PostgreSQL docs (and my undergrad's database notes) and tried my hand at designing a database schema based on my app's use cases. However, I believed strapi would work with a traditional database modeled in a bare bones way. What I see now is that the only option from the docs is modeling it from scratch through its admin panel. I'd like to really understand out how I'm supposed to work with something I modeled elsewhere - how it all connects. I'd really appreciate any help. I hope this question is not too broad but I'm hoping it'll clear up some huge misconception I have!
I work for an app that store some health datas and the law and our ethic make us respect some rules about the treatment of personnal datas.
We want to store the health datas of our users in a different database than the personnal datas (especialy the name of the user). The goal is that if a hacker get access to the health database/server app, he will not be able to get the identity of the persons. And if he get access to the personnal data database/server app, he will not be able to get the health informations of the persons.
Anyone in my team never made this kind of thing, the client proposed this kind of structure
The goal is to have a middleware that manage authentification and provide the id of the personnal data database with the other one.
In my mind, we could make far better by using some asynchronous tricks but i'm not an expert in security and i only have a confused idea of what i could make. Maybe there is some standard solution that is used in this kind of situation.
It would be realy great to have some advice of the community about this problem.
I'm working on a project at school where we have to create a small system for an RV retailer to track customers, vehicles, employees, inventory, and so on.
We've gotten to the point where we'll need to start coding pretty soon, but I'm having trouble figuring out the logistics of everything. For example, I know enough to build and use the website and database, but I don't have any idea on how to connect the two.
I know SQL fairly well. Enough to know what and where to look for the information, but I don't know enough about connecting my database to know what I'm looking for.
So what I'm looking for is a basic rundown on different options I can look and do some research on what would be best for our group.
I feel like there's a lot of information out there on how to do stuff, but I just don't have the basic information on why it's relevant and how and where to fully utilize it.
I hope this makes sense. Please let me know if there's anything I can do to help clear it up.
One of the options of having a database-driven website is to use PHP.
It is a server-side scripting language, which is used to generate the dynamic content on the webpages. You can connect to the database, obtain user input using for example HTML forms, perform queries and display results on the webpage.
Essentially you build an application with a web-based user interface. PHP is supported on a vast majority of web hosting platforms.