Skip to main content

· 2 min read
Aircampi, Inc.

Hands

As Virginia Burden notes that “Cooperation is the thorough conviction that nobody can get there unless everybody gets there,” a successful business comes down to clever team management. Together as one, it’s important for any team to set goals and objectives that can be achieved efficiently. In our case, it was important for us to determine how to improve our creativity and productivity because we worked mostly on large-scale applications.

The waterfall model follows a top-down approach, going through every step in linear progress. With the waterfall method, it was hard finding employees who met the challenge. We worked on big projects that required complex code logic – something that wasn’t easily grasped upon for a while. Even if we found such a person that took on the difficulty, it was costly to hire those people. Of course, we had an option to train inexperienced employees but it took a great amount of time to reach the desired level, some leaving in the middle of training.

As our “marathon” way was not delivering promising results, we switched to a newer and better way – sprinting. We broke our long journey into shorter paths, setting clear goals with every finish line. Seeing where the finish line was, or, in other words, knowing what to do in short periods facilitates efficiency and productivity. Once we “divide and conquer ''-ed it, we were twice as strong as ever. Dividing our work ensured us that we didn't have to be a perfect all-rounder because assembly of different skills and knowledge cultivates innovative solutions. Everyone had an important role to keep up in the team.

Paths

Teamwork is a valuable commodity and it can make or break an organization. Even though there isn’t a universally acknowledged way, effective team management is certainly achievable regardless of any kind of team. For us, the “sprinter” method ensured us a quick and easy way to work towards our goal. Whether it’s a big or complex project, we are now able to tackle any work much easier than before.

Rather than being perfect individually, we are perfect as one team.

· 2 min read
Aircampi, Inc.

BaaS

In our previous blog, we talked about the struggles we faced with monolithic architecture and why we decided to transition to microservice architecture. To provide a quick recap, monolithic architecture has a single large codebase, making code logic complex and hard to scale. In contrast, as the word “micro” suggests, the microservice architecture allows developers to split their logic into smaller parts, increasing productivity, flexibility, and overall performance. Also, it came with a bonus – a cloud server.

Now, there are essentially two types of ways of hosting and installing apps or soft servers: on-premise and cloud. While most companies use on-premises, cloud computing has been growing in popularity.

On-premise vs Cloud#

On-premise refers to the traditional approach of hosting in which all the resources are accessed and managed from the premises. With on-premise, the companies are responsible for the maintenance of the server hardware. On the other hand, cloud computing involves delivering hosted services over the internet with a third-party provider, requiring the companies to pay for the resources they use.

Thanks to microservice, we have migrated to the cloud without using many resources. The functionalities between a cloud server and a traditional physical data center are the same, but cloud services have several more advantages: security, flexibility, scalability, and cost-effectiveness.

With the usage of the cloud, there comes a variety of service models, each of which caters to a different set of business needs.

We are a backend as a service (BaaS) provider, which is often mistaken with a platform as a service (PaaS).

PaaS vs BaaS#

Platform-as-a-Service (PaaS) provides hardware infrastructure and software resources for developers, offering all the resources required to develop an app over the cloud. Backend-as-a-Service (BaaS) provides developers access to cloud infrastructure and performs backend tasks automation, APIs, backend storage, and ready-made codes. While PaaS offers more flexibility as it is required that developers write their own backend codes, BaaS offers functionalities like user authentication, security, database management, and search. With a BaaS, the developer can focus more on creating frontend design and business logic.

We are#

Aircampi is a platform made to build and scale your backend easily. From simple Single Page Applications to Complex Enterprise Systems, we can manage every level of complexity and scalability. Currently, we offer auth, database, realtime, and storage services, and there will be more to come.

Stay in tune!

· 3 min read
Aircampi, Inc.

BaaS

As backend development is the backbone of any large project, many developers spend a long period of time, energy, money, and resources during production. Our team, too, has gone through the same struggles when we built Complex Enterprise Systems such as “Human Resource and Payroll System” and “Education Sector Information System” for the past decade and spent a total of seven to eight years only for the development of the backend systems for the projects.

Eight years into our work, we found infrastructure solutions to data center, security, search, auth, and many more services; however, as we had monolithic technology – developing and deploying them collectively and running them on the same servers – we faced overloaded servers and problems along the way. Developing or scaling applications with monolithic architecture is challenging as the logic behind every server is connected wholly, and even making small changes to one part of the application requires a change in other parts. Moreover, as the application gets bigger, it was difficult finding good backend developers who met the challenge. Our backend developers needed to have familiarity with many different logical services to successfully manage complex systems.

Aside from the complexity in logic and development, our data center was getting old. Also, because our data center was located here, where we don’t have power backups, power outages were a big problem for us. To prevent it, we wanted to move to cloud services. But monolithic technology was costly as it had too many resources.

With our every sign pointing to a new direction in technology, we found microservice architecture to become our gate to new possibilities. The microservice architecture allows splitting big complex logic into smaller bits. We tested our eight-year work in a short amount of time and found a promising result. Taking a big chunk into smaller pieces lowered complexity and increased productivity, maintenance, and flexibility. It basically not only solved our problems but also made it even better. With our new technology, we wanted to do backend as a service to help people make from simple apps to complex systems and take out the hard work from backend developers to focus more on their desired business logic and frontend design. By using our product, backend developers will be able to build backend services in just a couple of minutes.

Every single step we have taken from up until now, we have accumulated many skills and experiences. This time we took a giant leap for the future of our company, and the direction of our work. We are ready to take your hand and travel through the wonders of our work.

Are you ready for it?