forked from gophercon/2016-talks
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request gophercon#28 from raphael/master
Update README of "Building Microservices From Design With goa"
- Loading branch information
Showing
1 changed file
with
17 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,18 @@ | ||
# Building Microservices From Design With goa | ||
## Building Microservices From Design With goa | ||
|
||
Slides for GopherCon 2016 talk. | ||
Raphael Simon, July 2016 | ||
|
||
[@rgsimon](https://twitter.com/rgsimon) | ||
|
||
goa presents a novel approach to developing microservices in Go that starts with the design. It is | ||
comprised of three parts: | ||
|
||
* The goa design language is a Go DSL that makes it possible to describe the microservice APIs. | ||
* The goagen tool generates boilerplate code and documentation from the DSL. | ||
* The goa library is used by both the generated and user code to implement the microservice. | ||
|
||
This talk will go over the rationale for goa and explain the benefits of the approach. Writing the | ||
design in code has many advantages compared to the traditional descriptive approaches. goa presents | ||
benefits to both API developers and API reviewers. | ||
|
||
[View the slides online](http://talks.goa.design/slides/gophercon2016/goa.slide#2) |