DEVOPS We strive for efficiency
At Resimator, we follow the agile software development approach and we like to make the best use of industry standard tools, opensource technologies and devops practises. We are transparent and involve our customers actively during the development and delivery cycle based on project size.
Our customers are added in our internal group slack/mattermost channels and are timely updated regarding latest decisions or build releases. The whole objective of the project is broken down into several iterations. We will create a suitable sprint and release plan for each iteration. There will be a weekly / bi-weekly meeting before each sprint where we discuss and confirm the requirements for the upcoming sprint. Similarly, we take feedback for past sprint’s tasks and try to implement them in upcoming sprint. During this whole process, you will be working closely with developers, allowing you to get a clear picture of how the development process is going on.
We tend to keep the release cycles fast and short, so that you can get new applications and features in a quick and reliable way. In order to keep the process smooth, we adopt the devops practice at our best.
THE WAY WE WORK End-to-End Development Approach
Maintenance and Support
WORKING PHASES Development Process in detail
Maintenance and support
THE WAY WE WORK What devOps as a service gives
Increase Productivity of the org
Automation of tasks
Deliver product faster
Frequent feedback loops
Easy/timely bug tracking and debugging
Technology Core Tools we use for better software development
Mobile App (Android, iOS, Tizen)
- React Native
- Google Engine
Project Management & Documentation
JIRA - Project Management
Confluence - Documentation
Slack or Mattermost - Communication
Swagger - API documentation
CI/CD - Bitbucket pipeline, Github
Other tools - Dockers, Kubernetes
Third-party API Integrations
- Accounting, Payments, IOT platforms, AI platforms, AWS, Google cloud, etc.
Devices and platforms
- Samsung Kiosks
- Elo Kiosks
We create three different environments for testing and deployment purposes.
A test server is deployed in order to facilitate developers to test the features in a remote environment. The server is mainly used by developers and may contain error prone features as well. Thus, the client is not supposed to have access to the server.
A server is created with identical configuration details and database data to the production environment. Clients will use this server to test the feature from their prospective and confirm if the features are production ready. Team members are required to publish error free, tested versions of code to the staging environment.
A production server is the one that is available to the end user's usage. A good amount of testing, manual and automated needs to be carried out before pushing the code to production.