In the competitive market of collaboration tools, Google is investing in Chat to challenge the likes of Microsoft Teams and Slack. If you are unfamiliar with the applications listed above don't feel left out. All three applications focus on consolidating the bombardment of communication tools that employees interact with on a daily basis. Chat and its competitors provide a single place for messaging, document editing, and files sharing allowing your users to effortlessly collaborate in realtime. Chat's most recent updates allow External Users into a Chat room and a new Chat app that allows users to collaborate without an internet browser! No matter what G Suite license you use, Chats is included at no extra cost.
With more public and private clouds popping up, it can be difficult for enterprises of any size to determine which cloud is best for them. As the technology develops, each cloud provider boasts improved functionality and new integrations to make management and monitoring easier and provide users more flexibility in network and infrastructure configurations. While AWS was the first cloud environment launched and Azure has the backing of industry powerhouse Microsoft, Google is finding its niche.
I took (and failed) the GCP Professional Collaboration Engineer certification earlier this week. I want to share my experience so that others can avoid the same mistakes. I have been administering over G Suite domains for two years and have obtained several Google certifications, most recently the GCP Professional Cloud Architect. I am sharing my past experiences to give context to the mistakes when preparing for the exam.
This is what the .NET community needed to fully embrace GCP
Yesterday at Google Next, they announced something I've been wanting for a long time. As a google partner, sometimes I get to hear about things when they're in alpha and this was one of them. Serverless containers is the ultimate awesome in my mind, especially for webapps and APIs, because everyone knows the biggest headache for containers is orchestration. Well this announcement kinda abrogates the need for orchestration at all. If these things auto-scale then I don't have to manage a K8s cluster at all. I mean, yeah for internal services there is some significant networking work to do, but DUDE. Auto-scaling CONTAINERS that are SERVERLESS. Can life better? I submit that it CANNOT!