20 minutes 40 seconds
Speaker 1
00:00:07 - 00:00:25
Hello. I think everyone is here. I will start the class. Before I start the class, I will introduce myself. I am Deokgyu Kim, the technical sales manager at OutSystems Korea.
Speaker 1
00:00:30 - 00:00:32
I will be in charge of the education.
Speaker 2
00:00:34 - 00:00:34
Of
Speaker 1
00:00:36 - 00:00:42
course, during the course of education, but if you have any questions after the education, please feel free to contact
Speaker 2
00:00:45 - 00:00:46
me or our director of
Speaker 1
00:00:46 - 00:00:48
the OECD, Director Kim Chang-hyun,
Speaker 2
00:00:52 - 00:00:53
and I will be kind enough
Speaker 1
00:00:53 - 00:01:05
to answer. Thank you. I will be happy to answer any questions you have. Thank you. I will let him introduce himself.
Speaker 1
00:01:06 - 00:01:08
I will
Speaker 2
00:01:09 - 00:01:11
introduce myself
Speaker 3
00:01:12 - 00:01:20
briefly. Hello, I am Kim Chang-hyun from OutSystems. I
Speaker 2
00:01:21 - 00:01:22
am so happy to
Speaker 1
00:01:22 - 00:01:22
be with you today.
Speaker 3
00:01:24 - 00:01:47
As you have seen in the news, we have announced that we will be partnering with OutSystem and expand the OutSystem business. We will continue to expand our OutSystems business. We are looking forward to the OutSystems business expanding with the new members. We will support you to adapt to the OutSystems business. Thank you.
Speaker 3
00:01:47 - 00:01:49
We will support all the content you need. Thank you.
Speaker 4
00:02:15 - 00:02:55
Before we start, I'd like to say a few words. I'm Sungjin, the CEO of SCN. As the CEO said, we recently launched a strategic partnership with Australia. We have invested in the system, so please listen to the 5-day training. If you have any questions about the low-code, or if you have any business opportunities, please let me and Mr.
Speaker 4
00:02:55 - 00:02:56
Lee know.
Speaker 2
00:03:00 - 00:03:01
Thank you.
Speaker 1
00:03:03 - 00:03:13
Now, we will start the training. Some of you may have heard of our systems. Is there anyone who has never heard of it?
Speaker 5
00:03:15 - 00:03:16
Is it your first time?
Speaker 1
00:03:18 - 00:03:26
Then, there is 1 person. Is there anyone who has never heard of low-code?
Speaker 2
00:03:28 - 00:03:28
But I think there
Speaker 1
00:03:28 - 00:03:43
are a lot of people who have experienced low-code. Then, before we proceed with this training, I will briefly explain about our systems and proceed with the training.
Speaker 2
00:03:59 - 00:04:17
What is the meaning of the
Speaker 1
00:04:18 - 00:04:54
word, OutSystems? OutSystems is a representative low-code application platform. It is a tool that helps you create applications with mouse and drag and drop without using traditional coding. There are many low-code solutions and platforms. You may have heard of other things besides Router Systems.
Speaker 1
00:04:54 - 00:05:36
But if I explain a little more about Router Systems, we are is a low-code platform. The low-code and no-code we are talking about have a clear difference. The low-code platform is a platform that allows you to develop without coding. I won't go into details, but the low-code platform is a platform that is more suitable for city developers. On the other hand, NO code is a platform that allows developers to code as much as possible without coding.
Speaker 1
00:05:37 - 00:05:52
Or, when developers want to code, they can code as much as they want. It is a low-code platform that supports enterprise-class applications. To create a full
Speaker 2
00:05:52 - 00:05:54
stack application.
Speaker 1
00:05:54 - 00:06:00
Our low-code basically supports full stack development.
Speaker 5
00:06:03 - 00:06:05
So, I don't think you've ever connected
Speaker 1
00:06:05 - 00:06:27
to the service studio after installing it. Basically, we support full-stack development in service studio IDE, from data to business logic, UI, and process. It is a full-stack development platform that supports all of these in 1 IDE.
Speaker 5
00:06:30 - 00:06:30
We will tell
Speaker 1
00:06:33 - 00:07:00
you more about the details in a week's time. And although we are not going to use it in the bootcamp, Our Systems is running its own marketplace. We are running on a marketplace called FORGE. There are 4, 500 components, but currently, we are providing more than 5, 500 components
Speaker 5
00:07:01 - 00:07:02
as open source.
Speaker 1
00:07:03 - 00:07:35
Anyone can download and install the components they want and use them as much as they want. And since it is 100% open source, it is possible to see how it is actually implemented. It is provided for free. However, even if the component itself is provided as open source for free, there are some components that provide services in the back. Those things can cost additional to receive API keys.
Speaker 1
00:07:36 - 00:07:45
Besides the 5, 500 components provided by 4G, basically, in our platform,
Speaker 5
00:07:47 - 00:07:48
API links in the list
Speaker 1
00:07:49 - 00:07:52
are basically supported to operate external systems. Also, SaaS
Speaker 2
00:07:52 - 00:07:53
based on other cloud, In this sense, to work with external systems, we support API in
Speaker 1
00:07:53 - 00:07:57
the REST. Also, other cloud-based SaaS, such as Salesforce, ServiceNow,
Speaker 5
00:08:01 - 00:08:02
SAP has a cloud version
Speaker 1
00:08:02 - 00:08:09
and an on-premise version. Whether it's a cloud or on-premise enterprise system, it is very easy to work
Speaker 2
00:08:09 - 00:08:10
with external systems. SAP has both cloud and on-prem versions. We provide various connectors or integration components so that
Speaker 1
00:08:10 - 00:08:16
you can easily connect to external systems whether it is a cloud or an on-prem enterprise
Speaker 2
00:08:19 - 00:08:20
system.
Speaker 1
00:08:22 - 00:09:10
And of course, when you use the OutSystems platform, you set up an internal DB and use it. If there is an external DB that each company or company uses, you can easily connect external DB and use it. And basically, from the design stage to to distribution of the app and operation environment. And full life cycle. So basically, we are a PaaS standard, but if you subscribe to our system and use it, we
Speaker 2
00:09:10 - 00:09:10
provide a set
Speaker 1
00:09:10 - 00:09:23
of development environment, test environment, operating environment, and CRCD environment. And the applications we develop for our systems, they are
Speaker 2
00:09:23 - 00:09:23
basically developed based on
Speaker 1
00:09:23 - 00:10:07
semi-contact web. Therefore, with 1 source, with 1 application, you can easily respond to PC or mobile. In addition, if you need more specialized mobile features, such as hardware sensors, offline features, as local storage, you can develop native apps. When developing a mobile native app, you can use the same source, Android and iOS, in each build at once. I can tell you that it is very useful.
Speaker 1
00:10:13 - 00:10:19
And The Scale Security Performance Flexible Deployment Card below
Speaker 5
00:10:19 - 00:10:20
does not apply to on-prem,
Speaker 1
00:10:23 - 00:10:44
but only applies to PaaS. If you subscribe to Scale, we provide free scale-up and scale-out for all instances depending on the usage. There is nothing to say about security. In terms of performance,
Speaker 5
00:10:46 - 00:10:47
we guarantee performance by providing scale-up
Speaker 1
00:10:47 - 00:11:37
and scale-out for front-end servers, development servers, runtime environments, and DD server in the back-end. In the case of AWS, domestic clients will basically use AWS before Seoul, but if you want to build an operating environment in the U.S. For future global services, you can easily add the environment to any region you want in our OutSystems Cloud. So, basically, OutSystems has an ID called Service Studio. In our systems, there is a service studio called IDE.
Speaker 1
00:11:38 - 00:11:55
Next, the development environment where the development platform and the runtime environment are developed in Parcels. So, you use the service studio to access the development platform and develop.
Speaker 2
00:11:59 - 00:11:59
All the
Speaker 1
00:11:59 - 00:12:23
content I develop in the service studio is uploaded to the development platform, and all the source codes are generated, compiled, and built, and run in a runtime environment, providing an environment where you can see the results at once. As I said, we provide each environment separately for development, test, and operation.
Speaker 2
00:12:23 - 00:12:24
And provide a better environment for users to use.
Speaker 1
00:12:24 - 00:12:24
As I mentioned earlier, we
Speaker 2
00:12:24 - 00:12:25
provide different environments for development, testing, and operation.
Speaker 1
00:12:25 - 00:13:07
This is how we can develop based on each environment. The main things we will use this week are service studios. We will develop everything in Service Studio. In addition, There is another IDE called Integration Studio. It is not for developing low-code, but if you want to code with C-sharp, or if you want to connect external DB, we provide an IDE that can make a connector that connects external DB or that can be used for C-sharp coding.
Speaker 1
00:13:07 - 00:13:08
1 thing
Speaker 2
00:13:08 - 00:13:08
to note is We provide a separate IDE for creating a connector for
Speaker 1
00:13:08 - 00:13:33
the DevDB connection or coding C-Sharp. 1 thing to note is that We provide all the IDE, so it can be developed anywhere. In the case of Integration Studio, we provide it only in Windows environment. That is, our system itself is based on the Windows server, and it runs on the .NET framework. So
Speaker 5
00:13:36 - 00:13:36
the source code generated on
Speaker 1
00:13:36 - 00:14:16
the server is C-sharp. Therefore, to develop C-sharp, we need a visual studio and other environments. Currently, it is only available on Windows. In the for the service center and Lifetime, we will be going into it once a week, not today, but in the future. It is a platform, a platform server, a management portal that manages the environment and the entire infrastructure.
Speaker 1
00:14:16 - 00:14:49
It's a simple admin portal. And besides what I've said so far, there are many services that provide various SaaS forms. This is a typical integration builder. Integration builder is a service that can easily create a wizard-like connector when linking various external systems. I will explain more about AI Method Studio later.
Speaker 1
00:14:54 - 00:15:20
This is the image of the service studio. This is the integration studio. This is the tool used to develop C-sharp coding or external DB connectors. This is the management portal that manages the development, test, management, and CRCD environment. Lifetime is
Speaker 2
00:15:21 - 00:15:21
a communication management
Speaker 3
00:15:21 - 00:15:22
portal that
Speaker 1
00:15:22 - 00:15:49
manages the entire infrastructure including these 4 environments. And it is also a tool that can manage and run tests or operations when deploying. I'll explain the users in detail later. And then, Holt. This is a marketplace we are running.
Speaker 1
00:15:51 - 00:16:23
When I want to go in here and find the component or UI function I want, I can find it through a search and use it right away. It's an integration builder. Basically, you can see Salesforce, SAP, MS products on the network, and other services. You can see the
Speaker 2
00:16:23 - 00:16:24
tools to make connectors.
Speaker 1
00:16:29 - 00:17:01
For example, the integration builder is used to create connectors for the items on the left. In addition, when creating other web DBs or custom connectors, you can see that the integration studio is used. And use it in the future. This is what we will add in detail later during the training. This is called AI mentor studio.
Speaker 1
00:17:02 - 00:17:04
What is this? When you
Speaker 5
00:17:04 - 00:17:05
develop an application in our systems,
Speaker 1
00:17:07 - 00:17:11
the reason for developing with low-code is
Speaker 2
00:17:12 - 00:17:12
to make it easy
Speaker 1
00:17:12 - 00:17:58
to develop, but after development, it it easy to operate in the operation stage and to make it easy to maintain the need for this. AI Metastudio is an application developed by me at Outstreams, which is analyzed by AI and the technology is being built up. If you develop without following the best practice, AI Mentor Studio will point out that you are not following the best practice.
Speaker 5
00:17:59 - 00:18:00
To follow the best practice,
Speaker 1
00:18:00 - 00:18:08
you need to improve in this way. So, AI Mentor Studio is suggesting the
Speaker 2
00:18:08 - 00:18:08
direction to improve. To improve the performance of the application. So we are offering a
Speaker 1
00:18:08 - 00:18:11
direction to improve. AI Mentor Studio analyzes
Speaker 5
00:18:13 - 00:18:15
the application in 4 major aspects
Speaker 1
00:18:15 - 00:18:48
to inform the direction of improvement. Architecture, security, performance, and maintenance perspective of the application. For example, When there is a logic called A, you can make it once and use it in multiple applications. But on the other hand, if a developer suddenly does not know that the common function of the existing A is developed, If
Speaker 2
00:18:48 - 00:18:48
you don't know that the A
Speaker 1
00:18:48 - 00:19:22
function is developed, and you can develop something new yourself, then AI-Mentor Studio has 2 separate modules, and if you say, it's a similar function, it's almost the same function, is it right for you to separate them and develop them individually? Or is it right to tie them together and use them as a reference? I'm looking for these things and suggesting them. This is the image of AI Studio. It is a hit map.
Speaker 5
00:19:25 - 00:19:27
The red modules are the modules
Speaker 2
00:19:27 - 00:19:27
with a lot of
Speaker 1
00:19:27 - 00:19:55
technical attachments. I go into it and find out what each item is and see if it is something I to improve, if I say I did it on purpose, not to improve, if you say Ignore, the technology fan will know that it was not intentional, so you can manage the technology fan score. I'll tell you about this at the end. You can manage the technical knowledge points by saying, this is not intentional, but intentional. I will tell you this
Speaker 2
00:19:55 - 00:19:58
at the end. Next, I will briefly
Speaker 1
00:19:58 - 00:20:22
explain about our systems platform. Do you have any questions? If not, I will start the bootcamp training. I sent all the emails to the people on the list of participants. Is there anyone who didn't receive the email?
Speaker 1
00:20:23 - 00:20:31
I sent you an email around 8 o'clock today. You got it all, right? Then, I will explain the contents in
Speaker 2
00:20:31 - 00:20:31
more detail before I proceed
Speaker 1
00:20:31 - 00:20:34
with the first presentation training and use
Speaker 2
00:20:34 - 00:20:35
the actual service studio. I will explain more about this before I start the presentation and
Speaker 1
00:20:35 - 00:20:36
use the service studio.
Omnivision Solutions Ltd