Spoonity Generation 3
  • Preamble
  • Company
    • Product Strategy
      • Sales and Marketing
      • Support
    • Onboarding
    • Development
    • Partnerships
    • Summary
  • Tools
    • Ingestion Services
      • Point of Sales
      • Importing Tool
    • OnScreen
    • Dashboard
    • Widgets
    • Summary
  • Product
    • Cache
    • Delphi
    • Drachmae
    • Lydia
    • Hermes
  • Architecture
    • Events
      • The Nexus
    • Cloud
    • Multi-Tenancy
    • Spoonity Apps
      • Technical Overview
  • Case Studies
    • Large Bubble Tea Chain
    • Sports Apparel Retail
    • Family-Owned Grocer
    • Neighbourhood Dentist Office
Powered by GitBook
On this page
  • Microservices
  • Philosophies of Software Design
  • Releases and Deployment
  1. Company

Development

PreviousOnboardingNextPartnerships

Last updated 4 years ago

Microservices

The development focus of our new generation will be on microservices, and the logical separation of concerns. This is a long-held application design philosophy called .

SRP is just one aspect of the approach to software development.

Applying this principle at architecture level will allow us to break out our services into independent units, which will increase productivity, reduce regressions, and allow for greater flexibility.

Another important benefit is improving our softwares ability to scale. This includes both a runtime context (support more users, run faster, etc), and an operational context (more developers, easier to work with, etc).

Philosophies of Software Design

In previous discussions regarding the next-generation of the Spoonity platform, we discussed the four guiding principles which we would use to build it. Those principles will make up the framework for how decisions are made in regards to the product and platform, and how they are justified.

Those core philosophies are:

Scalability: to design a solution that could naturally scale with our clients with minimal effort, disruption, and cost.

Stability: to deliver a solution that is error-resistant and easy to diagnose, and allows us to be proactive instead of reactive in its defence.

Maintainability: to implement solutions that promote a healthy environment for continued development without introducing new risks to our stated goals.

Extensibility: to provide opportunities to both ourselves and third-parties to easily and effectively interact with the core platform components.

With our growing full-stack approach, developers should be comfortable working in and contributing to any software project within the Spoonity ecosystem.

Additionally, more responsibility in helping scope feature requests, and support enterprise client onboarding in a consulting capacity would be approved.

Releases and Deployment

Additionally, it comes with baked-in support for automated and controlled software deployments. Changes can be tested, released, and deployed to all of our clients simultaneously in an automated fashion, with no disruption to our clients.

The Spoonity development lifecycle requires little effort to integrate these processes, and should save us hours each week.

These aspects are meant to be used pro-actively as the product is developed. Together, they will ensure a robust, durable, and efficient product that delights customers, makes our work simpler, and allows us to developer lasting relationships with .

Our software services will be deployed on , an orchestration engine for application containers. Kubernetes is an ideal candidate for working with microservices, and provides inherent strengths in support a service's scalability and reliability.

This process is called continuous integration/deployment, or .

partners
Kubernetes
CI/CD
Single Responsibility Principle
SOLID
333KB
Generation 3 Platform.pdf
pdf
Generation 3 Overview