github.com/tickoalcantara12/micro/v3@v3.0.0-20221007104245-9d75b9bcbab9/docs/blog/_posts/2020-01-30-micro-v2.md (about)

     1  ---
     2  layout:	post
     3  title:	Micro v2.0.0 release is out!
     4  date:	2020-01-30 09:00:00
     5  ---
     6  <br>
     7  We're happy to announce the release of Micro and Go Micro v2! This release is a major milestone for 
     8  us as we adopt gRPC and embedded NATS by default.
     9  
    10  See the releases here
    11  
    12  - [https://github.com/tickoalcantara12/micro/releases/tag/v2.0.0](https://github.com/tickoalcantara12/micro/releases/tag/v2.0.0)
    13  - [https://github.com/micro/go-micro/releases/tag/v2.0.0](https://github.com/micro/go-micro/releases/tag/v2.0.0)
    14  
    15  ## Evolution
    16  
    17  [**Micro**](https://m3o.com) is 5 years in the making now and through that time the tools in our industry have drastically changed. 
    18  We're moving towards cloud-native being the defacto standard for how we build software.
    19  
    20  Our vision from day 1 was always around [Microservices](https://m3o.com/blog/2016/03/17/introduction.html) and the 
    21  power of what it unlocks insides orgs that buy into this form of development. We also fundamentally believed 
    22  in [RPC](https://m3o.com/blog/2016/03/20/micro.html) and the direction of these patterns based on our 
    23  existing experiences at Google and Hailo.
    24  
    25  Since then though we've seen the emergence of gRPC, the dominance of kubernetes and many more systems including 
    26  the service mesh wave. Micro has stood through this test of time and actually thrived as it remained **developer 
    27  first focused**.
    28  
    29  To us all these tools are merely implementation details. What really matters is the abstractions and opinions 
    30  provided to the developer and this is why developers continue to adopt Micro in waves.
    31  
    32  We are never the early adopters of these new technologies but when a standard emerges we're fully onboard with 
    33  committing to a certain direction. In this case we've picked gRPC for synchronous communication and NATS for 
    34  async messaging.
    35  
    36  ## Road Ahead
    37  
    38  Micro started as a solo effort in 2015 as many of you have probably heard numerous times before but we're now slowly growing a 
    39  group of maintainers and a full time team to build out the next generation of tools and a platform to go beyond 
    40  open source.
    41  
    42  Micro wil be the defacto standard for microservices development in the Cloud and beyond as we look to build a serverless 
    43  platform so developers can focus on what really matters and stop thinking about the underlying infrastructure.
    44  
    45  Join our #platform channel on [Slack](https://m3o.com/community) to be the first to try it out.
    46  
    47  <center>...</center>
    48  <br>
    49  Micro is the simplest way to build microservices. If you're thinking about microservice development we want to help enable you on that journey. 
    50  To learn more check out the [website](https://m3o.com), follow us on [twitter](https://twitter.com/m3ocloud) or 
    51  join the [slack](https://slack.m3o.com) community.
    52  
    53  <h6><a href="https://github.com/tickoalcantara12/micro"><i class="fab fa-github fa-2x"></i> Micro</a></h6>