Facilitate seamless communication between client and server; not only at run-time but throughout the entire development process.

Without further ado, here is the repo: https://github.com/jczacharia/orcha
Note: within the repo contains a fully-featured example todo app.
Also, here is the user authentication starter repo you can use for starting your own Orcha projects: https://github.com/jczacharia/orcha-user-auth-starter

What is OrchaJS?

OrchaJS is a framework to safely, securely, and efficiently build scalable web apps requiring real-world, highly relational domain modeling and essential features such as user authentication, file uploading, pagination, and real-time updates. All while providing an unprecedented developer experience.

In a nutshell, OrchaJS uses a project-specific monorepository…

Managing the state of Angular components can become complex as your component grows.

A simple approach to handle your component’s state is with component member variables and Angular’s default change detection. However, this approach is flawed for two reasons:

  1. Difficulty Scaling: Your component quickly becomes cluttered with member variables and messy templates.
  2. Performance Issues: You lack control over Angular’s change detection, ultimately hurting your application’s performance. This is because default change detection will run multiple times whenever a change is detected within the component: e.g. user events, timers, XHR, promises, etc. …

Photo by Sven Mieke on Unsplash

I love type-safety. I love it so much that I felt compelled to write an article about how you can leverage Typescript in a monorepository using Domain-Driven-Design housing both the frontend and backend of an application architected for code reusability, maintainability, scalability, and type-safety.


It’s often the case that an application is split into two different repositories: one for the frontend, one for the backend. The problem with this approach is that you need to maintain two separate codebases with the only link between the two being the developers or a third-party. Wouldn’t it be better to have the compiler…

Source: Unsplash

It is often the case that the user of an application must wait while a request to a back-end is being processed. Usually, a loader is shown during that time to tell the user that stuff is happening. That’s good UX. When implementing a loader, I found myself repeating code that: shows a loader, awaits task completion, then closes the loader. So why not create a helper function that enhances this common pattern?

In this example, there is a loading controller service that shows a popup of a loader.

Load Task

Since this is an async function, each line with…

Jeremy C. Zacharia

Software Engineer at IQ Inc.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store