| By Alen Ziver MALHASOGLU,on May 8th,2012 By Alen Ziver MALHASOGLU,on May 4th,2012 By Alen Ziver MALHASOGLU,on May 3rd,2012 Commerce Server Next Steps whitepaper published by Ascentium. Notable sections from the whitepaper are as follows: “For current Microsoft Commerce Server customers,Microsoft will continue to honor mainstream and extended support of Microsoft Commerce Server 2009 through 2014 and 2019,respectively. Microsoft will not release future versions of Commerce Server,but Microsoft Commerce Server 2009 R2 will continue to be part of Microsoft’s official price list until July 2012. Both companies are working closely together to facilitate a smooth transition plan with customers. For more information,please visit http://www.commerceserver.net.”
“If you are currently running an older version of Microsoft Commerce Server,you may want to consider migrating to the new Ascentium-branded release (available Spring 2012) and gain the benefits from an enhanced product roadmap and premium product support offerings.” ref: http://go.zam.web.tr/bx By Alen Ziver MALHASOGLU,on May 3rd,2012 “Are there other options for Commerce and SharePoint 2010? –yes,in theory SharePoint will cooperate with any virtually any other commerce server solution. SharePoint would contain the detailed content,while the commerce component will handle payment and fulfilment. Examples of other commerce solutions that will interoperate with SharePoint 2010 include: Commerce Server 2009 R2 –http://www.microsoft.com/commerceserver/ Optimus BT –http://www.optimusbt.com/ Aivea –http://www.aivea.com/aivea-commerce-server.htm CommercePoint –http://www.sharepointinnovations.com/sharepoint-ecommerce/default.aspx Itequia –http://oriolquinquilla.tech.officelive.com/solutions_Itequia_eCommerce_for_sharepoint_en.aspx ” ref:http://blogs.technet.com/b/digital_musketeer/archive/2012/02/03/ascentium-commerce-server-2009-and-sharepoint-2010.aspx By Alen Ziver MALHASOGLU,on April 26th,2012 By Alen Ziver MALHASOGLU,on April 26th,2012 By Alen Ziver MALHASOGLU,on April 26th,2012 Windows Azure –VM Role Jump Start http://technet.microsoft.com/en-us/edge/Video/hh479556 What a VM Role Can Do The VM Role is a perfect fit for the following scenarios: - Long running application installations
- Error-prone application installations
- Application installations requiring manual interaction
In these cases,a startup task will not work,thus the only solution is to use a VM Role. ref http://msdn.microsoft.com/en-us/gg502178 Exercise 1:Creating and Deploying a Virtual Machine Role in Windows Azure http://msdn.microsoft.com/en-us/gg502180 How to Upload a VHD to Windows Azure http://msdn.microsoft.com/en-us/library/windowsazure/gg465385.aspx By Alen Ziver MALHASOGLU,on April 24th,2012 Using Windows Azure Regions efficiently http://weblogs.asp.net/cibrax/archive/2011/10/26/using-windows-azure-regions-efficiently.aspx * Network latency* Availability “a region or data center might become offline and your application should be prepared to handle that scenario.” Azure Table Service already provides some built-in support for crash recovery based on the idea of partitions that are replicated across different nodes (in different sub regions,for example North US and Central US),a SQL Azure database is not prepared for that scenario. http://weblogs.asp.net/cibrax/archive/2011/10/26/using-windows-azure-regions-efficiently.aspx Deploy an Azure VM Role Service Package http://www.techrepublic.com/blog/datacenter/deploy-an-azure-vm-role-service-package/5224 Windows Azure Jump Start http://channel9.msdn.com/posts/Windows-Azure-Jump-Start-01-Windows-Azure-Overview By Alen Ziver MALHASOGLU,on April 16th,2012 By Alen Ziver MALHASOGLU,on April 12th,2012 Service Bus QUeues (SB Queues) and Storage Queues (S Queues) | Comparison Criteria | Windows Azure Queues | Service Bus Queues |
|---|
| Ordering guarantee | No | Yes –First-In-First-Out (FIFO) (through the use of messaging sessions) | | Delivery guarantee | At-Least-Once | At-Least-Once At-Most-Once | | Transaction support | No | Yes (through the use of local transactions) | | Receive behavior | Non-blocking (completes immediately if no new message is found) | Blocking with/without timeout (offers long polling,or the “Comet technique”) Non-blocking (through the use of .NET managed API only) | | Receive mode | Peek &Lease | Peek &Lock Receive &Delete | | Exclusive access mode | Lease-based | Lock-based | | Lease/Lock duration | 30 seconds (default) 7 days (maximum) | 60 seconds (default) 5 minutes (maximum) | | Lease/Lock granularity | Message level (each message can have a different timeout value) | Queue level (each queue has a lock granularity applied to all of its messages,fixed for the lifetime of the queue) | | Batched receive | Yes (explicitly specifying message count when retrieving messages,up to a maximum of 32 messages) | Yes (implicitly enabling a pre-fetch property or explicitly through the use of transactions) | | Batched send | No | Yes (through the use of transactions or client-side batching) |
Quoted from the resource below Windows Azure Queues and Windows Azure Service Bus Queues –Compared and Contrasted http://msdn.microsoft.com/en-us/library/windowsazure/hh767287(v=vs.103).aspx Service Bus Queues vs Azure Storage Queues http://social.msdn.microsoft.com/Forums/en-US/appfabricctp/thread/e88255a5-4b02-4f44-97a3-d2dad9aff320 | |