Group: GitHub Unircs

Sort by:Popular▼

✓Popular✓Newest

Shared infrastructure and cross-cutting concerns (extensibility, error handling, i18n, caching, security, pagination) reused across every vertical domain module.

Shared core domain (users vertical): controllers, use cases, DTOs, JPA entities/repositories and mail infrastructure, consumed by the core microservice and the monolith. Core owns its data, so entities are identical across topologies and shared ...

Deployment-agnostic engagement domain: controllers, use cases, DTOs and persistence ports. Data access is provided per deployment via adapters.

Deployment-agnostic leisure domain: controllers, use cases, DTOs and persistence ports for city places, routes and public spaces. JPA entities are provided per deployment via adapters.

Deployment-agnostic mobility domain: controllers, use cases, DTOs and persistence ports for cars, street reservations and sanctions. JPA entities, Stripe config and webhooks are provided per deployment.

Maven archetype that scaffolds a concrete city's microservices deployable from the Model City platform. Generates an aggregator project with Eureka service registry, API gateway and one Spring Boot app per vertical (core, engagement, ...

Maven archetype that scaffolds a concrete city's monolith deployable from the Model City platform. Generates a single Spring Boot application bundling every vertical (core, engagement, leisure, mobility) and the Auth0 OAuth2 security ...

Phase-4 topology-specific persistence for the engagement vertical (concrete SecurityAlert, CivicQuestion, Objective, Answer and EngagementTrail entities, repositories and upstream Default*Store adapters — soft references only, no ...

Phase-4 topology-specific persistence for the engagement vertical (concrete SecurityAlert, CivicQuestion, Objective, Answer and EngagementTrail entities, repositories and upstream Default*Store adapters — real @ManyToOne navigations ...

Phase-4 prototype: topology-specific persistence for the leisure events vertical (concrete EventTicket entity, repository and upstream Default EventTicketStore adapter). Pairs with the invariant @MappedSuperclass EventTicketBase in ...

Phase-4 prototype: topology-specific persistence for the leisure events vertical (concrete EventTicket entity, repository and upstream Default EventTicketStore adapter). Pairs with the invariant @MappedSuperclass EventTicketBase in ...

Phase-4 topology-specific persistence for the mobility vertical (concrete Car, StreetReservation, Sanction and MobilityTrail entities, repositories and upstream Default*Store adapters — soft references only, no core-domain FKs). Pairs ...

Phase-4 topology-specific persistence for the mobility vertical (concrete Car, StreetReservation, Sanction and MobilityTrail entities, repositories and upstream Default*Store adapters — real @ManyToOne navigations to core-domain ...

Model City — an extensible smart-city back-end platform for municipalities