Non Functional Requirements for Hyland PaaS Alfresco

cancel
Showing results for 
Search instead for 
Did you mean: 
cbalaggan
Member II

Non Functional Requirements for Hyland PaaS Alfresco

Can someone please help with generic guidelines for Hyland PaaS for Alfresco

Availability

Scalability

Reliability

Observability

Mainitainability

Performance - Along with guidelines need some examples like for 1 MB of data upload how much time it will take, for searching a 1 MB file how much time it takes.

Please provide whatever information you have on above.

4 Replies
angelborroy
Alfresco Employee

Re: Non Functional Requirements for Hyland PaaS Alfresco

cbalaggan
Member II

Re: Non Functional Requirements for Hyland PaaS Alfresco

@angelborroy  thanks for the response. The document you gave me have lot of information i require. Some information i can't still find

Performance - How much time it takes to upload certain amount of data using REST API? Any examples for that

Scalability - How is the Hyland PaaS alfresco scalable? Is the only auto-scale option is there, apart from any other details on that.

Observability - I understand that hyland maintains logs and monitors systems as well. But can hyland paas integrate with tool like DevO for logging and New Relic for Monitoring.

 

If you can answer the above will be very helpful. Thanks.

williamsilva
Established Member II

Re: Non Functional Requirements for Hyland PaaS Alfresco

Hello,
The answers below are basic in migrations and deployments of Alfresco Community 6.0.1 and ACS-Docker 7.2, 7.4, 2.3 in corporate and government customers in Brazil.
They were carried out in on-premises and Cloud environments - AWS and Azure, Docker.

Q- Performance - How long does it take to load a given amount of data using a REST API? Any example for this.
A- The ACS is a content that receives and stores documents coming from "collection.json", so the sending rule must come from your service.
Ex.:
File format: JPG, GIF, PNG and PDF
·Maximum number of files: 10 files per transfer
·Maximum size: 10 Mb per transfer, adding all files
Estimated number of notifications: 16 thousand notifications per month
·Maximum number of files: 160 files per month
·Maximum file volume: 160 Mb per month


P-Scalability - How is Hyland Outdoor PaaS scalable? The only autoscale option there is, plus any other details about it.
A- Yes, we have already autoscaled kubernetes in 4 Alfresco Community pods and the same project in 04 Docker-Alfresco Community containers in the migration of 7 TB/ 4,080,000 docs.
Note. It is not the quantity but the quality of the documents

P- Observability - Understanding that Hyland keeps logs and monitors systems as well. But Hyland PaaS can integrate with tools like DevO for logging and New Relic for monitoring.
A- In our observability stack we have successfully used:
- Elasticsearch
-Filebeat
- Metricbeat
-Kibana-
- Logstash

We use PaaS - Azure Grafana + PostgreSQL

Successful implementation will only occur if Alfresco is installed with a good foundation and a good support and monitoring team.
SDS

 

cbalaggan
Member II

Re: Non Functional Requirements for Hyland PaaS Alfresco

@angelborroy @williamsilva and all in community, I am looking for some kind of statistics w.r.t performance for Alfresco for Hyland PaaS offering. For remaining i was able to get the information which @angelborroy  gave. 

 

Please check if you can provide the information.