Former-commit-id: 4ce6dff93c58c6f81247065228d194e7e220db7d
18 KiB
Iris is an efficient and well-designed toolbox with robust set of features.
Write your own
perfect high-performance web applications
with unlimited potentials and portability.
Hashtag #Not_Just_YAWF
Iris is fully vendored. That means it is independent of any API changes in the used libraries and will work seamlessly in the future!
The size of the executable file is a critical part of the Application Deployment Process,
I made two very simple identical applications, the first written with a famous mini web framework named gin
(=a Router, with logger, recover and pure Context out-of-the-box support) and the second in iris
(=every feature that you will need at the first place is bundled when you install Iris. Including sessions, websockets, typescript support, a cloud-editor, the view engine with 5 different template parsers, two Routers to select from, an end-to-end framework to test your API, more than 60 handy helpers via Context, complete rest API implementation, and cors, basicauth, internalization i18n, logger and recover middleware out-of-the-box).
I ran go build
for both of them,
- gin had
9.029 KB
overall file size, - iris had
8.505 KB
overall file size! - net/http had produced an executable file with
5.380 KB
size.
The app didn't used any third-party library. If you test the same thing I test and adapt other features like sessions and websockets then the size of
gin
andnet/http
could be doubled whileiris
' overall file size will remain almost the same.
Applications that are written using Iris produce smaller file size even if they use more features than a simple router library!
Q: How is that possible?
A: The Iris' vendor was done manually without any third-party tool. That means that I had the chance to remove any unnecessary code that Iris never uses internally.
Always follows the latest trends and best practices. Iris is the Secret To Staying One Step Ahead of Your Competition.
Iris is a high-performance tool, but it doesn't stops there. Performance depends on your application too, Iris helps you to make the right choices on every step.
Familiar and easy API. Sinatra-like REST API.
Contains examples and documentation for all its features.
Iris is a low-level access
web framework, you always know what you're doing.
You'll never miss a thing from net/http
, but if you do on some point, no problem because Iris is fully compatible with stdlib, you still have access to http.ResponseWriter
and http.Request
, you can adapt any third-party middleware of form func(http.ResponseWriter, *http.Request, next http.HandlerFunc)
as well.
Iris is a community-driven project, you suggest and I code.
Unlike other repositories, this one is very active. When you post an issue, you get an answer at the next couple of minutes(hours at the worst). If you find a bug, I am obliged to fix that on the same day.
Q: Why this framework is better than alternatives, does the author is, simply, better than other developers?
A: Probably not, I don't think that I'm better than anyone else, I still learning every single day. The answer is that I have all the world's time to code for Iris the whole day, I don't have any obligations to anybody else, except you. I'd describe my self as a very dedicated FOSS developer.
Click the below animation to see what people say about Iris.
Installation
The only requirement is the Go Programming Language, at least 1.8
$ go get gopkg.in/kataras/iris.v6
Documentation
-
Getting Started with Go+Iris http://gopherbook.iris-go.com
-
Navigate through community examples https://github.com/iris-contrib/examples
-
./adaptors and ./middleware contains examples of their usage.
-
HISTORY.md is your best friend, version migrations are released there.
Overview
package main
import (
"gopkg.in/kataras/iris.v6"
"gopkg.in/kataras/iris.v6/adaptors/cors"
"gopkg.in/kataras/iris.v6/adaptors/httprouter"
"gopkg.in/kataras/iris.v6/adaptors/view"
)
func main() {
// Receives optional iris.Configuration{}, see ./configuration.go
// for more.
app := iris.New()
// Order doesn't matter,
// You can split it to different .Adapt calls.
// See ./adaptors folder for more.
app.Adapt(
// adapt a logger which prints all errors to the os.Stdout
iris.DevLogger(),
// adapt the adaptors/httprouter or adaptors/gorillamux
httprouter.New(),
// 5 template engines are supported out-of-the-box:
//
// - standard html/template
// - amber
// - django
// - handlebars
// - pug(jade)
//
// Use the html standard engine for all files inside "./views" folder with extension ".html"
view.HTML("./views", ".html"),
// Cors wrapper to the entire application, allow all origins.
cors.New(cors.Options{AllowedOrigins: []string{"*"}}))
// http://localhost:6300
// Method: "GET"
// Render ./views/index.html
app.Get("/", func(ctx *iris.Context) {
ctx.Render("index.html", iris.Map{"Title": "Page Title"}, iris.RenderOptions{"gzip": true})
})
// Group routes, optionally: share middleware, template layout and custom http errors.
userAPI := app.Party("/users", userAPIMiddleware).
Layout("layouts/userLayout.html")
{
// Fire userNotFoundHandler when Not Found
// inside http://localhost:6300/users/*anything
userAPI.OnError(404, userNotFoundHandler)
// http://localhost:6300/users
// Method: "GET"
userAPI.Get("/", getAllHandler)
// http://localhost:6300/users/42
// Method: "GET"
userAPI.Get("/:id", getByIDHandler)
// http://localhost:6300/users
// Method: "POST"
userAPI.Post("/", saveUserHandler)
}
// Start the server at 127.0.0.1:6300
app.Listen(":6300")
}
func userAPIMiddleware(ctx *iris.Context) {
// your code here...
println("Request: " + ctx.Path())
ctx.Next() // go to the next handler(s)
}
func userNotFoundHandler(ctx *iris.Context) {
// your code here...
ctx.HTML(iris.StatusNotFound, "<h1> User page not found </h1>")
}
func getAllHandler(ctx *iris.Context) {
// your code here...
}
func getByIDHandler(ctx *iris.Context) {
// take the :id from the path, parse to integer
// and set it to the new userID local variable.
userID, _ := ctx.ParamInt("id")
// userRepo, imaginary database service <- your only job.
user := userRepo.GetByID(userID)
// send back a response to the client,
// .JSON: content type as application/json; charset="utf-8"
// iris.StatusOK: with 200 http status code.
//
// send user as it is or make use of any json valid golang type,
// like the iris.Map{"username" : user.Username}.
ctx.JSON(iris.StatusOK, user)
}
func saveUserHandler(ctx *iris.Context) {
// your code here...
}
Reload on source code changes
$ go get -u github.com/kataras/rizla
$ cd $GOPATH/src/mywebapp
$ rizla run main.go
Reload templates on each incoming request
app.Adapt(view.HTML("./views", ".html").Reload(true))
Third Party Middleware
Iris has its own middleware form of func(ctx *iris.Context)
but it's also compatible with all net/http
middleware forms using iris.ToHandler, i.e Negroni's middleware form of func(w http.ResponseWriter, r *http.Request, next http.HandlerFunc)
.
Here is a small list of Iris compatible middleware, I'm sure you can find more! Feel free to put up a PR your middleware if you have built one :
Middleware | Author | Description |
---|---|---|
binding | Matt Holt | Data binding from HTTP requests into structs |
cloudwatch | Colin Steele | AWS cloudwatch metrics middleware |
csp | Awake Networks | Content Security Policy (CSP) support |
delay | Jeff Martinez | Add delays/latency to endpoints. Useful when testing effects of high latency |
New Relic Go Agent | Yadvendar Champawat | Official New Relic Go Agent (currently in beta) |
gorelic | Jingwen Owen Ou | New Relic agent for Go runtime |
JWT Middleware | Auth0 | Middleware checks for a JWT on the Authorization header on incoming requests and decodes it |
logrus | Dan Buch | Logrus-based logger |
onthefly | Alexander Rødseth | Generate TinySVG, HTML and CSS on the fly |
permissions2 | Alexander Rødseth | Cookies, users and permissions |
prometheus | Rene Zbinden | Easily create metrics endpoint for the prometheus instrumentation tool |
render | Cory Jacobsen | Render JSON, XML and HTML templates |
RestGate | Prasanga Siripala | Secure authentication for REST API endpoints |
secure | Cory Jacobsen | Middleware that implements a few quick security wins |
stats | Florent Messa | Store information about your web application (response time, etc.) |
VanGoH | Taylor Wrobel | Configurable AWS-Style HMAC authentication middleware |
xrequestid | Andrea Franz | Middleware that assigns a random X-Request-Id header to each request |
digits | Bilal Amarni | Middleware that handles Twitter Digits authentication |
FAQ
Explore these questions and join to our community chat!
Testing
You can find End-To-End test examples by navigating to the source code.
A simple test is located to ./httptest/_example/main_test.go
Read more about gavv's httpexpect.
Philosophy
The Iris philosophy is to provide robust tooling for HTTP, making it a great solution for single page applications, web sites, hybrids, or public HTTP APIs. Keep note that, today, iris is faster than nginx itself.
Iris does not force you to use any specific ORM or template engine. With support for the most used template engines (6+), you can quickly craft the perfect application.
People & Support
The author of Iris is @kataras.
The Success of Iris belongs to YOU with your bug reports and feature requests that made this Framework so Unique.
Who is kataras?
Hi, my name is Gerasimos Maropoulos and I'm the author of this project, let me put a few words about me.
I started to design Iris the night of the 13 March 2016, some weeks later, iris started to became famous and I have to fix many issues and implement new features, but I didn't have time to work on Iris because I had a part time job and the (software engineering) colleague which I studied.
I wanted to make iris' users proud of the framework they're using, so I decided to interrupt my studies and colleague, two days later I left from my part time job also.
Today I spend all my days and nights coding for Iris, and I'm happy about this, therefore I have zero incoming value.
- Star the project, will help you to follow the upcoming features.
- Donate, if you can afford any cost.
- Write an article about Iris or even post a Tweet.
- Do Pull Requests on the iris-contrib organisation's repositories, like book, examples and to gopherbook.
If you are interested in contributing to the Iris project, please see the document CONTRIBUTING.
Contact
Besides the fact that we have a community chat for questions or reports and ideas, stackoverflow section for generic go+iris questions and the github issues for bug reports and feature requests, you can also contact with me, as a person who is always open to help you:
Versioning
Current: v6, code-named as "√Νεxτ"
v5: https://github.com/kataras/iris/tree/5.0.0
License
Unless otherwise noted, the source files are distributed under the MIT License found in the LICENSE file.
Note that some optional components that you may use with Iris requires different license agreements.
TODO
- Refactor the Examples to be align with the latest version
- Upgrade GitBook for the latest release
- Add some missing tests from the previous version and find a way to share these end-to-end tests accross the adaptors and the root
- Replace http://iris-go.com content to something more fancy, as suggested here
- Make a table list of the most famous middleware(s) with their descriptions, in order to help new Gophers find what they're looking for
Iris is a Community-Driven project waiting for your feature requests!