4Cloud comes from an international project with Austria and Singapure that saw 4ward Development and System teams working in one relevant project related to the cloud for evaluating of the use of the main solutions on the market.
A scope was to ensure maximum availability of services using:
It was established a basic framework that can offer services via SOAP and REST web services to web client, mobile and desktop with ASP.NET MVC interface for data management and test execution and a backend based on SQL Server or MySQL for the report and NoSQL engines such as: Storage Table, SimpleDB orMongoDB for large amounts of data.
This layer of abstraction is called 4Cloud and allows to use transparently the services on-premise or on the cloud without code modifications.
We have analyzed ways of use and performance of various components such as:
- 4Cloud:
- .NET 4
- Managed Extensibility Framework
- Microsoft AppFabric
- Entity Framework 4.3
- Automapper
- Layer web services SOAP/REST con JSON o XML
- AWS SDK
- Azure SDK
- Enterprise Library 5
- Cloud Integration Patterns
- ServicerStack JSON Serializer
- Automazione through T4 template
- Task Parallel Library
- WCF Autostart with AppFabric
- Azure:
- Blob Storage
- Table Storage (NoSQL)
- Queue Storage
- Service Bus
- SQL Azure
- SQL Azure Data Sync
- Reporting Services Azure
- Traffic Manager
- Web Role
- Worker Role
- Enterprise Library 5 extenstions for Azure: Topaze & Wasabi
- Diagnostics logging
- Azure AppFabric Caching
- AWS:
- CloudWatch
- CloudFormation
- Elasticache
- RDS (MySQL)
- S3
- SimpleDB
- SNS
- SQS
- VCloud:
- Windows Server AppFabric for Caching and hosting of web service and 4Cloud worker role
- SQL Server 2008 R2
For more information feel free to contact us: