Cloud Computing Köln - Seite 2213 von 7044 - Neues zu Cloud Computing, Internet of Things und Technologien

Pub/Sub stores messages reliably at any scale. Publish a log entry or an event and you don’t have to worry about when it is processed. If your subscribers, event handlers, or consumers are not keeping up, we’ll hold the messages till they are ready. Bugs made it past your integration test? Not to worry: just seek back and replay. But, you had to worry a little: until today, you had up to a week to fix the code and process everything. And if you wanted to use historical data to compute some aggregate state, such as a search index, you had to use a separate storage system. In fact, we noticed that many of our users stored raw copies of all messages in GCS or BigQuery, just in case. This is reliable and inexpensive, but requires a separate reprocessing setup in case you actually need to look at older data. Starting today, Pub/Sub can store your messages in a topic for up to 31 days. This gives you more time to debug subscribers. This also gives you a longer time horizon of events to backtest streaming applications or initialize state in applications that compute state from an event log. Using the feature is simple. The interfaces and pricing are unchanged. You can just set a larger value for a topic’s message retention duration. For example, you can configure extended retention of an existing topic using the gCloud CLI: gcloud pubsub topics update myTopic –message-retention-duration 31dOr use the settings in the Topic Details page in Cloud Console:One limitation of this feature is that you cannot extend storage retention for an individual subscription beyond 7 days. This limits the control individual subscription owners have over storage. The limit comes with benefits: controlling storage costs is simpler and so is limiting access to older data across multiple applications.We’d love to hear how you’ve used this feature or how it came short of your needs. Let us know by posting a message to the pubsub-discuss mailing list or creating a bug.
Quelle: Google Cloud Platform

10. Dezember 2021

da Agency

Software-Defined community cloud – a new way to “Government Cloud”

Google has a long history anddeep commitment to innovation in the public sector and regulated markets including healthcare, financial services, and telecommunications, to name a few. Recently, we’ve made significant advances in our security and compliance offerings and capabilities in order to better enable government and government supply chain customers to adopt Google Cloud. Specifically, our Assured Workloads product implements a novel approach to help customers meet compliance and sovereignty requirements: a software-defined community cloud. What is a community cloud? A community cloud is defined by NIST SP 800-145 as:Cloud infrastructure [that] is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises.The approach has been used for decades and offers potential benefits such as:Members of the community operate under the same set of security controlsThe ability to support attributes like citizenship and authorization controls while maintaining limited physical and/or logical access to resources.The ability to support data localization and some data sovereignty requirements based on the location of the community cloud’s data centersA clearly-defined perimeter security model encompassing the community cloudChallenges with legacy community cloud implementationsThe definition and objectives of community clouds are well-intentioned, but often the implementation of community clouds have failed to meet specific objectives or required significant tradeoffs for adopters.Most community clouds to-date have relied on physical separation as the primary means of establishing a security perimeter. While this approach offers benefits in simplicity and segregation, there are downsides. A perimeter security model, also referred to as a “castle wall model” often doesn’t yield significant advances in security, manageability, or compliance. The shortcomings of a perimeter model as the primary mode of protection is acknowledged across the industry and has accelerated adoption of alternative approaches such as Zero Trust architectures. This is the case for compliance as well – in models that are tied to physical perimeters (e.g., legacy “Gov Clouds”) control assumptions at the perimeter can lead to control failures on the interior that lead to potentially serious security problems. Having created a physical community cloud in the past, Google sought a new way to provide the benefits above along with scalable and lasting compliance implementations. Software-defined community cloudLike virtualization for servers or software-defined networking for switching and routing hardware, a software-defined community cloud is designed to deliver the benefits of a community cloud in a more modern architecture. Google Cloud’s approach provides security and compliance assurances without the strict physical infrastructure constraints of legacy approaches. Google Cloud’s approach for offering software-defined community clouds is implemented using a combination of technologies referred to in aggregate as “Assured Workloads.” With Assured Workloads, Google Cloud can:Define communities around shared mission, security and compliance requirements, and policy.Separate those community projects from other projects.Add or remove capabilities from a community’s boundary with policy-controlled and audited configuration changes.This software-defined approach yields several potential benefits to customers. But first, let’s consider community cloud characteristics mapped to traditional and software-defined implementations:Software defined community cloud as a new type of “Government Cloud”In Google Cloud Platform (GCP), a project is an isolated, logical grouping of “infrastructure primitives.” In this context, an infrastructure primitive is any atomic unit of capacity in GCP – a virtual machine (VM), a persistent disk (PD), a storage bucket, etc. Projects are “global resources” that can be assigned infrastructure primitives from any region or zone.Every project is, by default, isolated from other customers’ projects. Low-level resources like hypervisors, blocks in our distributed blockstore that underlies Google Cloud Storage (GCS), and other components are isolated with resource abstractions that enforce the isolation both logically and cryptographically. A Private Cloud deployment model is described in NIST SP 800-145 as:Cloud infrastructure [that] is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises.When a project is created within GCP, the infrastructure primitives that are assigned to that project are scoped to only that project. This scoping of infrastructure primitives effectively creates an “enclave” per Project.When overlaid with Assured Workloads constraints for data residency, support personnel attributes, and security controls common to that community, these per-project private cloud enclaves become software-defined community clouds.Benefits of a software-defined community cloudThe approach Google Cloud has taken brings multiple benefits in addition to meeting security and compliance requirements. New hardware, new services, and improvements to existing services can be made available faster than in traditional community clouds. The process by which new cloud technology can be onboarded and made available is also faster. Overall efficiency is improved in this model due to the scale of infrastructure available to the community; this can translate to improved availability and performance. Security enhancements can be scaled and implemented more quickly. Moving forwardAt Google Cloud, we continue to advance the capabilities that enable our customers to create and operate within software-defined community clouds. Learn more about the capabilities currently delivered through Assured Workloads here.Related ArticleGoogle Cloud achieves new public sector authorizations: Google Workspace earns FedRAMP High, key Google Cloud Platform services receive DoD IL4Governments across the globe want to make life easier for their citizens—they want to enable businesses to thrive, increase public safety…Read Article
Quelle: Google Cloud Platform

10. Dezember 2021

da Agency

commercetools powers modern, scalable digital commerce solutions with MongoDB Atlas on Google Cloud

Powering modern retail operations is no easy task – consumer and business preferences shift constantly, disruptions abound, and demand can significantly fluctuate daily or even hourly. But within this environment, there are almost limitless opportunities for retailers that have an agile IT environment that can efficiently and proactively meet changing consumer demands.At commercetools, we pride ourselves on giving businesses what they need to succeed in the digital era. As a cloud-native company, we constantly look toward the future, innovating on our platform and working to better serve our customers. To accomplish our goals and remain as agile and accessible as possible, we base our platform on microservices.For years we have taken advantage of being fully cloud native as a means to optimize our microservices infrastructure and take an API-first approach to management. Given constant innovations in cloud computing, we also look for the latest and greatest tools to further enhance the services we offer our customers.One area that has become particularly important in recent years is the ability to efficiently auto-scale and manage resources. That means being able to get even more performance out of our platform, which is why we chose to work with Google Cloud and MongoDB.Building on years of successGoogle Cloud has long been our trusted cloud services provider, and we’ve used MongoDB since 2014. We saw opportunities to extend these relationships and the technologies used to improve everyday operations across our business. This in part included implementing MongoDB Atlas to optimize database scalability and efficiency.A big advantage of running MongoDB Atlas on Google Cloud is the integration between the database and Google Cloud services including Google Kubernetes Engine (GKE), BigQuery, and the Cloud AI Platform. Since these solutions work so well together, the commercetools team is confident that performance will be exceptional regardless of the tasks we need to run.Given retail-specific factors such as seasonality and constantly shifting consumer preferences, we need to provide retailers with the confidence that our platform runs properly at all times. The combination of Google Cloud solutions and MongoDB Atlas as a fully managed database enables us to achieve our goals and deliver outstanding services to our customers.When it comes to scale, we have certain customers that process tens of thousands of transactions per minute. We need to make sure all of those orders execute flawlessly, with all accompanying data captured and managed. Accomplishing this requires that every step is fully integrated into the right area of our technology stack—something that Google Cloud and MongoDB make a lot easier.MongoDB’s application data platform also provides a whole suite of useful tools including MongoDB Charts, backups, and enhanced security capabilities. All are key to our success and important to our customers. In MongoDB, we can also scale horizontally or vertically, handle spikes through auto-scaling, and never worry about data security or retention. Without MongoDB Atlas on Google Cloud, this wouldn’t be possible.Because of this, we can quickly and reliably roll out new features, sites, touch points, and channels in step with our customers’ demands. The agility supported by Google Cloud and MongoDB Atlas allows commercetools to stand out from our competitors.Equally important to our success is the level of automation we build into our environment thanks to Google Cloud, MongoDB Atlas, and our own engineers. We’ve been able to take a more modern approach to performance testing, with everything monitored and fixed in real-time. For retailers, this is vital because many often wait until huge events like Black Friday, when it’s too late to test the power and reliability of an environment.Automating cluster management, deployments, and testing is essential for us to scale with our customers when they need us. With the automation offered in Google Cloud and MongoDB Atlas, we are always prepared for anything our customers need.All of this adds up to an unmatched ability to provide customers with roughly 300 APIs that they and our partners can mix and match to achieve the standout commerce experience they envision for their customers. This is what separates commercetools from our competitors. We are not just a one-size-fits-all tech stack. Instead, we give retailers the options to build their own solutions that map to their exact needs—and the opportunities their customers present.Addressing challenges across industriesWhile we are certainly rooted in retail, the need for digital transformation is evident in every industry, and our platform is flexible enough to adapt to many needs.For example, companies with smaller IT departments can work with our partners to accelerate the roll-out of new digital services and enhanced customer experiences. Our partners can project manage as needed and use our APIs to tailor the solution to each company’s unique needs. At the same time, companies with larger IT operations can have their own teams use our APIs to more quickly achieve their own goals.The success of our approach to build and manage commerce platforms was underscored during the COVID-19 pandemic, when so many businesses scrambled to strengthen digital footprint amid lockdowns and immense economic shifts.Let’s say a company wanted to build an additional channel to enable curbside pickup. With a monolithic system, an IT team might have worked six months or more to get that service up and running. For many companies, this would have been untenable given their resources and they would have lost market share.The beauty of commercetools is that we are flexible and accessible enough for any company, regardless of size or industry, to quickly deploy the services they need to keep pace with new market opportunities. It’s all thanks to our open architecture and cloud-native infrastructure, which Google Cloud and MongoDB are a big part of.Our success highlights the power of microservices supported by highly integrated solutions including GKE, BigQuery, and MongoDB Atlas. Through these partnerships, we can provide trials in which a customer can go to our website and explore everything we offer, spin up environments, deploy tools, and more.This is a huge differentiator for us. If we were locked down by our cloud infrastructure or database provider, we’d be unable to offer these types of readily accessible, high-performing self-service capabilities.We have accomplished a lot through our work with Google Cloud and MongoDB, and we are excited to continue transforming approaches to commerce in retail, healthcare, and many other industries in the future.
Quelle: Google Cloud Platform