github.com/tickoalcantara12/micro/v3@v3.0.0-20221007104245-9d75b9bcbab9/docs/blog/_posts/2016-03-17-introduction.md

github.com/tickoalcantara12/micro/v3@v3.0.0-20221007104245-9d75b9bcbab9/docs/blog/_posts/2016-03-17-introduction.md (about)

1 ---
2 layout: post
3 title: Introducing Micro - a microservice ecosystem
4 date: 2016-03-17 09:00:00
5 ---
6 
7 Hello World!
8
9 Let's talk about the future of software development.
10
11 Change is afoot. We're moving more and more towards a world driven by technology at
12 the heart of every business. Maintaining a competitive edge in this day and age is
13 becoming difficult. Organisation's ability to execute can grind to a halt as they
14 try to scale with inefficient platforms, processes and structure. Decade old technology
15 companies have undergone these scaling pains and most have used the same methods
16 to overcome those challenges.
17
18 It's time to bring the competitive advantages of the most successful companies in the world to
19 everyone else. So with that, let's talk microservices, a way to create competitive edge.
20
21 ###### What are microservices?
22
23 Microservices is an software architecture pattern used to breakdown large monolithic applications
24 into smaller manageable independent services which communicate via language agnostic protocols and
25 each focus on doing one thing well.
26
27 Definition of microservices from industry experts.
28
29 > Loosely coupled service oriented architecture with a bounded context 
30 > Adrian Cockcroft
31
32 
33
34 > An approach to developing a single application as a suite of small services,
35 each running in its own process and communicating with lightweight mechanisms 
36 > Martin Fowler
37
38 The concept of microservices is not new, this is the reimagining of service orientied architecture
39 but with an approach more holistically aligned with unix processes and pipes.
40
41 The philosophy of Microservices architecture:
42
43 - The services are small - fine-grained as a singular business purpose similar to unix philosophy of "Do one thing and do it well"
44 - The organization culture should embrace automation of deployment and testing. This eases the burden on management and operations
45 - The culture and design principles should embrace failure and faults, similar to anti-fragile systems.
46
47 ###### Why microservices?
48
49 As organisations scale both technology and head count it becomes much more difficult to manage monolithic
50 code bases. We all became accustomed to the Twitter fail whale for a period of time as they attempted to
51 scale their user base and product feature set with a monolithic system. Microservices enabled Twitter to
52 decompose their application into smaller services that could be managed separately by many different teams.
53 Each team being responsible for a business function composed of many microservices which can be deployed
54 independently from other teams.
55
56 <div class="text-center">
57 <img src="{{ site.baseurl }}/blog/images/micro-service-architecture.png" style="width: 100%; height: auto;" />
58 </div>
59
60 We've seen through first hand experience that microservice systems enable faster development cycles,
61 improved productivity and superior scalable systems.
62
63 Let's talk about some of the benefits:
64
65 1. **Easier to scale development** - teams organise around different business requirements and manage their own services.
66
67 2. **Easier to understand** - microservices are much smaller, usually 1000 LOC or less.
68
69 3. **Easier to deploy new versions of services frequently** - services can be deployed, scaled and managed independently.
70
71 4. **Improved fault tolerance and isolation** - separation of concerns minimises the impact of issues in one service from another.
72
73 5. **Improved speed of execution** - teams deliver on business requirements faster by developing, deploying and managing microservices independently.
74
75 6. **Reusable services and rapid prototyping** - the unix philosophy ingrained in microservices allow you to reuse existing services and
76 build entirely new functionality on top much quicker.
77
78 ###### What is Micro?
79
80 Micro is a microservices ecosystem focused on providing products, services and solutions to enable
81 innovation in modern software driven enterprises. We plan to be the defacto resource for anything
82 microservices related and will look to enable companies to leverage this technology for their
83 own businesses. From early stage prototyping all the way through to large scale production
84 deployments.
85
86 We've seen a fundamental shift coming in the industry. Moore's law is in effect and we're gaining access
87 to more and more compute power everyday. Yet we're not able to fully realise this new capacity. Existing
88 tools and development practices do not scale in this new era. Developers are not being provided the tools
89 to move from monolithic code bases to more efficient design patterns. Most companies inevitably reach a
90 point of diminishing returns with monolithic designs and have to undergo massive R&D reengineering efforts.
91 Netfix, Twitter, Gilt and Hailo are all prime examples of this. All ended up building their own microservice
92 platforms.
93
94 Our vision is to provide the fundamental building blocks to make it easier for anyone to adopt microservices.
95
96 We're kicking all this off with an open source microservice toolkit, also called [Micro](https://github.com/tickoalcantara12/micro).
97 Expect a follow up blog post detailing the toolkit soon.
98
99 ###### What now?
100
101 When you hear the word microservices we want you to think, Micro - the microservices ecosystem. 
102
103 If you want to learn more about the services we offer or microservices, checkout the website [micro.mu](https://m3o.com) or
104 the github [repo](https://github.com/tickoalcantara12/micro).
105
106 Follow us on Twitter at [@MicroHQ](https://twitter.com/m3ocloud) or join the [Slack](https://slack.m3o.com)
107 community [here](http://slack.m3o.com).
108
109