Datasets:
text stringlengths 0 1.82k |
|---|
• Introduction to Asim Aslam and his background |
• Overview of the Micro framework and its design decisions |
• Financial sustainability plan for the project and Asim's full-time work on it |
• Adoption and usage of Micro by companies (numbers and scale) |
• Philosophical discussion on the delineation point between a microservice and something larger |
• Designing and building microservices platforms |
• Microservices size and complexity: 1,000-2,000 lines of code |
• Measuring complexity based on mental model creation time |
• Comparing modular vs. monolithic architectures in microservices |
• Collaborative development of microservices in an open-source setting |
• Scaling and distributing microservices to achieve shared goals |
• Automation, self-healing, and fault-tolerance in distributed systems |
• Designing a framework for interacting with microservices through multiple interfaces (CLI, API, bot) |
• Micro is a toolkit for building managed microservices with Go |
• It uses the Go Micro library as its core, which provides fundamentals for communication, message passing, and request serving |
• The toolkit has an outer layer that includes a CLI, API, web UI, and sidecar for interacting with the HTTP interface |
• Asim Aslam built Micro to address the lack of tools for writing microservices in Go |
• Micro aims to simplify the process of building microservices by handling lower-level details |
• Go kit is another library for building distributed systems, which offers a standard library approach |
• The two libraries have different design goals and philosophies: Micro focuses on simplicity and ease of use, while Go kit provides more comprehensive abstractions |
• Micro's pluggable architecture allows users to easily swap out components such as messaging brokers or service discovery mechanisms |
• Importance of supporting different tools while maintaining a unified way of building software |
• Microservices architecture with interchangeable plugins for flexibility |
• Reusability of individual packages in unrelated projects |
• Getting started with Go Micro, including resources and tutorials |
• Serverless computing concept and its benefits |
• Challenges and limitations of serverless approach at scale |
• Event-driven programming and serverless architecture |
• Shift in thinking for building systems from traditional synchronous models |
• Serverless frameworks such as AWS Lambda, Google Functions, IBM OpenWhisk, and serverless.com |
• Use cases for serverless applications: rapid prototyping, frontend and API development, data analytics |
• Available products for driving serverless application development: serverless.com, Apex, OpenWhisk |
• Go 1.7 Beta release features, including SSA compiler, subtests, and performance improvements |
• CoreOS and Torus |
• Distributed storage system for containers |
• Hacker News comments on CoreOS' new project |
• [Discfg] - a distributed serverless configuration tool |
• Asim's Micro project and its potential |
• Open source projects that the panel is thankful for: |
• CoreOS (Brian) |
• State Management for Go (Carlisia) |
• Postfix (Asim) |
• VLC (Erik) |
**Erik St. Martin:** It's Go Time! A weekly podcast where we discuss interesting topics around the Go programming language, the community and everything in between. If you currently write Go or aspire to, this is the show for you. |
Alright everybody, welcome back for another episode of Go Time. This is episode number eight. We have a special guest with us today, Asim Aslam, and he is going to talk to us about the Micro framework. And we also have Brian Ketelsen on the line, as always. |
**Brian Ketelsen:** Hello. |
**Erik St. Martin:** And then we have the wonderful Carlisia Thompson also on the line. |
**Carlisia Thompson:** Glad to be here, hello. |
**Erik St. Martin:** Let's have everybody give Asim a warm welcome and if you could give us a brief introduction, a little bit of history about yourself and then we'll kind of roll into the whole Micro framework. |
**Asim Aslam:** Sure. So thanks for having me on the show, I really appreciate it. Basically, my background is that I spent the last ten years in London doing various kind of sys admin, SRE, engineering kind of roles. I worked at a startup, which later got acquired by Google. I spent a bit time at Google learning how t... |
Then I went to work at Hailo and helped build a global microservices platform back in 2013 when, you know, it wasn't really much of a thing. I think Netflix was the only one talking about it. |
Now I'm working on this thing called Micro. I realized everyone was really doing the same thing internally at companies, and it would be nice if there was a community project that was doing the same, where we could all contribute and kind of learn and benefit from it, and basically do this thing of simplifying, buildin... |
**Erik St. Martin:** So when I first saw Micro, I think, the thing that impressed me most and this was February of last year, it's been quite awhile; but the thing that impressed me most was the design decisions that you've made seemed to be - what's the word I'm trying to think... It encapsulates almost everything you... |
**Asim Aslam:** Thanks. I guess the wording is always hard. You can kind of go back and forth and on what it should be, but learning from the experiences of building something within a company... A library does not suffice, a toolkit does not suffice. We essentially build platform as a service or microservices platform... |
So when I built this, I really thought about what are the fundamental building blocks, how would you do if you built it open source first? So it needs to be pluggable... And it slowly evolved. I mean, it started as just Go Micro - the kind of core project - and now it's this bigger thing and I'm calling it an ecosystem... |
**Carlisia Thompson:** \[04:25\] Before we geek out on Micro, Asim, it seems that you're working exclusively on Micro. Is that true? And if so, what is the financial sustainability plan for the project and for yourself? |
**Asim Aslam:** Sure. That's right, I'm working on it full-time. Basically, I quit my job at Hailo over a year ago, because I felt so strongly about this and I wanted to build this. At the time I was talking to some venture capitalists, so the plan was, "Hey, I' m gonna raise this money, build this team and we're gonna... |
**Carlisia Thompson:** Very cool. |
**Brian Ketelsen:** Yeah, I always love to hear projects that work that way where people get sponsored to work on them full-time. Because I know a lot of people get really passionate about their open source projects and a lot of times they become abandoned when they move on to new places that no longer sponsor. |
**Asim Aslam:** It's really tough. I think I got very, very lucky in the sense that this friend of mine who I had worked with closely was going to this large enterprise company, and he could see the value and he knew exactly what I was planning to do and was willing to kind of help out in that way. And many people who ... |
**Brian Ketelsen:** So let's talk about adoption. Do you have any sense of the numbers or scale of companies that have deployed services with Micro? |
**Asim Aslam:** I set up a users page and there's about four companies listed there, a couple of which have gone to production. You can find that in the main repository in the Wiki. There are maybe about five or six other companies who kind of did a survey and said they would be on the way to production in next three o... |
The growth is slow and nice. I think the nice thing is there's a Slack where everyone joins, individuals and companies come along and kind of talk about their uses, and people are using it without me even knowing. For some reason it's really taking off in China, which is really, really nice to see, and someone even tra... |
\[07:53\] Here in London I just met with a company called Kazoop, and they have essentially posted the first job listing including Micro. For me, that's really profound, that someone thinks so much of it that they wanna put it in a job listing and kind of say, "Hey, we're moving over to this framework and here's what w... |
**Brian Ketelsen:** Are they looking for a developer with ten years of experience? |
**Asim Aslam:** \[Laughter\] No. They're looking for someone who knows Go and wants to build microservices and can kind of do this stuff. I think the awesome thing about microservices in general, these things are maybe less than a thousand lines of code. It's very domain-specific what you're building, so it doesn't req... |
People learning Go for the first time could probably do this, because what really matters is the API at the end of the day, the interface to that application that you're communicating with. The code is irrelevant, because you could rewrite that anytime in the future. |
**Brian Ketelsen:** That brings up an interesting question - what do you feel philosophically is the delineation point between a Microservice and something that's bigger than a Microservice? |
**Asim Aslam:** That's a tough one. For me, what I found is it's whatever I can kind of keep in my head and still feels fairly simple, and having written a lot of Go in the last three or four years and actually having built a microservices platform, I would say a lot of the time it does fall into a thousand to two thou... |
You know every language has a different kind of syntax, therefore it's gonna come down to a certain numbers of lines. For Go it feels naturally like that, but you kind of know a lot of the time, because this is a philosophy - you know from looking at the code if it takes longer than a week to do something, then you kno... |
**Carlisia Thompson:** That's an interesting measure, because I am thinking at the beginning when you're designing something - maybe that's what you mean - at the design/creation time how much you can hold it in your head; because for me as time goes by more and more and I'm working with the codebase... I mean, two yea... |
**Asim Aslam:** Yeah, it's interesting... I mean, I agree in that the longer you go, the more you can kind of remember about it and kind of model in your head. But at the same time, if you leave the project for a little while and come back, how long does it take you to kind of build that model again? For me, it's the c... |
End of preview. Expand in Data Studio
2016 Go Time Transcripts
Complete transcripts from the 2016 episodes of the Go Time podcast.
Generated from this GitHub repository.
- Downloads last month
- 128