A sneak peek of Global Summit 2018

Hi everyone,

 

are you curious which topics we are going to cover at this year’s Global Summit? You have come to the right place! I will provide you with a sneak peek of what you can expect from the areas I am responsible for.

 

Many of you are building REST interfaces on a daily basis. Since the last Global Summit, a lot has happened and we are going to show you the latest improvements in our REST tooling to make your life easier. We will cover topics like automated documentation and how we integrate with the Swagger ecosystem. Additionally, we will have a big surprise completely changing how you think about building modern APIs!

 

Taking a look at the interoperability landscape we will discuss how you can connect systems faster and provide value to your customers in less time. We will provide you with an overview of how we optimized our toolchain and give you an outlook on how you will build interfaces in the future.

 

Another big topic I discussed with many of you over the last couple of months is the benefit of a microservice architecture. Microservices is a topic you can read a lot about, but it is hard to grasp the benefits and translate them to your environment. What does it really mean to orchestrate multiple services, load balance them, achieve a resilient infrastructure and be able to continuously rollout new updates without downtime? We got you covered. We have prepared a complete experience lab for you to discover the benefits of microservices and to start a conversation about what value it can bring to your environment. Nothing is required except your laptop, but be fast, seating is limited!

 

You will find plenty of opportunities to hear about updates for our client languages and how you can efficiently communicate with InterSystems IRIS from your favorite language.

 

This is just the tip of the iceberg of what you can expect from Global Summit this year. Don’t miss the chance to save $600 with the super early bird discount which expires on Friday, August 10th

Comments

Alternatively...

For those interested in exploring and using MicroServices with all versions of Cache today, QEWD.js has provided a very cool set of Open Source solutions and advanced functionality for a year now.

The full detail is described in the following parts of the Online QEWD.js Course:

https://www.slideshare.net/robtweed/ewd-3-training-course-part-43-using-json-web-tokens-with-qewd-rest-services

https://www.slideshare.net/robtweed/ewd-3-training-course-part-44-creating-microservices-with-qewdjs

https://www.slideshare.net/robtweed/ewd-3-training-course-part-45-using-qewds-advanced-microservice-functionality

And QEWD.js is an ideal and very powerful, modern Open Source REST platform for Cache.  See:

https://www.slideshare.net/robtweed/ewd-3-training-course-part-31-ewdxpress-for-web-and-rest-services

 And all for free :-)

As QEWD makes use of the InterSystems Node.js connector which is available for both Cache and IRIS, the answer is yes. 

If you can provide me access to an IRIS system on GCP Cloud, then sure.

What functionality would you like to see, and what would the target audience be?

Note: I'm not around to do anything until early September

Rob

If you can provide me access to an IRIS system on GCP Cloud, then sure.

You can provide the access to IRIS on GCP by yourself - it's open for everyone, as listed in the announcement.

What functionality would you like to see, and what would the target audience be?

This is simple. I wonder, what are the benefits of QEWD for developers on IRIS.

Note: I'm not around to do anything until early September

No rush here.

Can you provide me with an IRIS license and cover the cost of the GCP Cloud Hosting for the purpose of a demo?

Hi Evgeny, Rob asked me to post his demo app he created as he's not around ATM.

The demo is the IRIS implementation variant of a very popular example app: https://github.com/gothinkster/realworld

The IRIS demo is at: Conduit on IRIS using QEWD.js

The app is a Medium.com clone (called Conduit) which is implemented with all sorts of front- and back-ends. Which makes it very easy to compare different technologies.

Enjoy!

Ward

Fantastic!  Should we substitute Community engine to it? ;)

It seems though that comments doesn’t work. 

Is there the source code of this implementation of Conduit available? I mean the implementation which works with IRIS?

Thanks Ward for raising awareness of the QEWD / IRIS demo while I'm away!

Evgeny - I'm on holiday right now and quickly integrated IRIS with the Conduit / RealWorld back-end code before I left - I didn't have much time and hadn't tested the demo out.  It's actually an interesting "hybrid" version of the back end that works with both WebSockets (the version you see in this demo) and REST (which you would see if you pointed a "vanilla" Conduit front-end at it.  

I pushed out a new version of QEWD to formally integrate IRIS, and also a new supporting module: 

https://github.com/robtweed/ewd-qoper8-iris

Just specify the database type as "iris" in your QEWD startup file, and provide the other parameters (username, password, namespace etc) just as for Cache.

Needless to say, the demo you see works identically, with exactly the same Node.js code, for all supported databases, so you'll just have to take my word, for now, that it really is working with IRIS! :-)  Actually the performance will indicate that it's hooked up to a pretty fast DB (and yes, it really is IRIS, running on an AWS EC2 Ubuntu machine): see the response time recorded in the raw response messages that you'll see if you enable your browser's JavaScript console.  All the data is being stored in IRIS as persistent JSON - see Slide decks (part 17 onwards) here:

http://docs.qewdjs.com/qewd_training.html

When I get back from holiday, time-permitting, I intend to put together some proper, updated source code for the Conduit app that people can try for themselves, using pure REST (which is probably what many / most want to see) and also (again time-permitting) do a MicroService-based version. 

However, the code base you've found will give you an initial idea how a QEWD / IRIS application would be written (though there have been some enhancements that have simplified some of the coding still further since I wrote the Conduit app).  This slide deck is up to date and explains the way you write REST apps these days:

https://www.slideshare.net/robtweed/ewd-3-training-course-part-31-ewdxpr...

I'll also check out the Comments asap to see if / why they aren't working as you report.

In the meantime, enjoy!

Rob