AWS Lambda macht es jetzt einfacher, Protokolle an benutzerdefinierte Ziele zu senden

Mit Hilfe von AWS Lambda Extensions können Sie jetzt Protokolle von AWS Lambda-Funktionen direkt an ein Ziel Ihrer Wahl senden. AWS Lambda Extensions sind eine neue Art der Integration von Überwachungs-, Beobachtungs-, Sicherheits- und Governance-Tools mit Lambda, und heute können Sie Erweiterungen verwenden, die Protokolle an die folgenden Anbieter senden: Datadog, New Relic, Sumo Logic, Honeycomb, Lumigo und Coralogix.
Quelle: aws.amazon.com

Amazon QuickSight bringt neue Diagrammtypen, Tabellenverbesserungen und mehr auf den Markt

Amazon QuickSight unterstützt jetzt Wasserfalldiagramme. Wasserfalldiagramme zeigen, wie jede Metrik durch eine Reihe von beitragenden Faktoren positiv oder negativ beeinflusst wird. Dashboard-Autoren können ein Wasserfalldiagramm erstellen, indem sie diesen neuen visuellen Typ aus dem Menü zum Bildmaterial auswählen. Hier finden Sie weitere Informationen.  
Quelle: aws.amazon.com

Helping media companies create consumer streaming formats with Transcoder API

Media and entertainment companies across the world are in the midst of a transformational shift to direct-to-consumer (D2C) streaming experiences. With audiences sheltering in place in 2020, this shift has been accelerated as audiences have adopted new streaming services more readily in 2020 than ever before. With more content being streamed in higher resolutions and operations becoming more distributed, media companies today require a cost efficient, high speed, and scalable way to process and deliver video content to an ever increasing number of end devices and platforms.Google Cloud is committed to building industry products and solutions that help media companies simplify operations and distribute their content to the widest possible audience. We’re building a set of video-focused APIs that empower developers to easily build and deploy flexible high quality video experiences. Today we’re announcing the first of these products, the preview availability of the Transcoder API. The Transcoder API is an easy-to-use API for creating consumer streaming formats, including MPEG-4 (MP4), Dynamic Adaptive Streaming over HTTP (DASH, also known as MPEG-DASH), and HTTP Live Streaming (HLS). Many D2C streaming platforms use a multi-codec strategy, and the Transcoder API supports popular codecs, including H.264, VP9, and HEVC. This strategy allows providers to offer a better, high definition experience to more viewers. The API also supports full partitioning for fast encoding of large video files, meaning that entire hours-long movies can be prepared in minutes.Developers can get started quickly by submitting transcoding jobs through REST API, transcoding files in Google Cloud Storage, and using Google Cloud CDN or third party CDNs to effectively distribute content to audiences across the globe. To learn more about the Transcoder API, please visit the documentation and pricing pages.Related ArticleHelping media companies navigate the new streaming normalAs media and entertainment companies evolve their future plans as a result of COVID-19, they should keep new audience behaviors top of mi…Read Article
Quelle: Google Cloud Platform

A developer’s guide to Google Kubernetes Engine, or GKE

When people think about whether or not to deploy on a container management platform like Kubernetes, the decision often comes down to its operational benefits: better resource efficiency, higher scalability, advanced resiliency, security, etc. But Kubernetes is also beneficial to the software development side of the house. Whether it’s improved portability of your code, or better productivity, Kubernetes is a win for developers, not just operators.For one thing, as we argued in Re-architecting to cloud native: an evolutionary approach to increasing developer productivity at scale, Kubernetes makes it easier to adopt modern cloud-native software development patterns like microservices, which can give you:Increased developer productivity, even as you increase your team sizes. Faster time-to-market – Add new features and fix defects more quickly. Higher availability – Increase the uptime of your software, reduce the rate of deployment failures, and reduce time-to-restore in the event of incidents. Improved security – Reduce the attack surface area of your applications, and make it easier to detect and respond rapidly to attacks and newly discovered vulnerabilities.Better scalability – Cloud-native platforms and applications make it easy to scale horizontally where necessary—and to scale down too. Reduced costs – A streamlined software delivery process reduces the costs of delivering new features, and effective use of cloud platforms substantially reduces the operating costs of your services. Google of course invented Kubernetes, which Google Cloud offers as the fully managed service, Google Kubernetes Engine (GKE). But did you know that Google Cloud also offers a full complement of developer tools that are tightly integrated with GKE? Today, in honor of KubeCon, we’re revisiting a few blogs that will show you how to develop apps destined for GKE, how to deploy them safely and efficiently, and how to monitor and debug them once they’re in production. Developing for GKE: It all starts with youEven the most enterprise-y applications get their start in life on a developer’s laptop. The same goes for applications running on GKE. To make that possible, there’s a variety of tools you can use to integrate your local development environment with GKE. Developers are known for tricking out their laptops with lots of compute resources. Using Minikube, you can take advantage of GPUs, for example. There are also local development tools to help you containerize Java apps: Jib, and Skaffold. Jib helps to containerize your Java apps without having to install Docker, run a Docker daemon, or even write a Dockerfile, and is available as a plugin for Maven or Gradle. Then, you can use Skaffold to deploy those containerized Java apps to a Kubernetes cluster when it detects a change. Skaffold can even inject a new version of a file into a running container! Read about this in depth at Livin’ la vida local: Easier Kubernetes development from your laptop.Another popular tool among GKE developers is Cloud Code, which provides plugins for the popular Visual Studio and IntelliJ integrated development environments (IDEs) to simplify developing for GKE. For example, we recently updated Cloud Code to have much more robust support for Kubernetes YAML and Custom Resource Definitions (CRDs). Read more at Cloud Code makes YAML easy for hundreds of popular Kubernetes CRDs. Have a quick and dirty development task to do? Check out Cloud Shell Editor, which launches a full-featured, but self-contained, container development environment in your browser. Read more at New Cloud Shell Editor: Get your first cloud-native app running in minutes.Related ArticleLivin’ la vida local: Easier Kubernetes development from your laptopRunning applications in containers on top of Kubernetes is all the rage. However, the brave new world of containers isn’t always kind to …Read ArticleGet in the (pipe)lineEventually, you’ll be ready to push the apps you developed on your laptop to production. Along the way, you’ll probably want to make sure that the code has been properly tested, and that it passes requisite security and compliance tests. Google Cloud offers a variety of tools to help you push that code through that pipeline. Setting up an automated deployment pipeline to GKE doesn’t have to be hard. In Create deployment pipelines for your GKE workloads in a few clicks, learn how to use Cloud Build to create a pipeline from scratch, including selecting your source, build configuration, and Kubernetes YAML files. But before you do, make sure that the image that you’re deploying is secure. Binary Authorization provides a policy enforcement chokepoint to ensure only signed and authorized images are deployed in your environment. You can read more about it in Deploy only what you trust: introducing Binary Authorization for GKE.Even better, Artifact Registry has built-in vulnerability scanning. Once enabled, all container images built using Cloud Build are automatically scanned for OS package vulnerabilities as they’re pushed to Artifact Registry. Read more at Turbocharge your software supply chain with Artifact Registry.Monitor, Debug, Repeat: Remote development for GKE appsNow that your app is in production on a GKE cluster, your work is done, right? Wrong. For developers, getting an app to production is still just the beginning of the software lifecycle. Chances are, you have ideas about how to improve your app, and you’ll definitely want to monitor it for signs of trouble. GKE is tightly integrated with several monitoring, debugging, and performance management tools that can help ensure the health of your GKE app—so you can make them even better!When there’s a problem in your production environment, one of the first places you’ll want to look is your logs. You can do that with Cloud Logging and Cloud Monitoring, both enabled by default when you create a GKE cluster. To learn more about how to use Cloud Logging for GKE logs, use cases and best practices, check out Using logging for your apps running on Kubernetes Engine.Once you’ve found the culprit, find out how you can use Cloud Logging and Cloud Monitoring to debug your applications.We’re developers tooAs long-standing leaders of the open source community, including the Cloud Native Computing Foundation (CNCF) and Open Container Initiative (OCI), we’re always thinking about how industry developments impact your day-to-day as a GKE developer. For example, Docker’s recent announcements about new limits on pull requests prompted us to write this post on how to manage these restrictions in a GKE environment. In addition to making GKE the most scalable and robust container management platform, we’re deeply committed to making it the easiest to use and develop on. New to Kubernetes and GKE? Learn more with this free, hands-on training. And if you’re participating in KubeCon this week, be sure to stop by our (virtual) booth to meet an expert.Related ArticleYour guide to Kubernetes best practicesOur entire Kubernetes best practices blog series in one location.Read Article
Quelle: Google Cloud Platform

Four ways to generate value from your APIs

It’s been 20 years since Jerry Maguire hit movie theaters in 1996, and yet one line from the movie still resonates like no other. The constant banter between the agent, Jerry Maguire (Tom Cruise) and budding professional football player Rod Tidwell (Cuba Gooding Jr.) is fun, if not bombastic, with one central theme that Tidwell not only enthusiastically expresses but also insists Maguire express as well:“Show me the money.”Tidwell’s passion for football was far outweighed by his passion to become rich; indeed, one of the movie’s themes is that only once he got past playing for the money could he achieve the level of play required to drive real value to his team, his team’s owners, and ultimately himself.What does this have to do with API management? Digital product owners tend to follow a similar path: the knee-jerk reaction is that the easiest way to drive value from APIs is to charge for them. While this may be the easiest thing to do, more often than not, API value is best extracted from other indirect means. By creating a tri-partite value exchange—a proposition that satisfies end users, partner developers, and the company publishing the APIs— a great amount of untapped value may be mined. And just like the football player, the agent, and the team, putting some heart into the game can make all three of them winners.How to start deriving value from APIsBehold: here are the four best practices to derive value from APIs:1. Extend channel reachSuppose your application is great but targeted toward a specific set of users. What if there’s a set of users—perhaps even an entire channel—that cannot use it? Perhaps your application doesn’t integrate well with other corporate systems, or perhaps it isn’t available in certain markets, doesn’t accept certain currencies, or can’t support certain business models (such as pre-paid or post-paid). Creating an API product—that is, an API designed for developer consumption and productivity, not just integration between systems—is the single best way to make your application flexible enough that the functionality can be adopted into channels that aren’t being addressed by your current go-to-market approach. An excellent example of this is the Walgreens Photo Prints API. As photos have moved from digital cameras to mobile phones, a cadre of third-party photo applications has cropped up…yes, pun intended. These applications took great pictures and featured wonderful effects but offered no easy way to print the photos. By leveraging the API and the connection it facilitated to Walgreens photo printing facilities in stores nationwide, these apps can now use Walgreens stores as a venue for photo printing. This has enabled customers to quickly get prints of their favorite photos, helped developers to build richer apps, and let Walgreens photo services go well beyond the store, embedding a presence in a multitude of apps and handsets they wouldn’t have addressed without a productized API. Walgreens has turned their developer ecosystem into channel partners and now offers them much more than just photo printing services.In this model, the API product is offered for free, as there is an obvious value proposition to all three parties—API publisher, developer, and user. (Learn more about how Walgreens uses Apigee.) 2. Consider brand awareness and promotionYour application is lost in a sea of hundreds of other similar apps in an app store. What now? One way of driving awareness is to extend your branch reach/footprint via an API, then reward users or developers for sign-ups and usage, in order to proliferate the application to new surface areas, experiences, and form factors. Streaming services, for example, generally have an incentive to make their streaming players easy to integrate across a wide variety of devices, form factors, and digital experiences. This can in turn create an incentive among device-makers and app-makers to integrate the service, creating a potentially exponential increase in the value proposition for the end consumer and the developers integrating the streaming player API. And when this variety of viewing options for the user meets quality content from the service, the result can be a self-reinforcing cycle of more subscribers and increased reach across more consumer touchpoints. Developers, device-makers, and the service publishing the API create ways to make money, and end users get a steadily-improving and flexible service.Similarly, Brazilian retailer Magalu (formerly Magazine Luiza) leveraged APIs to achieve, as CTO Andre Fatala put it in a 2019 blog post, a “newfound ease and speed of spinning up new services and customer experiences and adjusting existing ones,” which let “everyone … work in small teams of five or six people that take care of segments of an application, whether it’s online checkout, physical store checkout, or order management.” The approach means Magalu “work[s] much more like a software company than a retail company now,” he said.With these new agility, the company has expanded its e-commerce strategy to third-party sellers and created a digital marketplace that lets merchants easily join the ecosystem via Magalu’s API platform. Whereas the company’s old legacy sales and distribution systems only supported 50,000 SKUs, the marketplace supports thousands of sellers and millions of SKUs, significantly expanding the brand’s reach.3. Enable customization to create new value propositionsIn a bid to create an ecosystem around its banking products, ABN Amro partnered with telecommunications company KPN, smart homes expert 50five, and Energizer—and begun leveraging its first-party payments app Tikkie, the Olisto IoT device triggering platform, and the Google Nest API—to create an entirely new value proposition around smart home solutions. Thanks to this collaboration, when the Nest Protect smart smoke alarm runs low on batteries, it can order replacements automatically, performing the payment through Tikkie and triggering the batteries to be delivered directly to the owner’s home. This capability significantly reduces risk of a smoke alarm not working due to battery failure—and with Google currently rolling out new Nest initiatives to replace the program under which ABN Amro’s solution was created, we’re excited to see what novel and convenient user value propositions our APIs enable in the future. These API partnerships let ABN Amro position their offering as a flexible platform, able to generate network effects to aggregate demand. As new value propositions are created in these many ecosystems, ABN Amro will already be integrated and available to meet the needs of the ecosystem. The company’s flexible, customizable platform will offer the path of least resistance for future similar API partnerships.In this model, the API product is offered for free, as there is an obvious value proposition to all three parties—the API publisher, the bank, is a more desirable destination to keep money (and do business with) because of its flexibility; the developer drives value and differentiation to their product by alleviating a significant consumer pain point; and the end user benefits from having a functioning smoke detector.4. Enable access to rare and valuable competenciesThere are situations in which the best way to generate value from an API is to charge for it. If the API product substitution risk is low—if your value proposition is rare, valuable, and is not being competed against by indirect competitors—there is an opportunity to generate direct value from the API by charging for access. A great example of this is telecommunications infrastructure APIs, such as telematics APIs for in-vehicle connectivity. Though there are other telecommunications providers likely competing, the threat of other non-telecom providers offering in-vehicle applications and connectivity—i.e., the product substitution risk—is very low. As a result, telecoms can charge for those API products, as they are rare and valuable. Reducing the importance of API value generation to simple revenue generation or cost savings frequently misses the key sources of untapped value available when targeting developers with an API program. This ability to inspire developers—not unlike Gooding’s Rod Tidwell character rediscovering the drive that inspires people to watch football—is the bedrock of the internet economy, the “demand aggregation” model that enables ecosystem effects and significant value generation. When considering an API productization approach, make sure to have all of these in mind as you map your path to success. To learn more, check out our ebook on API productization.Related ArticleGoogle named a leader in the 2020 Gartner Magic Quadrant for Full Life Cycle API ManagementFor the fifth year in a row, Google Cloud (Apigee) has been named a leader in Gartner’s Full Life Cycle API Management Magic Quadrant.Read Article
Quelle: Google Cloud Platform