Services

Design, Deploy, Run Cloud Solutions!

Design

Leap from discussions to a cloud solution suggestion!
High level steps below:

  1. Capture your cloud solution requirements as a note
  2. Tag it as “Problem-Domain-Solution” and request an implementation suggestion
  3. Review suggested Note Web DSL and save it
  4. Optional: you can request to get a diagram of suggestion, setup forms for suggested data models and create git repositories

 

Deploy

If suggested Note Web DSL code looks ok, deploy it!

  • Supply connection details for your AWS account in a "Cloud Account" tag
    OR
    (soon)
    grant relevant trust permissions to NoteWeb AWS account
  • Click “Deploy DSL” button
  • Observe deployment progress
  • Inspect newly provisioned resources under your AWS cloud account tag in NoteInWeb.com or jump to resource details directly in AWS web console
 

Run

As you define your request processors in Note Web DSL, Content Delivery Network distributions, load balancers or API gateways, you can define user-friendly DNS names to access actual endpoints.

(soon)Also, NW v9.35 is expected to bring improvements for deployment logs availability and status tracking. This improvements also include deployment summary with a list of resource names, ARNs, endpoint URLs, if available.

Use these endpoint URLs to access deployed APIs and front-end applications

 

Personal Content Management

Organize your files, publications, web resources using unique content model:

 

  • Start with a note, tag accordingly, your web note is ready. It can be a web page, diagram, calendar event, a work context, etc. ... or even several of those, if you apply multiple tags with different functionality!
  • Conveniently manage your tags, define behavior of sub-tags and tagged notes. Examples of supported tag types:
    • cloud account (eg. AWS) - get resource types of interest as sub-tags (eg. buckets, queues, container and Kubernetes services, VMs, VPCs, etc.) Individual resources of the type would be mapped as notes. Linking can occur per cloud provider tag criteria, so that whatever notes you capture for resource remain if it gets re-provisioned.
    • folder for files - a web note is allocated a directory available per WebDAV or via UI. You can manage files, sub-directories or edit files directly in Note Web UI:
      • notebook files - using an embedded Jupyter editor of usual kernel types (Python, Scala, etc.)
      • office files - with an embedded OpenOffice online editor
    • work context - build a bounded context by controlling tags of what types and notes match the context, what operations and web note aspects are available in the scope
    • forms and form documents

    Tag can affect UI of the note - contribute a web note aspect or it can change its behavior. You can even define your own tag types, by implementing handlers of tag lifecycle events in JavaScript.

  • Speaking of work contexts, not only is it a bounded context, but also can have a UI of its own with header, footer, navigation across multiple boards, each board tiled by multiple web notes.
  • Each note, tagged "Files and Links" can be related to tags, contexts and other notes, using Drag and Drop interface.
    Soon: relations would be able to have a type assigned and have a comment.
 

Visualize with Diagrams!

Soon:So you've mapped your web resource to notes and tags, imported or established links between them. Would you like to analyze some particular slice of this data or communicate a concept that relies on dozens of already mapped notes and tags?
Just create a new note, tag it diagram, select notes and tags of interest, drag and drop them onto the diagram view in content panel. Use automatic layout and arrangement and other common diagram editing tooling. Then you can export it as a file or use on a web page.


 

Customization

You participate on a large migration project. It deals with hundreds or even thousands of tables, modules, folders, file systems, services, you name it. Maybe there are more such projects in sight?
How about pulling these entries with only the data you need into a familiar web UI? You'd be able to browse, filter, sort these hundreds and thousands of entries, group and tag it for analysis. Generate diagrams. Just contact Note In Web, Inc. for developing a custom tag type for your needs. Possible common use examples:
  • distributed file systems
  • legacy groupware systems
  • version control systems
  • databases
 



Note In Web, Inc. © September 2022-2025; Denys Havrylov Ⓒ 2018-August 2022