Simplicity is the ultimate sophistication Leonardo da Vinci, 1452



Modern microservices... they're fast and scalable and resilient (if you do them right)... but still slow to develop, using the same old IDEs, languages and processes! We're working on a project to accelerate development of microservices and integration applications, using a low code environment, reactive flows, lambda hosting and other cool technologies.

With an account, you can create your own micro "lambda" services, very useful for prototyping, mocking or testing - see some examples below.


Mocking microservices


One basic need in developing distributed applications is mocking other systems - you can use a simple DSL environment to rapidly create and mock 3rd party REST services:

$mock say.hi (name ?= "Harry") => (greeting = "Hello, " + name)


Click on the REST to get the URLs and test this, click on Run to see it run or... click on Edit and experiment on your own, even without creating an account!


Having an API can be easy - here's one just above (one that you can edit and fiddle with). In fact, this is also the simplest microservice you could have ever created (read more)


Interested in accelerating microservices development ? ...

Testing microservices

Testing your own microservices is really simple, with a framework to express and bind together test cases and business requirements - click on run to see this test pass...

$send say.hi (name = "Jane")
$expect (greeting contains "Jane")


That's all nice and dandy, but what if some test fails? What if one of the three hundred requirements/tests fail? Can you easily figure out what happened and get to the source of it? With our framework, you can! Click on Run below and see what happens when you get a different value for instance...

$send say.hi (name = "Jane")
$expect (greeting contains "Mitch")

While most testing frameworks will point out the error, they won't help you in figuring out what happened, so you end up having to go to some log file or inspect code or such. By pointing out exactly where the discrepancy is and where it came from, it is very easy to tell what happened and debug any deviation from the original requirement/test. This simple approach will speed up development significantly, compared to traditional frameworks.



How do we specify our expectations about the value? How do we communicate it, record it, share it, cooperate on it?



Use cases and user stories can turn into automated tests! (one that you can run and trace right now) (read more)




APIs are often much less interesting than the stories they tell... or the stories you can create with them, i.e. systems, apps etc. The behaviour of these systems as a whole... that's where the value of the system is.



Interested in simplifying microservices testing? ...


In the modern age, enterprises are transformed by microservices, APIs and reactive principles.

If you want to take a refreshing look at microservices requirements, acceptance and truly continuous testing, while fiddling with the architecture itself, start by creating a free account.






Was this useful?    

By: Razie | 2016-10-18 .. 2019-03-30 | Tags: admin


Viewed 116357 times ( | Print ) this page.