Startup Success: Introducing Startup OS with DevOps and DevSecOps Integration

Concept of Startup OS

Startup OS is a platform that supports early-stage startups in validating their ideas, building MVPs, and achieving product-market fit. It offers a range of features, including a step-by-step approach and access to tools and resources, as well as integration with popular tools and platforms. It also supports a variety of programming languages and frameworks and provides regular check-ins with a dedicated Product Owner. Startup OS aims to increase the number of startups and their chances of success.

Industry: Business & Startup

Startup OS: DevOps and DevSecOps Integration

Our Process

Conceptualization

  • Requirement analysis
  • Market analysis
  • Existing workflow analysis/ understanding

Design

Development

Deployment

Challenges We Faced + Solutions We Implemented While Building This Web Mapping Platform

 

Building our Web Mapping Platform was no easy task. We had some big challenges, especially when we tried to make Mapbox work just right for our needs. We had to create special parts and put shapes on top of each other, which was pretty tough. But we didn’t give up! We made lots of changes to get things just the way we wanted, and it all worked out in the end. Let’s talk about how we did it.

1

Optimizing Geojson Rendering and Performance

A major hurdle involved rendering routes/polygons from a 50MB geojson file. The process was time-intensive due to the need for constant loading and route searching.

Solution:

To make things work better, our DevOps pro split the big geojson file into smaller pieces. This helped the MLOps system run faster. We also added a system to store data temporarily, which made everything work much smoother. And, we made a special system to make finding routes faster when dealing with a big 50MB geojson file.
2

Adapting to Large Data and Local Storage Constraints

Dealing with substantial data volumes and local storage presented another obstacle. While initially storing route data locally seemed effective, as routes expanded, browser limitations led to storage exceptions.

Solution:

To fix the problem, our DevOps experts changed how we share data in our app. We used a method called "props" to do this, which made our app run smoothly and work better. We also made sure our app can handle lots of data without any issues. Finally, our team created a special system to manage data and used smart strategies to solve the problem.
3

Overcoming Geojson Loading and Browser Limitation

While loading route polygons from server-fetched geojson files, our approach of using continuous Ajax calls to accommodate the numerous split files (thousands in total) led to challenges. This triggered browser errors, citing “Insufficient resources.”

Solution:

Our DevOps expert fixed the problem by making a system that waits in line for calls and automates deploying software updates. We also made a faster way to get and manage files, which saved computer resources and got rid of the "Not enough resources" errors.

Results We Achieved to Build this Web Mapping Platform Through DevOps

During our project, we confronted the challenge of tailoring Mapbox to our specifications and customizing components and polygon overlays. In Sprint 1, leveraging playground access, we focused on UI design and API architecture.

Setting up vital API calls and implementing Sockets were pivotal. With two ReactJS developers and QA, one developer concentrated on UI finalization, while the other wired APIs and conducted tests. With robust QA for CI/CD, we implemented test case creation and detailed Jira backlog user stories.

Our GraphQL-based backend evolved. Sprint planning commenced, aligning tasks, priorities, and estimates. Task comprehension, including necessary APIs and responses, was ensured. Agile adaptation enabled us to manage changes and unexpected API shifts effectively.

We established CI/CD, merging code upon story completion for QA testing. Agile approaches, dedicated QA, and proactive planning led to bug detection and smoother development, exemplifying our successful outcome. In this project, our team used a range of CI/CD tools, including Docker, Git, Java, Linux, and Ubuntu. Lastly, the client was happy with our high availability/disaster recovery capabilities for production systems.

 

Want to leverage the power of DevOps with DevSecOps?

Our team can help you with that!

Find out more about how Mindbowser created a solution

Get a detailed case study here

Check out some of our other case studies

Know how we delighted our customers

Mindbowser is excited to meet healthcare industry leaders and experts from across the globe. Join us from Feb 25th to 28th, 2024, at ViVE 2024 Los Angeles.

Learn More

Let's create something together!