The AUT is a web application. There are different types of users like admint, consumer etc.
The application is a utility domain application. There is hardly any data that user/human inputs into the system.
The data is coming from electronic meters and getting stored in the database.
Our application only renders the data to the consumers, admins and other users with the data with different calculations in the form of charts and graphs.
There are about 9-10 pages in the application.
My question is : How can I proceed with automation in this scenario..?
Related
We are a SaaS product and we would like to be able have per-user data exports that will be used with various analytical (BI) tools like Tableau or PowerBI. Instead of just managing all those exports manually, we thought of using some cloud database such as AWS Redshift (which will be part of our service). But then, it is not clear how is user will access those databases naturally, unless we do some kind of SSO integration with AWS.
So - what is the best practice for exporting data for analytics use in SaaS products?
In this case you can build your security in to your backend API layer.
First you can set up processes to load your data to Redshift, then make sure that only your backend API server/cluster has access to redshift (e.g. through a vpc with no external ip access to redshift)
Now you have your data, you can validate your user as usual through your backend service, then when a user requests a download through the backend API, the backend can create a query to extract from redshift only the correct data based upon the users security role. In order to make this possible you may need to build some kind of security column into your redshift data model.
I am assuming getting data to redshift is not a problem.
What you are looking for, if I understand correctly is a OEM solutions.
The problem is how does one mimic the security model you have in place for your SaaS offering.
That depends on how complex is your security model.
If it is as simple as just authenticate the user and he has access to all tenant data or the data can be easily filtered for user. Things are simple for you. Trusted authentication will allow you to authenticate that user and user filtering will allow you to show him all that he has access to.
But here is the kicker, if your security is really complex , then it can become really difficult to mimic it within these products.
Here for integrating tableau this link will help:-
https://tableau.github.io/embedding-playbook/#
Power BI, this product am not a fan off. I tried to embed a view in one my applications and data refresh was a big issue.
Its almost like they want you to be a azure shop for real time reporting.( I like GCP more )
If you create the api's and populate datasets then they have crazy restrictions like 1MB/sec etc.
On the other instances datasets can be refreshed only 8 times.
I gave up on them.
Very recently I got a call from Sisense and they seemed promising as well from a OEM perspective. You might was to try them.
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.
We want to build a large customer web portal for our customer care rep and end customers. The web portal has multiple functionalities like Case mgmt, customer mgmt, reports, Trouble shooting tools,etc. Each of these are built by separate team but the portal is to be hosted/deployed/accessed using one url and the portal should have SSO to navigate across these functionalities/modules. Each of the modules can be built and hosted in separate servers. What are the alternatives to build such web application where multiple teams can make releases independent of each other. Less scenarios to merge source code. Note the technology stack is AngularJS for UI and Spring Rest API for backend server. Any design proposals will be appreciated. Not looking for portlets since they have their own challenges
One Option is each of these functionalities will be modeled as tab and within each tab we have an iframe which gets data from separate app server.
Our company is thinking about a mobile app (android, ios) that needs to comunicate with a backend sending "questions" and receiving "answers", based on a search in an ontology database.
I have some questions:
1)What is the state of the art in ontology database at the moment (both commercial or open source)?
2)In order to develop such a backend, what kind of server(software) is required?
3)Since this application is supposed to have thousands of users at a time (it is meant for public administration purposes), what kind of server (hardware) would be require? (distribuited server, load balanced, etc).
Thank you very much.
I have got olap cube on ssas which has all operational history data
I need a front end toll which can not only show data from cube but also sources like web crawl scribe blogs Facebook etc.
Can I leverage any open source software for building required reports which can be run in real time
Have got OBIEE but need a platform which can help devise such reports through a search screen on wrbsitw with parameter enters by user