Introduction to Iron Functions with Iron.io
Built with a microservices architecture and utilizing Docker containers, Iron.io has transformed the way job processing is built and deployed. Architects and developers benefit from the microservices approach that separates components into discrete functional elements or individual services. This model reduces complexity, while increasing scalability. Smaller, more granular compute services which can be developed and deployed independently are easier to maintain, repair, and update.
Iron.io is language agnostic for greater flexibility when developing and deploys on any cloud or hybrid for flexibility and control of enterprise applications. When managed or hosted services are included, developers have a true serverless experience.
Outline/structure of the Session
Lightning talk.
Learning Outcome
Iron.io introduction.
Target Audience
Anyone
Links
https://github.com/iron-io/functions
schedule Submitted 4 months ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
Alex Papadimoulis - DevOps for Japan
45 mins
Talk
Beginner
DevOps represents a simple idea: increase collaboration across teams while automating processes. Although the concept is relatively new to Japan, American IT organizations have been trying to implement DevOps in recent years: many have found success, while others have seen failure.
One of main causes of failure is adopting the wrong culture. Although companies like Netflix and Etsy dominate the DevOps conversation, most enterprises do not have the same problems to solve, nor do they employee the same types of engineers. Thus simply, attempting to emulate Netflix will often yield failure.
It’s similar in Japan; the culture of Japanese IT organizations are quite different from western companies, and attempting to emulate western DevOps practices will often result in failure and other setbacks. Thus, in order to be successful with adopting DevOps practices, those practices must first be adapted for Japan.
In this talk, I’ll compare and contrast the unique cultural differences in Japanese IT organizations and discuss how you can adopt DevOps practices that specifically address those.
-
Comments