Micro vs fabric8: What are the differences?

# Introduction
Micro and fabric8 are both popular platforms used in the field of microservices. While they share similarities, there are key differences that set them apart. Below are the top 6 differences between Micro and fabric8.

1. **Architecture**: Micro follows a more traditional microservices architecture, with its primary components being a service registry, API gateway, and messaging system. On the other hand, fabric8 is built on top of Kubernetes and focuses on providing a seamless experience for building, deploying, and managing microservices in a Kubernetes environment.

2. **Extensibility**: Micro provides a modular framework that allows users to easily extend its functionality through plugins. In contrast, fabric8 focuses on tight integration with Kubernetes and provides a rich set of tools and features that are tailored specifically for working within a Kubernetes cluster.

3. **Community Support**: Micro has a large and active community that contributes to its development and provides support to users. Fabric8, being an Eclipse Foundation project, benefits from the resources and support provided by the Eclipse community, which includes tools, plugins, and documentation specifically tailored for fabric8 users.

4. **Ease of Use**: Micro is known for its simplicity and ease of use, making it ideal for developers looking to quickly get started with building and deploying microservices. Fabric8, while more powerful and feature-rich, can be more complex to set up and configure due to its deep integration with Kubernetes.

5. **Monitoring and Logging**: Micro provides basic monitoring and logging capabilities out of the box, which can be extended with additional plugins. Fabric8, on the other hand, comes with built-in support for advanced monitoring, logging, and tracing tools, leveraging Kubernetes native capabilities for observability.

6. **Continuous Integration/Continuous Deployment (CI/CD)**: Micro focuses on providing a lightweight and flexible CI/CD pipeline that can be easily customized based on individual project requirements. Fabric8, built on top of Jenkins and Tekton, offers a more robust and scalable CI/CD solution that is tightly integrated with Kubernetes.

In Summary, Micro and fabric8 differ in their architecture, extensibility, community support, ease of use, monitoring/logging capabilities, and CI/CD features, catering to different needs and preferences in the world of microservices development.