Can we perform below task on Windows Azure Media Service that is
storing, Retrieving,maintaining Version of Video, Permission handling, Searching for the video
for each tenant on the SaaS environment
Currently Azure Media services providing infrastructure to ingest, encode and deliver media assets. Complex metadata, versioning, access control and additional content management functionality can be extended by third party providers or in your application.
Short answer that for now Windows Azure Media Service is not positioned as CMS system with listed in your question functionality.
You can use Asset.AlternativeId to store any keys from external system which can be built on top of Windows Azure Media Service.
Related
I am reading about and then trying to use IBM Bluemix. I have seen some confusing statement about MBaaS support on Bluemix. Some sites mention that Bluemix is a PaaS, and some places say it supports MBaaS. I have basic doubts: does IBM support MBaaS? If yes, where can I find the full MBaaS features list for IBM Bluemix? I couldn't find it in IBM site.
You're correct: Bluemix is a PaaS. However as you probably know and as you can see here:
Mobile backend as a service (MBaaS) enables you to quickly integrate
your mobile apps with data and functions in security-rich, backend,
cloud storage. MBaaS is usually delivered through a set of custom
software development kits (SDKs) and application programming
interfaces (APIs). MBaaS can offer you full data synchronization, user
management, push notifications, integration with social networking
services, and file-handling.
A PaaS provides SDKs and APIs and for this reason it can support MBaaS. In Bluemix the MBaaS capabilities are provided by the MobileFirst platform. It is designed for building and enhancing multiplatform, enterprise-grade apps that can be native or hybrid – for Android, iOS, and Windows. You can get started here.
Yes, Bluemix Mobile supports a Mobile Backend as a Service.
Here are the current services that we have that support the MBaaS pattern and a bit of information about them (and here's a quick graphical view and some links for how to get started):
Mobile Client Access
This service enables you to secure your Mobile Application. You can add Facebook, Google, or custom authentication to your application.
Push Notifications
You can add the Push Notifications service to send push notifications to your app on Android and iOS.
Mobile Analytics (Beta)
The Mobile Analytics service enables you to gather crash and usage knowlege about customers using your mobile app.
Cloudant NoSQL DB
The Cloudant service is the IBM NoSQL database to store your data.
Object Storage
The Object Storage service is an unstructured cloud data store where you can store things like images or files.
Mobile Foundation
The catalog also includes the Mobile Foundation service which you can use to create a test environment before deploying or purchasing the on-premise software. This service is another way for enabling a developer to create a mobile channel.
You may have a look at this :
http://www.ibm.com/mobilefirst/mobile-backend-as-a-service/mbaas.html
I am trying to port my Android application into a Cloud based one. Where I wanted the data stored in cloud. I am a .NET guy so looking into Azure. I see Azure Mobile services which allows me to create tables and ability to authenticate. I also Looked into Azure SQL database.
I would like to know what is the difference between these two services and what are the scenarios using mobile services gives values than using Azure SQL database
Actually, the tables you see listed in Azure Mobile Services are actually tables that are in an Azure SQL Database instance. The Mobile Services provides an abstraction layer on top of the tables in SQL Server. If you use the current JavaScript back-ended mobile services you'll see the table in the management portal and it uses the dynamic nature of JavaScript to provide what appears to be a NoSQL like experience with Azure SQL DB in that you can send in an object and properties it doesn't recognize will be added to the table schema (you turn this off when you ship to production :) ). The big thing to remember is that under the hood the database is an Azure SQL DB, so you should have access and do anything via the one created by Azure Mobile Services as you can with the raw Azure SQL DB.
By using Azure Mobile Services you get an API hosting layer that you can use to do direct access to the tables (based on the permissions you hinted at) but also to just about anything utilizing the custom API feature.
If you chose to bypass the Azure Mobile Services you'd likely want to have some API layer between your Android app and the data for a variety of reasons (security, abstraction of data location, etc.). In which case you'd have to write and host that API layer somewhere. Other options within Azure would be a Web API site in Azure Web Sites, an API hosted in an Azure Cloud Service or all the way up to an Azure VM; however, as you slide up that scale you're taking on more and more responsibility and work.
The scenario that is useful to use Azure Mobile Services over the Azure SQL DB is pretty much the scenario you have. You don't have to maintain your own hosting API layer, just the code the API layer executes. You can scale an necessary (to a very large scale indeed) and also get features like the push notifications and web jobs (though those are also things you can do via other services in Azure if you'd like). Thinks of Azure Mobile Services as a higher level grouping of Azure services that are helpful to mobile developers.
Mobile services provide you with built-in push notification features and other such mobile friendly features too. They are more mobile oriented in a way.
I have a Windows 8 app that I want to connect to a WCF Service hosted on Windows Azure - easy.
The tricky part is that I want to allow only Authenticated users (via their windows live account) to access my service, including being able to pass a unique identifier to the service to identify the user on the Azure hosted app.
All of this plumbing is available when you use Azure Mobile Services, but surely there must be a solution for a regular WCF app within azure.
Azure Mobile Services has a MobileServiceClient type that has all of the required functionality, but I need a regular Azure-hosted WCF equivalent
You can try pulling some of the content from the now deprecated Windows Azure Toolkit for Windows 8. For the moment the Release Preview version is available; it won't work as is since it's pre-RTM, but it should help jumpstart your effort.
I'll re-emphasize though that it's not supported and Windows Azure Mobile Services is the plan of record.
I have SOAP services with data. I want to download all data from that service and upload it to my own server and then use these data from my server (don't worry I have permission for that). I want to do it because now I don't have function from that service which I need.
I want to use Windows Azure for this and I think SQL Database scenario would be best. Now I have classes for previous SOAP service so I think EF Code first would help me with creating database and I upload data somehow. But what about API? How can I access my data from windows phone or tablet? Is azure database enought or I must create more? Is there any good article for that?
I think what you are saying, is that you are aggregating data from several sources and storing the information in your own database. And, you would like your database to be Azure Database. Then, you want to build an API to expose the data you retrieved.
If this is indeed your goal, then yes, Azure will do everything you need. I'd recommend checking out Web API in conjunction with your Azure deployment. I've used this scheme with some success over the past year.
Warning: You should know that Azure Database does not have an SLA which means that Microsoft does not guarantee any level of performance including transactions/second. This means that if your API has a high load, you could end up getting throttled heavily in an unpredictable way. I've been bitten by this before and ended up moving my data to Azure Table Storage instead.
Windows Azure gives you a few options to expose an API to your mobile clients:
You could build an API yourself with the ASP.NET Web API (and use SQL Azure as backend): Mobile-friendly REST service using ASP.NET Web API and SQL Database
You can use Windows Azure Mobile Services, this does all the heavy lifting of building a backend for you
I am to implement a service such the user can upload files to azure storage, and also store the meta data in a azure sql database.
Lets say the user want to upload 1gb of data, is it then needed to be send to the webservice first and then from service to azure storage? Is there a way to initiate the upload and then the user sends the data directly to the server with azure storage?
I think i read something like that but cant find it now and not sure what to search for on google.
Yes this is possible but you'll need to use a client side technology which can talk to the REST API, like Silverlight for example. Steve Marx did a series of blog posts explaining how you can leverage Silverlight and the REST API to upload files to blob storage (even very large files): Uploading Windows Azure Blobs from Silverlight – Part 3: Handling Big Files by Using the Block APIs. And a Silverlight control is very easy to integrate in an existing website.