Back to Home

ObjectServe Engineering Tenets

These tenets define the core principles that guide our development, consulting, and training. They serve as our quality bar for building software that doesn't just work, but thrives in production.

1. Application Portability

Application remain portable across vendors, platforms, and cloud providers, making the migration of data or applications cost-effective and timely.

Provider-agnostic Core: Core business logic remains independent of any provider. Integrations with proprietary systems are implemented as adapters — never as the foundation.
No Deep Vendor Lock-in: We design systems using well-established open-source and cloud native standards to ensure switching vendors is possible without rewriting the core business logic.

What this rules out:

  • Cloud-specific code mixed into the business logic
  • Exorbitant hidden operational costs
  • Difficult Migrations

2. Coding Practices

Adhering to disciplined coding practices ensures the codebase remains clean, maintainable, readable, and easy to audit, enabling effective collaboration across teams.

Key Guidelines: We use git version control, write unit tests, document code, adhere to DRY (Don't Repeat Yourself), and apply SOLID and proven design patterns wherever appropriate.
Distinct layers of code: We organize codebase into distinct layers (e.g., Presentation, Business, Data Access), enforcing strict separation of concerns through well-defined interfaces, dependency inversion, and modular boundaries.

What this rules out:

  • Inconsistent, messy code that is difficult to read
  • Recurring bugs caused by poorly organized structure
  • Slow onboarding for new developers

3. Non-Functional Requirements

Performant, secure, scalable, highly-available, fault-tolerant, and resilient distributed applications are requirements, not nice-to-haves.

Performance and Scalability: We apply stateless design, CQRS-like patterns, caching at appropriate layers, and event-driven architecture using streaming platforms like Kafka to sustain real-world load.
Zero-downtime Failover: We leverage cloud-native techniques like Kubernetes for automated self-healing and multi-zone automated data distribution eliminating single points of failure.
Resiliency Techniques: We ensure seamless recovery via automated retries, protected by intelligent throttling and backpressure to prevent cascading failures.

What this rules out:

  • Manual failover dependencies
  • Frequent timeouts
  • Systems that stop responding under peak load

4. Reliable Software

We extend quality beyond the basics — while unit and E2E tests are vital, place equal emphasis on performance, regression, security, and UAT

Test-Driven Development: Writing unit tests before the functional code naturally encourages developers to proactively identify and address edge cases.
CI/CD based Testing: Automated software tests are integrated directly into the CI/CD pipelines thereby accelerating software delivery and improving code quality.

What this rules out:

  • Manual testing efforts
  • Fragility under edge-case conditions
  • Security vulnerabilities in the delivery pipeline

How We Enforce Our Tenets

Our core principles are embedded into our day-to-day engineering workflow through:

Architecture Validation

Frequently ignored by others, we validate the NFRs early through load testing, security audits, and structured design walkthroughs to catch architectural flaws before implementation begins.

Strict Engineering Standards

We do not compromise on code quality, emphasizing functional programming principles, TDD, rigourous QA, dual reviews for complex changes, idempotent operations, and immutable data patterns.

Static Analysis Tools

We use automated scanning tools that detect vulnerable patterns, overly complex functions, duplication, and performance regression checks before code even reaches human review.

Post-Production Governance

Production systems are monitored using real-time alerts and logs. When defects arise, we resolve them promptly and conduct root cause analysis to eliminate underlying causes and prevent recurrence.

Website is undergoing maintenance