I am exploring ways to improve some of our processes and applications using microsoft tools and more specifically the Custom Vision Cognitive Service. However, i am getting lost in the MS offerings and the Preview AI Builder service in PowerApps which seems to be offering the same capability.
The test that I am trying with both services i using Products pictures and utilize the services to provide me with the brand, sub-brand and some other specifications on the product. To start with, i have started with the browser version of the Custom Vision service (not the SDK) which, because it is a non-programmer interface, is really similar to the AI builder.
Has someone more inputs on the strategy behind the AI Builder in Powerapps and how it complements/replaces some of the capabilities of the MS cognitive services (and more specifically their browser/non-programmer versions)?
In a few words, tools in PowerApps (like in Microsoft Flow or even Logic Apps) are backed by other (more technical) services provided by Microsoft (or third party).
PowerApps and Flow are solutions designed to be used by non-developer people: understanding the technical behaviour / implementation is not needed.
Using AI Builder service in PowerApps vs Custom Vision: generally, there may be a delay between new technical features and the time they are provided in those tools for example. Some features are also never available in "business" versions.
Related
Anyone know the future of Azure Blueprints? Is Microsoft embracing Terraform as a replacement? I don't mind ARM templates just trying to get a sense of the future for managing infrastructure.
I currently use ARM and Blueprints to manage our Azure subscriptions and infrastructure but I have been seeing a lot of posts around Terraform in relation to Microsoft and Azure.
I have also looked into other tools such as Bicep and Pulumi but right now I more interest in what the planned future for Blueprints is.
Future or roadmap of Azure Blueprints:
Most of the Blueprint resourcing is going towards Template Specs (video overview) and Deployment Stacks, which is what Blueprints are eventually going to use under the covers. For authoring improvements, focus is bicep. The GA (General Availability) ETA is set for March/April when the new underlying resource types (template specs and deployment stacks) are ready and we can migrate everything over.
More info in this talk:
Blueprints migration plan
Deployment stacks overview
Most of the Blueprint UserVoice asks are either already implemented in Templates/Template Specs, or they are something we will address with above mentioned future improvements to templates/bicep and stacks.
Lastly, even though the Blueprint service is listed as “Preview”, we treat the service as GA, which means even once a migration path is made available, we will continue to support the current Blueprint APIs for 1-3 years or until everyone has been migrated.
Source of above information: https://learn.microsoft.com/en-us/answers/questions/177308/index.html
I am evaluating wep api gateway for my new projects. I used azure api gateway in the past. Reading about nginx as it is new and adopted by many. Can someone help me point out with some facts, pros, cons? Bug matrix will be a best help for me
Azure API Management is a mature and widely-used product, with many customers being very respected enterprises. Take a look at some public case studies.
It offers a very wide range of features, which are typical of an API management platform, and it is still being very actively developed. However, one of its biggest strengths lies in integration with Microsoft Azure services and features - multiregional deployments, virtual networks, monitoring and alerting solutions, native support for Service Fabric, Azure Function Apps and Azure Logic Apps, Azure Active Directory and others.
If you are considering hosting your new projects with Microsoft Azure, Azure API Management is a no-brainier.
The product is also one of the main reasons why Gartner named Microsoft a leader in the enterprise integration space.
Disclaimer: Although all of the above is best to my knowledge, I am affiliated with Azure API Management.
Although I have just started looking into this myself, here's what I can already conclude.
Looking at www.nginx.com/blog/deploying-nginx-plus-as-an-api-gateway-part-1/, Nginx requires a lot of manual configuration washed over many text files. That doesn't look flexible or effective, but I may have gotten a wrong impression.
Judging by how you're supposed to define your API keys using the map directive, Nginx API Gateway also looks like a new idea stretched on top of the existing product, while Azure API was designed for that exact purpose from the ground up.
Azure APIs, when published, come with auto-generated documentation and an interactive console that are in sync with all your updates.
With Azure API, you're putting all your eggs into one basket and completely depending on it's pricing and availability. At any moment Microsoft can increase their prices, or discontinue the product, and you cannot migrate elsewhere, at least not easily/quickly. At the same time, you can do your Nginx work once and run it on pretty much any server, starting with a low-end VPS or a Raspberry PI, if you'd like. It's pretty much yours.
I am trying to a good comparison between AppDynamics and Application Insights in regard to Azure App Service.
I tried to google around but couldn't find any good comparison, if someone can point me or summarize here.
Information I got from another website.
Application Insights (AI) is a very simplistic APM tool today. It does do transaction tracing, it has very limited code and runtime diagnostics, and it doesn’t go very deep into analyzing the browser performance. Application Insights is much more like Google Analytics than like a typical APM tool.
AI does not support mobile apps, AppDynamics does Android and iOS
AI only supports Java, .NET, and node.js while AppDynamics supports many
additional languages and technologies.
AI requires code changes to do additional metric capture from the
code. AppDynamics has do this on the fly without code change on most
languages.
AI doesn’t so transaction distributed tracing, it has a simple data
collection model similar to what New Relic does. This makes
troubleshooting much harder in complex apps. If your app is simple
it’s not required.
AI lacks transaction scoring and baselining, you must set manual
thresholds. AppDynamics does this for every metric and every business
transaction.
AI doesn’t monitor databases or data stores. AppDynamics does both.
AI is SaaS only, while AppDynamics can be deployed on premises or
SaaS.
I've been asked to develop a .NET web application with the following requirements and features:
Moderate software license expenses
.NET Web Application
Document storage (with change history, although a complete CMS is not needed)
Complex data model
Extensible and groupable object attributes
Private/public field visibility
Non-trivial relationships between database tables
Custom alert configuration (screen and e-mail notifications) about approaching due dates, missing documentation, etc.
Resource access control & user management (roles and groups)
High user volume (several thousands of users)
Many complex and dynamic forms
Search engine
Statistical reporting
Bulk data & metadata upload and download
Simple data migration
REST API for external integration
Multilanguage
Full-featured mobile version (for tablets and smartphones)
Corporate look and feel
These are the options I have considered:
SharePoint Foundation 2013 + Custom Web Parts + Custom DB + Document Libraries
Sense/Net + Custom Web Parts + Custom DB + Document Libraries
Custom ASP.NET Web Application
What approach would you recommend? Also, can you please make a recommendation on the following points?
Server characteristics and topology
Application architecture
Scalability
Search capabilities
Reporting tools
Persistence framework
Document storage (MS Office)
Mobility
First of all, I work for Sense/Net, which I want to put out there to be fair.
However, even if I wouldn't be, I'd still recommend looking at our solution based on the criteria you outlined. What you are planning to build seems to be really custom stuff and from experience, I can say that projects like this never changing. Going for an open-source application would definately be my choice, in order to make sure I don't hit a wall later down the line.
Sense/Net is practically capable of delivering everything you need out of the box, but of course, customization will be needed.
From a licensing perspective, you would also be better off probably, since we only lincense the CPU cores, not the thousands of users benefitting from the system.
Writing a custom application from scratch with these requierements would make no sense in my opinion as the costs would be well over the one of a readymade solution (whichever you choose).
The things need to be clarified are the reporting tools you will need and whether you need a native application for mobile devices (or would something working in their browsers would be sufficient).
I can see that this answer is well overdue, but if the topic is still of interest and you havent done so yet, drop us an e-mail through our website and we can help you out in finding the perfect solution!
I want to know the difference between multi-tenancy and single tenancy.
Is tomcat supporting mutli-tenancy .Can you explain both with an example.
I am asking this question in context to http-servers.
Definition
From Wiki definition
In a multitenancy environment, multiple customers share the same application, running on the same operating system, on the same hardware, with the same data-storage mechanism. The distinction between the customers is achieved during application design, thus customers do not share or see each other's data.
So you can imagine that single tenancy is the other way around.
Example
Let's take JIRA as an example,
If you use OnDemand JIRA Service, it is multi-tenant, cloud-based service.
If you download JIRA Standalone and install it for you organisation. It is single tenancy case.
Designing multi-tenancy software
Designing multi-tenancy software is nothing to do with the hosting technology. It's actually about the way you architect the software.
Tomcat in your case, is absolutely suitable for multi-tenancy software.