Haishi Bai
Haishi.Bai
-
Meet WACELNov 06, 2013 at 4:15 PM
5
Introducting WACEL - Windows Azure Cache Extension Library.
WACEL implements a number of high-level cloud-backed data structures that can be shared among your Cloud Services, Web Sites as welll as Windows Store applications. You create these data structures just as if you were using local data structures....
-
High Available Messaging with Windows Azure Service BusIn this episode I'm joined by Abhishek Lal, a Senior Program Manager of Windows Azure Service Bus to discuss about high available messaging with Windows Azure Service Bus. We'll peek behind the scene and examine high available designs and features at various layers of Windows Azure Service Bus. And we'll...
-
Bootstrap yourself on Boostrap with Pranav RastogiJoin your guides Cory Fowler and Jaffe Worley as they talk to the product teams in Redmond as well as the web community.
This week Jaffe and Haishi are joined by Pranav Rastogi to talk about Bootstrap. Bootstrap is a mobile first front-end framework for building web...
-
Episode 115: Getting Started with the New Windows Azure Cache ServiceIn this episode Nick Harris and Chris Risner are joined by Haishi Bai - Sr. Technical Evangelist on Windows Azure. During this episode Haishi demonstrates the Windows Azure Cache Service preview including:
- What is the NEW Windows Azure Cache Service Preview
- What's the difference between...
-
Priority QueuesIn this short episode we’ll review how to implement a Priority Queue using Windows Azure Service Bus.
-
Competing Consumers PatternThis is a brief introduction of Competing Consumer Pattern, which can be used to achieve common loose coupling, load balancing, dynamic scaling as well as failover scenarios.
-
Episode 108 - What's New With Windows Azure Virtual NetworkingIn this episode our special guest host, Haishi Bai, is joined by Yu-Shun Wang – Program Manager of Windows Azure Networking – who discusses the latest developments of Windows Azure Virtual Networks. Yu-Shun shows us the improved Site-to-Site connection and the new Point-to-Site...
-
Building the Windows Azure Trivia SampleStarting with this episode we'll start to build a real Cloud Service with sufficient complexity for us to have deeper discussions of various software engineering topics and scenarios. Our starting point is a working version that allows user to play in practice sessions. We'll see how we can enhance...
-
Windows Azure Cloud Services Role LifecycleIn earlier episode we removed WebRole.cs from our Web Role. Now it's time to bring it back and have a closer look at role instance lifecycle. And then we'll briefly look into startup tasks. This is also the last episode of fundamentals.
-
Introduction to Windows Azure Worker Roles (Part 2)In this episode we'll continue with the Worker Role introduction. Instead of tightly coupled direct communication, we'll explore other means such as using shared storage and Windows Azure Service Bus to communicate among roles.
Next Episode:
...
Windows Azure Cloud Services Role Lifecycle
http://channel9.msdn.com/Series/Windows-Azure-Cloud-Services-Tutorials/Windows-Azure-Cloud-Services-Role-Lifecycle
Staff
Here is a list of Channel 9 staff members.
Meet WACEL
Nov 20, 2013 at 10:50 PMHi ivan:
To answer your questions:
1. The library itself is stateless, so it scales along with backend services.
2. The size is limited by backend service, such as the size of your cache cluster.
3. Because all operations go through the backend service, the existing telemetry, logging and monitor tools are still applicable. However it cold be a good idea to include more metrics counters to provide fine-tuned perf info.
4. There will be more blog articles and video introductions coming out. Keep tuned!
Thank you!
Meet WACEL
Nov 13, 2013 at 2:47 PMThank you for your interests in WACEL! WACEL is designed to make common scenarios easier. If you have any scenarios that you think that WACEL could be helpful, please feel free to reach out to us by sending a mail to hbai@microsoft.com.
Windows Azure Cloud Services Concepts (Part 1)
Feb 26, 2013 at 1:22 PM@11111111: Yes. Your customers access your services via endpoints, and traffic will be distribute across your roles in a round-robin fashion.
Windows Azure Cloud Services Role Lifecycle
Feb 24, 2013 at 6:28 PM@mohandeval2: Thank you for your feedback. We'll see if we could fix it.
Using the Request-Acknowledge-Push Pattern to Display Progress of Long Running Tasks
Feb 01, 2013 at 10:50 AMLOL. Sorry for the typo. Fixed now
Using the Request-Acknowledge-Push Pattern to Display Progress of Long Running Tasks
Jan 31, 2013 at 2:06 PMHi PeterNL: Thank you for comment. We have a couple of episodes being edited at the moment and we are recording more. This is a new series and there are still some details we need to work out. So we might be slow in releasing the first few episodes.Thank you for your patience, and please keep tuned! And if you and anyone else in the community want to share your experiences you are welcome to contact me at any time.
Using the Request-Acknowledge-Push Pattern to Display Progress of Long Running Tasks
Jan 21, 2013 at 10:30 AMSource code link is fixed.
Using the Request-Acknowledge-Push Pattern to Display Progress of Long Running Tasks
Jan 18, 2013 at 5:49 PM@peternl: Thank you for your kind comment. I've added source code link to the post. We'll have more episodes coming very soon, keep tuned
.
Advanced Cloud Services Development
Nov 07, 2012 at 10:54 AMHere's the link to the Fireworks demo I mentioned but didn't have time to show during the session:
http://haishibai.blogspot.com/2012/11/play-fireworks-together-process-of.html
Announcing Microsoft’s U-Prove Community Technical Preview (CTP)
Mar 13, 2010 at 9:53 PMAn e-commerce transaction is not completed until the actual merchandise has been shipped. However to get the goods to be shipped people are forced to disclose their real addresses to online venders. Here’s my two cents – an anonymous shipping system. Basically a user will pick one trusted carrier such as UPS and get a token that represents her address. Then when she’s purchasing online, she’ll give the token to the vender instead of a real shipping address. The vender can call to UPS service to validate the token and get shipping cost estimation (or the token can have zip code in it for cost estimation), but the vender never knows where the product is shipped to. The token can be static or dynamic – user can apply new tokens any time. I’m not sure if U-Prove consider the scenario like this?