Open Source Java Cloud Services Software

microG GmsCore is a FLOSS (Free/Libre Open Source Software) framework to allow applications designed for Google Play Services to run on systems, where Play Services is not available. The linux-based open-source mobile operating system Android is not only the most popular mobile operating system in the world, it’s also on the way to becoming a proprietary operating system. How is that? While the core operating system is still released as part of the Android Open Source Project, the majority of core apps are not. It gets worse: More and more libraries and APIs are only available on phones that run various Google apps pre-installed, effectively locking third-party apps to the Google ecosystem. For these reasons Android is described as being a “look but don’t touch” kind of open. At this point, several popular open-source applications already require some of Google’s proprietary libraries to be installed.

This repository is for the active development of the Azure SDK for Java. For consumers of the SDK we recommend visiting our public developer docs or our versioned developer docs. To get started with a specific service library, see the README.md file located in the library's project folder. You can find service libraries in the /SDK directory. For a list of all the services, we support to access to our list of all existing libraries. New wave of packages that follow the Azure SDK Design Guidelines for Java and share a number of core features such as HTTP retries, logging, transport protocols, authentication protocols, etc., so that once you learn how to use these features in one client library, you will know how to use them in other client libraries. These libraries can be easily identified by folder, package, and namespaces names starting with azure-, e.g. azure-key vault.

Eclipse Che is a Kubernetes-native IDE that makes Kubernetes development accessible for development teams. It places everything a developer could need into containers in Kube pods including dependencies, embedded containerized runtimes, a web IDE, and project code. With the Kubernetes application in your development environment and an in-browser IDE, you can code, build, test and run applications exactly as they run on production from any machine.

Spring Cloud Config provides server-side and client-side support for externalized configuration in a distributed system. With the Config Server, you have a central place to manage external properties for applications across all environments. The concepts on both client and server map identically to the Spring Environment and PropertySource abstractions, so they fit very well with Spring applications but can be used with any application running in any language. As an application moves through the deployment pipeline from dev to test and into production, you can manage the configuration between those environments and be certain that applications have everything they need to run when they migrate. The default implementation of the server storage backend uses git, so it easily supports labelled versions of configuration environments as well as being accessible to a wide range of tooling for managing the content. It is easy to add alternative implementations.

The AWS CloudTrail Processing Library is a Java client library that makes it easy to build an application that reads and processes CloudTrail log files in a fault-tolerant and highly scalable manner. The AWS CloudTrail Processing Library helps Java developers to easily consume and process log files from AWS CloudTrail. Provides functionality to continuously download CloudTrail log files in a fault-tolerant and scalable manner. Serializes the events in JSON format to Plain Old Java Objects (POJO). Provides interfaces to implement your own business logic for selecting which events to process, processing events, handling errors, and handling log processing status updates. Monitor, store, and validate activity events for authenticity. Easily generate audit reports required by internal policies and external regulations.

Seata, or Simple Extensible Autonomous Transaction Architecture is an open source distributed transaction solution that brings high performance and easy-to-use distributed transaction services under a microservices architecture. It has 3 basic components: a Transaction Coordinator for maintaining the status of global and branch transactions; a Transaction Manager that defines the scope of global transaction; and a Resource Manager that manages resources being worked on by branch transactions, and drives branch transaction commit or rollback. Seata has played a pivotal role of distributed consistency Middleware in Ali economy, and has provided strong support for businesses of all departments. It continues to be used and trusted by dozens of other companies.

Speed up development and migration, reuse our templates to create complex environments for common use cases with ease. Rely on high-quality infrastructure templates: peer-reviewed by an expert (certified AWS solutions architect Professional) and verified with automated tests. You can apply updates to an existing stack with an updated template. CloudFormation will figure out what needs to be changed. Never make manual changes to infrastructure managed by CloudFormation! The bastion host has a optional dependency on the alert stack. So if you want to receive alerts if your bastion hosts is in trouble, supply an alert stack. Do you want to accelerate your start with AWS CloudFormation and our templates? We do offer remote and on-site training for you and your team. All templates are published under Apache License Version 2.0. Besides our open-source projects, we also offer commercial products on the AWS Marketplace.

Google Santa Tracker app for Android is an educational and entertaining tradition that brings joy to millions of children (and children at heart) across the world over the December holiday period. The app is a companion to the Google Santa Tracker website (repository here), showcasing unique platform capabilities like Android Wear watchfaces, device notifications and more. First up, Santa Tracker is powered by Firebase, so you'll need to enable it on your Google account over at the Firebase console. A beautiful designed village. Exciting games like Penguin Swim and Rocket Sleigh. Use of Dynamic Feature Modules (each game is a separate module, fetched dynamically on first run). Interactive Android Wear watchfaces (with sound!). Videos, animations and more.

React native module for firebase cloud messaging and local notification. react-native-firebase now can do what react-native-fcm can so it is a waste of effort to build the same thing in parallel. To allow android to respond to click_action, you need to define Activities and filter on specific intent. Since all javascript is running in MainActivity, you can have MainActivity to handle actions. If you are using RN < 0.30.0 and react-native-fcm < 1.0.16, pass intent into package, edit MainActivity.java. Import libraries, add Capabilities (background running and push notification), upload APNS and etc. Put frameworks under ios/Frameworks folder, and drag those files into your xcode solution. Make sure the file is not just moved into the folder. You need to Right Click the project folder in XCode and Add File to <Project Name>. Select Copy if needed in the Options page while selecting the file.