I want to build a wind turbine ontology with protege.
There is a class named Blade and many instances of this class.
It’s better to add all these instances or add only one instances and link to a database? The database is to store the date of Blade.
Related
I have a database for my shop which I've written in Laravel and was wondering if it's possible to merge that database with Woocommerce or vice versa.
What I want to do is create a product in one site and be able to show it on my other site including pictures, description and ...
I looked into woocommerce database structure and saw that products are being saved in wp_posts.
Is it possible?
We´re planning to use the Microservice Architecture in our next application. I wanted to know if it´s a common practise to have a same domain entity for every related microservice. For example, there is a customer. A customer consists of multiple users and one company. They are existing in a customer service. Then there is a warehouse service. A warehouse can have different customers in different roles. So the warehosue entities holds keys to the customers.
In front of those two microservices there is an API gateway. Now when showing a screen with warehouses we need also the information about the customers from the customer service. So the API gateway could handle this, meaning fetch the warehouses and then the related customers. But then we connect two services via the API gateway. Is it a better way to hold the customers with specific attributes also in the warehouse service? But this is just necessary for view/UI specific use cases? Is this a correct way to bring "view logic" to the services?
You might implement this in different ways. The warehouse micro-service may consume data from the customer micro-service and enrich its response having everything in it for the presentation. Or the presentation may consist of several areas which are loaded from different micro-services each presenting its section.
Try to have as much microservice as you can based up single responsiblity system.
Create a API service and allow it to generate events which will be then consumed by other microservices and will provide results based on required parameters.
Now API can club the data and can respond back with the required format.
having multiple microservices will help you in scaling up and down , if you had only 2 microservices it is more or less like a monolithic services only.
Take the decision, considering future in mind.
I have an iOS app that currently stores and pulls its data in/from SharePoint lists via a web service. I want to have the option in settings for the app to also use another database or cloud database i.e. parse.com
I don't want to have to put if statements all throughout my code to test whether the app is set up to use either of the repositories.
What's the best way in an iOS app to architect it to use multiple repositories/databases to store and retrieve the data used in the app?
Build a data manager class that handles the logic. I would go so far as to create one for each service you are attaching to. They can all inherit from a single base class and share the local cache code (which I am assuming is Core Data based on your tags). Then on launch you can instantiate the one you want to use.
I would NOT use a Singleton as suggested. Better to use Dependency Injection and be able to tear down and build up a new data manager if you switch between services while your application is running. Using a singleton would be a poor design decision.
If you localize all of your network code into a single class (something I was speaking about last year as a Network Controller) you can then easily switch between services by keeping your interfaces the same.
I'm building a Google App Engine server alongside an Android client using the Google plugin for Eclipse. I have an unexpected problem when using the automated tool to generate the Android client library for calling the server APIs.
I have 3 model classes on the server-side: User, UserLocation, DeviceInfo.
User has a OneToOne relationship with UserLocation, and a OneToOne relationship with DeviceInfo (both of these relationships are owned by User).
I'm using JPA annotations to model these relationships in the server model classes.
After implementing the model classes, I then use the plugin to "Generate cloud endpoint client library", which automatically adds libraries to my Android client enabling me to perform CRUD operations on the model classes.
This all works great, except that the plugin generates multiple User, UserLocation, and DeviceInfo classes, one for each of the three endpoints. The problem manifests when I try to add a User object to a DeviceInfo object, because the DeviceInfo object expects a different User class than the one I'm trying to add.
I hope that makes sense.
How can I associate a User object with a DeviceInfo object?
I am using subtable inheritance strategy to design my data store using JDO for my application hosted in google app engine. There are three types of users that can logs into my app.
these are the classes that I designed for this purpose 1) User(Abstract)
2)UserType1 extends User 3) UserType2 extends User 4) UserType3 extends User. Now the problem is every time I want to find an user based on the userId I have to check each entity kind separatly. It will become more problem when the user types increases. Please help how to design the model classes in this scenario.
Thanks
you're looking for JDO2's superclass-table inheritance technique. it works similar to the python app engine PolyModel class.
unfortunately, app engine doesn't support superclass-table right now. instead, consider consolidating all of the different class's fields into a single User class with a type enum.