The Paremus Service Fabric: Making Microservices Manageable ...Â Â Â Â Â Â Â Â Â Â Â Â Â
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
Service Fabricis a distributed runtime platform composed of a population of one or more
Service Fabricis created from a corresponding
fabric profile:this template defines the number and type of Fibres required.
- A Service Fabric may host one or more
- A Fibre is smart OSGi based agent that runs on the host's Java VM: the host may be a physical machine, a virtual machine, or a container.
- A Fibre may host one or more
- A Fibre may act as either:
- `the container` for one or more OSGi assemblies.Â
- `the proxy / controller` for one or more container images.
- A combination of each.
The Fibre is responsible for the creation of any required local Linux container (e.g. Docker), and then container image life-cycle management.
>Â InstallÂ -Â Installing a Service Fabric, minimum requirements & supported platforms.
>Â 8178143736Â - Service Fabric management.
>Â pretournamentÂ - Design Principles, Site Planning and Background Information.
Standards based, non-Opinionated, Modular & Reactive ... Â Â
- A System is a modular distributed Application.Â
- A System is composed of one or more
system.partis composed of one or more colocated
When deploying a System, the Service Fabric will place the required number of
system.part instances upon most appropriate Fibres available. Each instance is dynamically configured by its Fibre host.
system.part.element may be the implementation of a CRUD/REST microservice, an Synchronous or Asynchronous RPC microservice, or a consumer / producer of messages or events.
The Service Fabric automatically enforces appropriate visibility / boundaries for each System's microservices:
- Internal microservices are only visible to other entities within the same System.
- External or Public microservices are visible to third parties.
>Â TutorialsÂ - Introducing Service Fabric concepts and capabilities: both OSGiâ¢ / Java & Polyglot / Container based microservices.