Former-commit-id: 6ef71a4b9f5a79160a42d1111dd924e244ce1f4e
13 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.
Powered by Google's Go.
# Not 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!
Iris follows the latest tech trends around the world.
Iris' features are visible to other web frameworks after some time. That means that Iris is followed by other go web frameworks.
The executable file size is a critical part of Application Deployment process.
I made two very simple identical applications, the first written with a famous mini web framework named gin
(=Just a Router, with logger, recover and pure Context 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).
I ran go build
for both of them,
- the first had
9.029 KB
overall file size, - the second had
8.505 KB
overall file size!
Keep note that the same app written in pure net/http
had produced an executable file with 5.380 KB
size.
Note that these applications doesn't uses any third-party library, they are simple applications, if we used other features like sessions and websockets then the size of gin
and net/http
could be the double, while in the same time iris
' overall file size will remain almost the same.
Result: Iris' executable file size is even smaller than simple router libraries!
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.
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.
Examples and Documentation for the most use cases and if you don't find something, just do an online search of the net/http way and adapt this way to Iris, Iris is not black-magic, I didn't invent the world.
Iris is a low-level web framework, you know what you code on each single line.
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 others, this repository is very active. When you post an issue, you get an answer in the next couple of minutes, hours at the worst. If you find a bug, I am obliged to fix it on the same day.
If you're coming from Node.js world, this is the expressjs for the Go Programming Language.
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 v1.7.
$ go get gopkg.in/kataras/iris.v6
Overview
package main
import (
"gopkg.in/kataras/iris.v6"
"gopkg.in/kataras/iris.v6/adaptors/view"
"gopkg.in/kataras/iris.v6/adaptors/httprouter"
)
func main() {
app := iris.New()
app.Adapt(iris.Devlogger()) // adapt a logger which prints all errors to the os.Stdout
app.Adapt(httprouter.New()) // adapt the adaptors/httprouter or adaptors/gorillamux
// 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"
templates := view.HTML("./views", ".html")
app.Adapt(templates)
// http://localhost:6200
// Method: "GET"
// Render ./views/index.html
app.Get("/", func(ctx *iris.Context) {
ctx.Render("index.html", nil)
})
// 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:6200/users/*anything
userAPI.OnError(404, userNotFoundHandler)
// http://localhost:6200/users
// Method: "GET"
userAPI.Get("/", getAllHandler)
// http://localhost:6200/users/42
// Method: "GET"
userAPI.Get("/:id", getByIDHandler)
// http://localhost:6200/users
// Method: "POST"
userAPI.Post("/", saveUserHandler)
}
// Start the server at 127.0.0.1:6200
app.Listen(":6200")
}
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)
}
TIP: Execute
iris run main.go
to enable hot-reload on .go source code changes.
TIP: Add
templates.Reload(true)
to monitor the template changes.
Documentation
-
The most important is to know where to find the details
-
Navigate through examples
-
HISTORY.md file is your best friend.
Testing
You can find RESTFUL test examples by navigating to the following links:
FAQ
Explore these questions and join to our community chat!
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 and examples.
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.