Wegen politischer Meinungsmache und gezielter Desinformation haben Twitter und Facebook Tausende Nutzerkonten gesperrt sowie Inhalte aus ihren sozialen Netzen entfernt. Für die falschen Facebook-Konten wurden Profilbilder mit KI erzeugt. (Fake-News, Spam)
Quelle: Golem
Noch eine Akquisition: Der schwedische Publisher Embracer – bis vor kurzem THQ Nordic – kauft das Entwicklerstudio Tarsier, das vor allem für Little Nightmares bekannt ist. Erst vor wenigen Monaten übernahm Embracer bereits Piranha Bytes und Warhorse Studios. (Koch Media, THQ Nordic)
Quelle: Golem
Alle drücken aufs Strompedal: Brandenburg verkauft ein 300 Hektar großes Grundstück bei Berlin, auf dem Tesla seine nächste Gigafactory bauen will. Der Vertrag ist fertig, der Tesla-Vorstand muss ihn noch billigen. (Tesla, Elektroauto)
Quelle: Golem
There was amazing attendance at Containers Today in Stockholm a couple of weeks ago. For those who were unable to make it, here is a quick overview of what I talked about at the event in my session around the future of the developer journey.
Before we talk about what we think will change the journey, we need to think about why it changes. The fundamental goal of any change to the way of working for developers should be to reduce the number of boring, mundane and repetitive tasks that developers have to do or to allow them to reach new customers/solve new problems. Developers create amazing value for companies and provide solutions to customers’ real world problems. But if they are having to spend half of their time working out how to get things into the hands of their customers, then you are getting half the value.
Developer Evolution
The role of developers has changed a lot over the last ~40 years. Developers no longer deploy to mainframes or in house hardware, they don’t do waterfall deployments and not many of them write in machine code. Developers have to now think about web languages and ML, work in Extreme Agile DevOps teams (ok I made that up a bit) and deploy to the Cloud or to Edge devices. This change keeps happening as the entire industry tries to find new ways for developers to deliver value, deliver that value faster and reduce the number of mundane tasks for developers.
Today the process for getting value to customers is often described as the ‘outer loop’ of development, while the creative process of development, i.e. creating new features, is described as the ‘inner loop.’
In an ideal world, that outer loop is automated and uses modern CI/CD technologies to create a cycle of feedback that allows developers to create new features and fix bugs ever faster. This looks something like:
Though this is an ideal world, this is not the case for a lot of developers. In the “The State of Developer Ecosystem 2019” report, only 45% of developers said that CI/CD was part of their regular tool set. This also means 55% of developers have yet to adopt it. This is one of the changes we think will start to accelerate in the near future. As CI/CD is democratized with new tools like Github Actions, we will see even small teams starting to adopt CI/CD over manual deployments.
Another big change in the outer loop is how people look at what they are passing through this outer loop. Developers are trying to get value out to customers but the concept of value is changing. As we moved away from monoliths, we have started to create individual services that are easier to work with and deploy. The idea of bundling these services with systems like Helm or CNAB tools is becoming more prominent as businesses consider that in isolation, a single container does not provide value to a customer. But a collection of these services together is the minimum set to deliver customer value.
These may each be a separate microservice, but just a notifications service or a payment service won’t drive business value in isolation.
For the outer loop, some of the big changes we see are changes to how things are deployed. 57% of developers are still not using orchestration (Slashdata Developer Report 16th Edition). The growth in orchestration and in particular K8s is going to change how we think about the hand off between developers and operations as we move towards more microservices in production than ever before. The complexity of this change will be compounded as production is likely to be on multiple clouds or on premises, and as over 50% of companies have a hybrid strategy and a multi cloud strategy.
For developers, all of these things are going to be impactful at a significant scale as we aim to develop the next 500 million apps by 2023 (IDC Analyse the Future). With Edge/IoT growing 10X between 2017-2025 (Allied Market Research), we are also going to need to think of new ways for developers to work with these technologies and extend their inner loop outside of their immediate machine.
So in summary, we are going to see more bundled apps being deployed via CI/CD to orchestrators in the cloud and on prem, and movement between them. We will be building more of these apps than ever and they have to run anywhere, considering how they interface with the Edge and work as part of our inner loop for this on the Cloud. And finally, we strongly believe that the use of containers is going to be a driving factor and the underlying technology to enable this.
What’s Next for Developers
At Docker, we have started to look ahead at how we can build technology to help developers adopt some of these tools.
For local developers, we have looked at how to accelerate people creating the next 500 million new applications with Application templates, enabling developers to create new containerized applications in seconds from existing examples. We have been working out how we can improve our IDE integration to make developers lives better where they work today. We have added a layer of GUI abstraction into Docker Desktop to make it simpler to understand all of these components.
We are also thinking about how we can extend the local development environment and the inner loop for new objects. We have Docker Context to allow developers to work on a remote instance within their inner loop and ARM builds in Docker desktop for Working with the Edge.
And to deploy value in the future, we have Docker App for bundling the value of more than one container service to get it running in production.
We are also thinking about things like CI, moving between platforms and generally how to make it easier for the next 10 million developers to get started with Docker. We know that a lot of these technologies have been embraced by early adopters. But as all of these new technologies and changes start to reach the early majority, we need to think about how we are going to scale all of said technologies and keep mundane tasks away from developers!
Containers Today was a fantastic event with great turnout. Hopefully this post gives some insight into my talk at the event and the trends we see. If you have other thoughts on what the future of the developer journey holds, please reach out to us!
The post Containers Today Recap: The Future of the Developer Journey appeared first on Docker Blog.
Quelle: https://blog.docker.com/feed/
Jetzt können Sie Amazon CloudWatch Contributor Insights für Amazon DynamoDB (Vorschau) in 15 weiteren AWS-Regionen rund um die Welt nutzen.
Quelle: aws.amazon.com
Amazon MQ unterstützt durchsatzoptimierte Message Broker, die von Amazon Elastic Block Store gesichert werden. Durchsatzoptimierte Broker reduzieren die Anzahl der benötigten Broker und die Kosten für den Betrieb von datenintensiven Anwendungen.
Quelle: aws.amazon.com
Ab heute können Over The Air (OTA)-Updates für IoT-Geräte, auf denen Amazon FreeRTOS ausgeführt wird, über HTTPs durchgeführt werden. Die OTA-Konsole wurde aktualisiert, um Benutzern die Wahl zwischen MQTT und HTTP für die Bereitstellung von SW-Updates zu ermöglichen. Dabei wurde die HTTPS-Client-Funktion genutzt, die Anfang dieses Jahres in Amazon FreeRTOS bereitgestellt wurde. Weitere Änderungen in unserem Release 201912.00 können in unserem Änderungsprotokoll nachgelesen werden.
Quelle: aws.amazon.com
Heute hat AWS Service Catalog die Unterstützung der Deprekation von Produktversionen bekanntgegeben. Mit der Veröffentlichung der Produktversionsanleitung können Administratoren neue Starts einer Produktversion verhindern und gleichzeitig deren Verwendung und Aktualisierung in vorhandenen Stacks zulassen.
Quelle: aws.amazon.com
Moving from a traditional on-prem data warehouse platform to a cloud data warehouse, such as Google Cloud’s BigQuery, is about more than just adopting new technology. It also provides an opportunity to revisit existing practices and adopt new ways of working. We’ve noted some typical changes that teams undergo to support data warehouse migration to the cloud. To get a framework for change management and best practices for moving to the cloud, you can find more details in the Managing Change in the Cloud whitepaper.People form the core of any change management initiative. For a data warehouse migration initiative, we’ll focus on three key stakeholders who are involved in day-to-day usage and management (though there may be other ancillary roles involved): Data consumer—typically a data analyst, data scientist, or business user Data enabler—typically a data engineer or ETL developer Data administrator—typically a database/data warehouse administratorClick to enlargeLet’s take a look at each stakeholder and see how their responsibilities change as their organization transitions from on-prem to cloud. Data consumer Data analysts and data scientists have a lot to gain from migrating to a cloud data warehouse— easier availability of new datasets, new algorithms to play with, and lower-latency access options in the cloud. Most often, during the migration, existing reporting applications and BI tools are initially kept as is to ensure minimal business disruption—making it relatively easy for data consumers to adopt the changes. Data consumers, however, will likely want to ensure that their existing reports and use cases are tested on the new platform. It is, therefore, advisable to require their participation in any data validation efforts. You might create a data validation team, for example. Post-migration, data consumers can find new ways of working once they have access to new datasets, like converting batch reporting into real-time dashboards, and finding ways to make machine learning a reality for the organization. New platform capabilities end up becoming the most important catalyst for change in this role. The more ambitious the data consumers are, the greater the change will be for other roles in the organization. Data enablerThe technical abilities of the data enabler are vital to how successfully cloud is adopted into the organization. These individuals own the data pipelines and are deeply involved in any reengineering efforts needed to migrate workloads to the cloud. The learning curve can be steep depending on the technology stack that’s adopted; proper resource planning will be crucial for these data enablers. Migration to the cloud in and of itself could be a long-term undertaking, so it’s worth considering taking the time to plan, re-tool and automate the migration. As data enablers are refactoring and redesigning data pipelines and working together with data consumers, they have plenty of opportunities to rethink how business processes should change to take advantage of real-time data ingestion, new data modeling techniques, or new persistent stores that cloud technologies offer. Data enablers might also revisit old asks that were not possible to deliver due to scale, data format complexity, or ETL complexity. Cloud technologies can be better suited to overcoming such challenges through capabilities such as storage and compute resource elasticity, support for numerous data format and storage options, as well as a wide variety of tools and libraries to process data. Beyond that, adopting a DevOps model, application containerization, or a serverless compute model are avenues that data enablers (along with data administrators) can explore to improve the speed with which changes are applied and new insights are delivered to users.Data administrator Database administrators continue to play a vital role even if the enterprise data warehouse is hosted in the cloud. As owners of the platform, administrators must get acquainted with cloud technology capabilities at the earliest and drive the enterprise transformation with key stakeholders. As database administrators move data workloads into the cloud, there continue to be important focus areas: governance overview during and post migration, data integrity, and SLAs such as RPOs and RTOs. If the organization adopts a vendor-managed cloud data warehouse, database administrators will have fewer platform procurement and database-tuning tasks. But cost vs. performance optimization is still a critical area for administrators to be fully involved in. (Check out ESG’s report on how migrating to BigQuery can lower your three-year TCO up to 52%.) Database administrators are also freed up to gain a deeper understanding of the storage, network, and compute options that cloud offers and look for ways to optimize enterprise workloads in the cloud. Administrators can adopt new ways of working with machine learning notebook environments, new query tools, containerization, hybrid cloud, and more—there’s plenty to learn and optimize for! Organizations that adopt these new skills and processes have a greater chance of success in delivering business results in the cloud. For more information on how to streamline your enterprise migration path, check out our data warehouse migration guide and framework. You can also apply for our data warehouse migration offer for help with the full migration process.
Quelle: Google Cloud Platform
The California Consumer Privacy Act (CCPA) is a data privacy law that imposes new requirements on businesses and gives consumers in California the right to access, delete, and opt-out of the “sale” of their personal information. Businesses that collect California residents’ personal information and meet certain thresholds (for example, revenue) will need to comply with these obligations. You can count on the fact that Google Cloud is committed to supporting CCPA compliance across G Suite and Google Cloud products when it takes effect on January 1, 2020. Google Cloud will support you in meeting your CCPA obligations by offering convenient tools alongside the robust data privacy and security protections in our services and contracts. How does Google Cloud support CCPA compliance?The security and privacy of customer data is our highest priority, and we’re committed to supporting your efforts to comply with the CCPA by: Providing tools and support to enable you to comply with CCPA requirements around your consumers’ rights. You can use G Suite and Google Cloud’s administrative consoles and services to help access, export, or delete data that you and your users put into our systems. This functionality will help you fulfill your obligations to respond to requests from consumers who exercise their rights under CCPA.Offering security products and features that will help you to protect personal data. Google operates global infrastructure engineered for security from the start. You can rest assured knowing that we have designed for the secure deployment of services and data storage. We’ve implemented end-user privacy safeguards, secure communications between services, secure and private communication with customers over the Internet, and granular operational controls by administrators. Google Cloud runs on this infrastructure, and our products and features provide capabilities for data governance, access control, export, encryption, and security management that can help organizations with their CCPA readiness.Providing documentation and resources to assist you in your privacy assessment of our services. We want to ensure that Google Cloud customers can confidently use our services in light of the CCPA. When you use Google Cloud, we support your efforts by providing detailed documentation and resources, such as our new Google Cloud and the CCPA whitepaper. Continuing to monitor the regulatory landscape, and evolving as needed. Our cross-functional teams of privacy advocates, user experience researchers, public policy, and privacy legal experts regularly engage with customers, industry stakeholders, and supervisory authorities to shape our Google Cloud services in order to help customers meet their compliance needs. As the regulatory landscape shifts, we evolve to support our customers’ changing compliance needs. Offering a team dedicated to addressing Google Cloud customers’ data protection-related inquiries. For more information, refer to Google’s Businesses and Data website or visit our support pages for Google Cloud and G Suite. Where do you stand?As a current or future customer of Google Cloud, there are many ways to begin preparing for the CCPA. Consider these tips:Familiarize yourself with the text of the CCPAand its regulations. Create a data inventory that describes how your business collects, uses, and shares personal information. We have tools such as Cloud Data Loss Prevention and Data Catalog that can help identify and classify data.Review the current controls, policies, and processes that govern your use of personal information to assess whether they meet CCPA requirements, and build a plan to address any gaps.Consider the best process for your business to accept and verify a California consumer request.Review our Google Cloud third-party audit and certification materials, as well as our guidance documents and mappings, to see how they may help with this exercise. Consider how you can leverage existing data protection features on Google Cloud to support your CCPA compliance.Monitor the latest regulatory guidance as it becomes available, and consult a lawyer to obtain legal advice tailored to your business’s circumstances. What’s next?We’re carefully monitoring developments around this new legislation, and constructively engaging with our customers and partners throughout this process. We’ve also created this CCPA Compliance pageon our Compliance resource center to assist with your efforts as you prepare for CCPA.For information on Google Cloud privacy practices, please visit our Google Cloud Trust Principles. This blog post is intended to be for informational purposes only. You should seek independent legal advice relating to your status and obligations under the CCPA, as only a lawyer can provide you with tailored legal advice for your situation. Nothing in this blog post is intended to provide you with or should be used as a substitute for legal advice.
Quelle: Google Cloud Platform
