Making Compose Easier to Use with Application Packages
Docker Compose is wildly popular with developers for describing an application. In fact, there are more than 300,000 Docker Compose files on GitHub. With a set of services described in a docker-compose.yml file, it’s easy to launch a complex multi-service application (or a simple, single-service app) on Docker by running a single command. This ease of use makes Docker Compose perfect for development teams striving for a quick way of getting started with projects.
Over time Compose has evolved, adding lots of features which help when deploying those same applications to production environments, for example specifying a number of replicas, memory resource constraints or a custom syslog server. But those attributes can become specific to your own environment. There are a number of different strategies for trying to address this situation, but the most common is relying on copy and paste. It’s fairly common to maintain multiple Compose files for the same application running in different environments for example. This leads to two problems:
- We share Docker images all the time, but don’t have a good way of sharing the multi-service applications that use them
- It’s hard to collaborate between developers and operators around a Compose file. This waters Continue reading
This money will fund what Neri called “intelligent edge” research and development around connectivity, security, edge computing, automation, machine learning, and artificial intelligence.
Deploying NB-IoT will require a software upgrade to the RAN and a few other network elements.