I remember Azure Data Catalog V2 will be released soon which has the Data lineage features but I could see the same kind of service was introduced recently as Purview. Could you please shed some light on differences and when to choose these services?
You can think Purview as the next generation of Azure Data Catalog, and with a new name. There will be no ADC v2, Purview is what Microsoft earlier talked with name ADC v2. Microsoft aims to profile it a bit differently and this way the new name is logical for many reasons:
Featurewise Purview is much richer.
There is no upgrade path from ADC to Purview.
Pricing model for these products is different.
ADC will be available for old customers yet for long time.
Many have been disappointed with the features and lack of development progress for ADC. I assume Microsoft hopes that the new name does not carry this old weight.
The roadmap for ADC has been unknow, or dead, for long time. I personally have used it years ago and cannot recommend. I recommend using Purview for all new data cataloging and governance use-cases. It integrates with modern Azure data services and Microsoft is actively developing it forward.
Related
I was reading and found a very nice service in Azure called "Azure Container Apps", but i found it in (Preview).
What does it mean, like i have some doubts:
Can i consider this for a production releases ?
Does it affect the SLA ?
How long time is usually takes to stay in Preview ?
Azure may include preview, beta, or other pre-release features, services, software, or regions offered by Microsoft ("Previews"). Previews are licensed to you as part of your agreement governing use of Azure.
Pursuant to the terms of your Azure subscription, PREVIEWS ARE PROVIDED "AS-IS," "WITH ALL FAULTS," AND "AS AVAILABLE," AND ARE EXCLUDED FROM THE SERVICE LEVEL AGREEMENTS AND LIMITED WARRANTY. Previews may not be covered by customer support. Previews may be subject to reduced or different security, compliance and privacy commitments, as further explained in the Microsoft Privacy Statement, Microsoft Azure Trust Center, the Product Terms, the DPA, and any additional notices provided with the Preview. The following terms in the DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and HIPAA Business Associate. Customers should not use Previews to process Personal Data or other data that is subject to heightened legal or regulatory requirements.
Certain named Previews are subject to additional terms set forth below, if any. These Previews are made available to you pursuant to these additional terms, which supplement your agreement governing use of Azure. We may change or discontinue Previews at any time without notice. We also may choose not to release a Preview into "General Availability".
Source (and more information): Supplemental Terms of Use for Microsoft Azure Previews.
In short, to me the answers to your questions would be:
Yes, you can... however. It might mean you need to take into account that stuff might break or change and prepare for that.
It does (read above)
That completely depends on the service
If you want to stay up to date with services, Previews, General Availability and more, see Azure updates.
Some Preview services are more Preview than others. There have been Preview services in the past, where you could be pretty sure it would most probably propagate into it being a full blown Azure service in the future. And then there are services that are in early Preview that will probably have some big changes before moving to GA, if they are moving there at all.
As far as Container Apps goes: I think Microsoft hit a sweet spot between Kubernetes and App Services with Container Apps. I think chances of it not moving to general availability are close to zero.
Also, Microsoft Build is just around the corner (May 24th to 26th 2022). These are normally the times quite a few new Preview services are announced, or existing ones move to GA.
EDIT:
For a product roadmap on Azure Container Apps, please see its GitHub repo.
Azure offers preview features to you for evaluation purposes. A preview may include preview, beta, or other pre-release features, services, software, or regions. Previews are subject to reduced or different service terms, as set forth in your service agreement and the preview supplemental terms -https://azure.microsoft.com/en-us/support/legal/preview-supplemental-terms/ . Previews are made available to you on the condition that you agree to these terms of use, which supplement your agreement governing the use of Azure.
It always safe and recommended to use previews only for testing or evaluating a service and not on productions, as they are not stable services and are subjected to change.
Azure Container Apps is now generally available. No longer in preview: https://techcommunity.microsoft.com/t5/apps-on-azure-blog/azure-container-apps-general-availability/ba-p/3416885
Since ADC is provided by MS as SaaS to customers, is MS taking backups of the dataset and business glossary? If yes, how often and how can a customer get access to the backups for recovery purposes?
Unfortunately, there is no explicit backup/restore feature available for catalogs.
I would suggest you to vote up an idea submitted by another Azure customer.
https://feedback.azure.com/forums/906052-data-catalog/suggestions/33125845-azure-data-catalog-backup-feature
All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.
The closest way to achieve this with current functionality is to use the Azure Data Catalog REST API to extract all assets and persist them locally (and re import them manually later).
There is a sample application available that demonstrates this technique: Data Catalog Import/Export sample tool.
I've been researching the new unified API for office365 (graph.microsoft.com). Currently one can authenticate to it using an organisationalID and it will return information from emails-from-exchange/OneDrive4Business/Skype4Business(future)/calendar-from-exchange/exchange-contacts/etc...
The ability to surface such a plethora of information from one endpoint strikes me as being hugely valuable. In the future I'd really like to see information relating to Azure be surfaced in here also. For example, I'd love to use graph.microsoft.com to access lists of:
Azure storage accounts
Azure SQL DB servers and databases
Azure SQL DB firewall rules
Azure ML experiments
Countless other things
Are such things on the roadmap?
That is a great question, and it's great to see such enthusiasm around a single endpoint surfacing this information. We're not sure when Azure resource providers would be a part of the unified API, but it would be great to have them. There are a number of other teams who are very interested, and in general we've been pretty focused on user or person centric developer experiences here as you should be able to see from Yina Arena's //Build or Ignite presentations.
What guarantee does Microsoft give to providing long term support for Azure? If Microsoft was to shutdown Azure how long would they keep the Azure cloud up and running? Has anyone regretted using a SQL Azure feature as it harmed their ability to move off of SQL Azure?
OK. A few questions there. Some can really only be answered officially by Microsoft but I'll take a stab at providing at least some detail for you.
1. What guarantee does Microsoft give to providing long term support for Azure?
Microsoft commit to providing at least 12 months notice for any disruptive change. This is set out in their Online Services Support Lifecycle document. http://support.microsoft.com/gp/OSSLpolicy
2. If Microsoft was to shutdown Azure how long would they keep the Azure cloud up and running?
Per the above. I would consider that a disruptive change and expect them to provide a minimum of 12 months notice.
3. Has anyone regretted using a SQL Azure feature as it harmed their ability to move off of SQL Azure?
There are very few features that are only available in SQL Azure. IN terms of shipping features I can only think of Federations off the top of my head. It's a unique feature in that it's only somewhat interesting for on-premise deployments as you don't typically have elastic capacity on tap on premise and you can probably take other approaches such as a monolithic DB server + storage partitioning to solve your problems. In short I haven't had such regrets.
There are many Azure projects on codeplex and scattered over MSDN. Some of them are so old that they use the code-based version of the storage client, and not the compiled version.
Which projects are current and relevant, and which are outdated?
Getting Started with Azure
http://blog.syntaxc4.net/post/2010/12/30/Essential-Resources-for-Getting-Started-with-Windows-Azure.aspx
Current and by MSFT:
MSDN Samples
Part 1 Demonstrates COMET via Silverlight and WCF among other samples
Part 2 Includes HTTP compression sample
How to... In Azure
Some entries contain code samples
http://msdn.microsoft.com/library/gg432998.aspx
FabrikamShipping
Includes AD FS Federation, Facebook integration, and provisioning automation
http://blogs.msdn.com/b/vbertocci/archive/2011/03/14/fun-with-fabrikamshipping-saas-ii-creating-an-enterprise-edition-instance.aspx
Azure SDK
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7a1089b6-4050-4307-86c4-9dadaa5ed018
Azure Training Kit
Located at C:\WAPTK\Default.htm
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=413E88F8-5966-4A83-B309-53B7B77EDF78
Patterns and Practices
Cloud Guidance (Greenfield and Brownfield scenarios)
Tailspin Toys Hands On Lab
Note there is a part 1 and part 2 to this
http://wag.codeplex.com/
Developing applications for the cloud
http://msdn.microsoft.com/en-us/library/ff966499.aspx
All In One Samples
Has some Azure samples for oData and more. See both the 2008 and 2010 samples since each has different code.
http://1code.codeplex.com/
WCF Azure Samples
(looks up to date, but is located on "archive.msdn" which is disconcerting )
http://archive.msdn.microsoft.com/wcfazure
http://code.msdn.microsoft.com/windowsazure/
3rd Party up to date
Encryption for Azure Table
Easily and transparently encrypt Table data
http://azuretableencrypt.codeplex.com/
Lokad.Cloud
An ORM for the cloud aka O/C mapper
http://code.google.com/p/lokad-cloud/
Facebook
http://facebooksdk.codeplex.com/
http://azuretoolkit.codeplex.com/
Azure Storage
http://azurestorageexplorer.codeplex.com/ (Oct of '10)
Azure Accelerators
http://azureaccelerators.codeplex.com/
Aside from makerofthings7's thorough answer, let me add one more:
David Pallman's 'Azure Storage Samples' - these are complete samples with two implementations each: .NET Storage Client Library and REST. This was published in February, 2011.
A project that probably contain all the providers you will ever need; Membership, Role, Session, and Profile providers. Stores in the Azure Table Storage and uses the Azure Queue http://azureproviders.codeplex.com