März 2022 - Seite 21 von 46 - Cloud Computing Köln

Azure API Management is a fully managed service that enables customers to publish, secure, transform, maintain, and monitor APIs. With a few clicks in the Azure portal, you can create an API facade that acts as a “front door” through which external and internal applications can access data or business logic implemented by your custom-built backend services, running on Azure, for example on Azure App Service or Azure Kubernetes Service, or hosted outside of Azure, in a private datacenter or on-premises. Azure API Management handles all the tasks involved in mediating API calls, including request authentication and authorization, rate limit and quota enforcement, request and response transformation, logging and tracing, and API version management.

Azure API Management helps you in:

Unlocking legacy assets—APIs are used to abstract and modernize legacy backends and make them accessible from new cloud services and modern applications. APIs allow innovation without the risk, cost, and delays of migration.
Create API-centric app integration—APIs are easily consumable, standards-based, and self-describing mechanisms for exposing and accessing data, applications, and processes. They simplify and reduce the cost of app integration.
Enable multi-channel user experiences—APIs are frequently used to enable user experiences such as web, mobile, wearable, or Internet of Things (IoT applications. Reuse APIs to accelerate development and return on investment (ROI).
Business-to-business (B2B) integration—APIs exposed to partners and customers lower the barrier to integrate business processes and exchange data between business entities. APIs eliminate the overhead inherent in point-to-point integration. Especially with self-service discovery and onboarding enabled, APIs are the primary tools for scaling B2B integration.

We are happy to announce the preview of Azure Private Link support for Azure API Management service. If you are not familiar with Azure API Management, when you deploy this service, you get three main components: Azure portal, gateway, and management plane. With Azure Private Link we can create a private endpoint for the gateway component, which will be exposed through a private IP within your virtual network. This will allow inbound traffic coming to the private IP to reach Azure API Management gateway.

Azure Private Link

With Azure Private Link, communications between your virtual network and the Azure API Management gateway travel over the Microsoft backbone network privately and securely, eliminating the need to expose the service to public internet. To learn more about Azure Private Link technology and platform as a service (PaaS) services that support it, you can review our Azure Private Link documentation.

Key benefits of Azure Private Link

Through this functionality we will provide the same consistent experience found in other PaaS services with private endpoints:

Private access from Azure Virtual Network resources, peered networks, and on-premises networks.
Built-in data exfiltration protection for Azure resources.
Predictable private IP addresses for PaaS resources.
Consistent and unified experience across PaaS services.

Private endpoints and public endpoints

Figure 1: Architecture diagram depicting the secure and private connectivity to Azure API Management Gateway—when using Azure Private Link.

Azure Private Link provides private endpoints to be available through private IPs. In the above case, the contoso.azure-api.net gateway has a private IP of 10.0.0.6 which is only available to resources in contoso-apim-eastus-vnet. This allows the resources in this virtual network to securely communicate. The other resources may be restricted to resources only within the virtual network.

At the same time, the public endpoint for the contoso.azure-api.net gateway may still be public for the development team. In this release, Azure Private Link will support disabling the public endpoint, limiting access to only private endpoints, configured under Private Link.

How to decide which networking model to use with Azure API Management?

Azure API Management also supports virtual network injection, allowing all components to be deployed inside a virtual network. With the addition of private endpoints, we have the following options for integrating inside a custom Azure Virtual Network:

Network model

Supported tiers

Supported components

Supported traffic

Virtual network—external

Developer and Premium.

Azure portal, gateway, management plane, and Git repository.

Inbound and outbound traffic can be allowed to internet, peered virtual networks, Express Route, and VPN S2S connections.

Virtual network—internal

Developer and Premium.

Developer portal, Gateway, Management Plane, and Git repository.

Inbound and outbound traffic can be allowed to peered virtual networks, Express Route, and VPN S2S connections.

Private endpoint connection (preview)

Developer, Basic, Standard, and Premium.

Gateway only (managed gateway supported, self-hosted gateway not supported).

Only inbound traffic can be allowed to internet, peered virtual networks, Express Route, and VPN S2S connections.

At this moment, these three options are mutually exclusive, you cannot choose a virtual network integration option (external or internal) in combination with private endpoint connections. Also notice that only our managed gateways will support private endpoint connections, the Self-Hosted Gateway does not support private endpoints in Azure.

Preview limitations

During the preview period, we will only support inbound traffic coming to the gateway, instances using STV2 compute platform, all pricing tiers except consumption, and Azure Private Link is limited to instances that are not using virtual network injection (internal or external). The feature will move to general availability as we assess feedback.

With the preview of Azure Private Link for Azure API Management, you are now empowered to bring your Azure API Management instances to a virtual network using the same consistent experience of other Azure PaaS services. You can create and manage private endpoints for the gateway of your Azure API Management instance. We will be sharing more updates and content in the future, so stay tuned for new updates towards the general availability of this feature.

Learn more

About Azure API Management.
Documentation on how to connect privately to API Management using a private endpoint.
Documentation on Azure Private Link.

Quelle: Azure

17. März 2022

da Agency

Speed boost achievement unlocked on Docker Desktop 4.6 for Mac

Introducing virtiofs

The 4.6 release of Docker Desktop for Mac contains a number of changes that drastically improve file sharing performance for macOS users. Firstly, developers now have the option of using a new experimental file sharing implementation called virtiofs (the current default is gRPC-FUSE). Secondly, improvements have been made to the way that files are synced between the macOS host and Docker VM. During testing with our amazing macOS community of users, we have observed that these changes have reduced the time taken to complete filesystem operations by up to 98%.

For developers, these incredible gains in speed mean less time waiting for filesystem operations to complete (or building project-specific workarounds to improve performance) and more time focusing on innovation!

Understanding common developer workflows

A common developer workflow when using technologies like Symfony or React is to edit source code located on the macOS host while running the app itself in a Docker container. The source code is shared between the host and the container by using Docker volumes, with a command like the following:

docker run -v /Users/me:/code -p 8080:8080 my-symfony-app

This allows the developer to edit their source code, save the changes and immediately see the results in their browser. Changes made to files located on the host system must propagate quickly and reliably to the container file system for the developer to optimize productivity and have a good user experience. This is where file sharing performance is absolutely critical.

Big performance improvements

Performance is vital when application source code is shared between the host and container. For example when a developer uses the Symfony PHP framework, edits the source code and then reloads the page in the browser, the web-server in the container must re-read many PHP files stored on the host. When considering that modern dependency management can easily bring 10k – 100k files into a project (which linearly increases the performance penalty), this can result in poor performance as the host and container keep in sync via the volume.

The recent changes to Docker Desktop for Mac, including the usage of virtiofs, alleviate this problem and bring drastic improvements to file system performance. Specifically, developers working with an early preview of Docker Desktop 4.6 with virtiofs enabled and changes to file syncing included have observed:

A 90% improvement in the time taken to complete a 284MB MySQL import (3m 16s to 18s)An 87% improvement in the time taken to run ‘composer install’ in a large codebase (1m 27s to 11s)An 80% improvement in the time taken to boot a monolithic Typescript app (1m 30s to 18s)

And here are some of the comments we’ve heard from users:

“This works great on my mac mini M1!, running migrations on my laravel instance is now instant…instead of running for minutes.” (Source: Github user feedback)“My development setup is ridiculously fast now. Thanks everyone!” (Source: Github user feedback)“Looking forward to seeing this enhancement land in a released build. It was like night and day! .” (Source: Github user feedback)

How to enable virtiofs

Virtiofs is only available to users of the following macOS versions:

macOS 12.2 and above (for Apple Silicon)macOS 12.3 and above (for Intel)

To enable virtiofs in Docker Desktop:

Ensure that you are using Docker Desktop version 4.6, available hereNavigate to ‘Preferences’ (the gear icon) > ‘Experimental Features’Select the ‘Use the new Virtualization framework’ and ‘Enable VirtioFS accelerated directory sharing’ togglesClick ‘Apply & Restart’

Your feedback is needed!

Virtiofs is accessible today within Docker Desktop for Mac (version 4.6) and available to all users including Docker Personal free users as well as Docker Pro, Team and Business paid subscription users.

Please download it, give it a try and let us know how it goes. If you discover any problems, please report them on the Mac filesystem performance thread on our public roadmap. For the moment, we are aware of an outstanding issue where containers running with virtiofs can fail due to permission errors. We have released a fix for this in an experimental Desktop build to the Mac filesystem performance thread and will confirm its stability in the coming days.

Likewise, we’re always interested to hear of any performance benchmarks that you may use to test out virtiofs !

Download button for Desktop 4.6

Thanks to our macOS community

We’d like to say a massive thank you to our macOS community of users for providing brilliant feedback and testing out the feature so rigorously. In particular, the excellent analysis of file system performance conducted by Konstantinos Tsanaktsidis led to valuable insights around file syncing.
The post Speed boost achievement unlocked on Docker Desktop 4.6 for Mac appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/

16. März 2022

da Agency

Docker: Nine Years YOUNG

Nine years ago today, March 15, 2013, Solomon Hykes, the founder of Docker, first demoed Docker publicly to the world at PyCon. On stage Solomon noted that, for developers, “shipping to the server is hard,” and thus he and the early team designed Docker to help developers more easily build, share, and run any app, anywhere. The rest, as they say, is history.

Fast forward to today, and thanks to Solomon, hundreds of Docker employees past and present, and millions of developers, community members, contributors, customers, and partners, we are able to celebrate Docker’s ninth birthday and can look forward to many more to come. And while our journey these last nine years has been anything but a straight line, our re-focusing in 2019 on the needs of developers is starting to bear fruit across our community, product, customers, and business.

Sustainably growing Docker was the critical desired outcome of our re-focusing in 2019. The changes we’ve made to our product, pricing, and licensing since then have enabled us to sustainably grow the business while continuing to grow the Docker developer community. To wit, growing sustainably enables us to continue to serve 100% for free 10 million registered Docker developers, 35 million Docker Engine downloads / month, 14 PB of container image storage, 31 PB / month in container image network egress, and much more.

In addition to investing in the community, sustainably growing our business enables us to increase our investment in our product for developers. Since 2019, you’ve seen us consistently deliver against our public product roadmap – most recently Docker Desktop for Linux and a 6X improvement in performance in Docker Desktop for Mac – and there’s much more to come! Be sure to swing by the Docker Community All Hands on March 31 for more birthday celebrations and exciting announcements, and there’s even more to share at DockerCon on May 10.

Happy ninth birthday, Docker community! Here’s to many more years in which we together build, share, and run!

DockerCon Live 2022

Join us for DockerCon Live 2022 on Tuesday, May 10. DockerCon Live is a free, one day virtual event that is a unique experience for developers and development teams who are building the next generation of modern applications. If you want to learn about how to go from code to cloud fast and how to solve your development challenges, DockerCon Live 2022 offers engaging live content to help you build, share and run your applications. Register today at https://www.docker.com/dockercon/
The post Docker: Nine Years YOUNG appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/