AEM author scalability key Parameters to be considered
Solution : Common approach for Application Scalability as follows:
- Vertical Scability
- Horizontal Scalability
- Data Partitioning
Bottlenecks and Priority
1. LAN bandwidth, including WiFi
2. Server Disk IO Individual spinning hard disks are not useful for large deployments.
3. Server RAM Unused RAM improves Disk IO
4. Server CPU
Note :
- Vertical Scability
- Horizontal Scalability
- Data Partitioning
Bottlenecks and Priority
1. LAN bandwidth, including WiFi
2. Server Disk IO Individual spinning hard disks are not useful for large deployments.
3. Server RAM Unused RAM improves Disk IO
4. Server CPU
Note :
- More Server Disk I/O = More performance
- More Server RAM = More Disk I/O Performance
- Vertical Scaling – More Effective than Horizontal Scaling
Refer the document from Adobe:
AEM Developer tools for Eclipse and Integration
Statement : AEM Developer tools for Eclipse
Solution :
Reference Resources
AEM Developer Tools Download Site
http://eclipse.adobe.com/aem/dev-tools/
Sling IDE Tooling
https://sling.apache.org/documentation/development/ide-tooling.html
Forum for discussions & questions
http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobeexperience-manager.html
Issue reporting & tracking
https://github.com/Adobe-Marketing-Cloud/aem-eclipse-developer-tools/issues
Hobbes.js: UI Testing Framework
http://docs.adobe.com/docs/en/aem/6-0/develop/components/hobbes.html
Solution :
Reference Resources
AEM Developer Tools Download Site
http://eclipse.adobe.com/aem/dev-tools/
Sling IDE Tooling
https://sling.apache.org/documentation/development/ide-tooling.html
Forum for discussions & questions
http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobeexperience-manager.html
Issue reporting & tracking
https://github.com/Adobe-Marketing-Cloud/aem-eclipse-developer-tools/issues
Hobbes.js: UI Testing Framework
http://docs.adobe.com/docs/en/aem/6-0/develop/components/hobbes.html
Subscribe to:
Posts (Atom)